' Wrote:Course it didn't work. There's no VB6 in DSLauncher. It's written in C#.NET (2010 I think).
Bob, I find service packs usually fix this kind of error. At least, it did on Vista.
SP? My copy's wannabe legal... It's fully updated.:(
Ah well. It's not a real issue, and Ioncross is the more irritating problem anyway.
I generally forget to use useful stuff like this anyway xD
DSLauncher is a C# based application, but FAM is written in VB.NET, although I doubt the runtimes will help you much anyway - most systems will have them installed as standard with the operating system, or via various updates. DSLauncher was thoroughly tested on XP, Vista and Windows 7, once without updates (but with the required .NET FX), and once again with full updates, including service packs.
One thing you could try, is registering the OCX controls (hopefully eliminating the error).
If you have x86 (32-bit), you should follow these steps:
Code:
Start > Run > "cmd"
cd C:\Windows\System32
regsvr32 COMDLG32.OCX
If you have x64 (64-bit), use these:
Code:
Start > Run > "cmd"
cd C:\Windows\SysWOW64
regsvr32 comdlg32.ocx
Restart the system after registering the OCX controls. Make sure you do it while FAM is closed. That might help you out by registering the OCX component that it's complaining about.
As for Ioncross and FLCompanion, I'll get around to working the checks for those in later today once I get back from the bank. If there are no objections, I plan to place them under the "Tools" menu item, which will come below Mod Manager, and contain links for Ioncross, FLCompanion and Datastorm.
' Wrote:Warnings will be issued. Accounts will be banned. In game characters will be deleted. I will drive to your house and punch you in the mouth.
' Wrote:DSLauncher is a C# based application, but FAM is written in VB.NET, although I doubt the runtimes will help you much anyway - most systems will have them installed as standard with the operating system, or via various updates. DSLauncher was thoroughly tested on XP, Vista and Windows 7, once without updates (but with the required .NET FX), and once again with full updates, including service packs.
One thing you could try, is registering the OCX controls (hopefully eliminating the error).
Code:
Start > Run > "cmd"
cd C:\Windows\SysWOW64
regsvr32 comdlg32.ocx
Restart the system after registering the OCX controls. Make sure you do it while FAM is closed. That might help you out by registering the OCX component that it's complaining about.
As for Ioncross and FLCompanion, I'll get around to working the checks for those in later today once I get back from the bank. If there are no objections, I plan to place them under the "Tools" menu item, which will come below Mod Manager, and contain links for Ioncross, FLCompanion and Datastorm.
Did that, then restarted the comp and I still get the message. \: (FLAM was closed of course...)
On the other hand, could you create a "Launch on Windowed Mode" too?:PAnyway nice program, I like it. ^^
' Wrote:Did that, then restarted the comp and I still get the message. \: (FLAM was closed of course...)
On the other hand, could you create a "Launch on Windowed Mode" too?:PAnyway nice program, I like it. ^^
EDIT: Never mind, found windowed mode thingy.:P
Indeed there is a windowed mode already in place.
As for the FAM issue, I assume yours also works when executed as admin via a shortcut? If so, I may have to do a little digging around, as I can't seem to replicate this problem in any of my test environments.
' Wrote:Warnings will be issued. Accounts will be banned. In game characters will be deleted. I will drive to your house and punch you in the mouth.