OnCourse Software

Hi Dillon,
Sorry but I have no idea what Windows is doing when the splash screen calls the gui. Our really does sound as though there is a system dll that's been wipef out or corrupted

Sent from my Samsung Galaxy S

Kind of disappointed there's no solution from the guys who actually programmed the software. I ran the Windows restore feature which did not solve the problem... If I could debug it I'd find the faulting code...

For the record everything else on my machine from IE8 to Google Chrome to FS9 to all my high end aircraft/scenery to TrackIR to ActiveSky Evolution runs without any issue. This is something unique to this application alone. It's a shame a developer can't tell me what the unique set of circumstances are to their own software that would cause it to fault when loading up. There's something it's looking for that no other application on my machine needs that's causing the problem, this should be easy (because we've eliminated all standard .dll's). I've even reinstalled my Visual Basic runtime files. I wish someone could tell me something here...

Hi Dillon,

Since you had this program running for years without any issues I think its safe to assume the program is basically sound. The problem started after something got screwed on your system.

This runtime error can be caused for a number of reasons and without knowing the exact line of code the error occurs it is not easy to speculate the root of the problem. If this was happening on my system it would be easy to diagnose. On your system I would need to send you a new executable to run, one which I could add some additional debug code. I have no problem doing so but when that might be I really couldn't say. We're in the middle of completing a new house build, into which we'll be moving. All my development equipment is packed away.

By all means keep nagging me so I don't forget.

Sent from my Samsung Galaxy S

Fair enough...

Good luck with your move.

dmarch wrote:

We're in the middle of completing a new house build, into which we'll be moving. All my development equipment is packed away.

By all means keep nagging me so I don't forget.

Dave is there any estimated date your move will be complete where it makes since to check in with you to see if your up and running so we can work on this issue?

Just wondering becasue I have no idea as of now when to start checking back in with you.

You could be looking at days or maybe a few weeks here...

You could if you want to,reformat your HD and re-install windows if you don't want to wait,depending how much stuff you have or time depending!

It's your call...

Dave Leesley wrote:

You could be looking at days or maybe a few weeks here...

You could if you want to,reformat your HD and re-install windows if you don't want to wait,depending how much stuff you have or time depending!

It's your call...

I have years of FS9 development and other work on my system. Reinstalling WindowsXP is not an option unless I had a totaly HD failure which happened a year and a half ago...

Any word on you guy's systems being back up and running so I can get my issue looked at and hopefully help someone else that could have this problem in the future?

whats to say that part of your HD as failed now,hence the reason for it not working?

Have you contacted the makers of the scenery you installed to see if they might have a solution...maybe someone else as had similar issues?

Did you make backup of your HD prior to FS2004 crash or regular backups?

Dave Leesley wrote:

whats to say that part of your HD as failed now,hence the reason for it not working?

Have you contacted the makers of the scenery you installed to see if they might have a solution...maybe someone else as had similar issues?

Did you make backup of your HD prior to FS2004 crash or regular backups?

FS9 and every other add-on I have installed (which is almost every decent add-on ever made) is running great. I have FS9 installed on a separate HD from the Windows 'C' drive. AMS has stated they know their scenery has a bug in it. Usually it just crashes FS9 but they have no idea how to fix FDC.

Why are we here again when it was promised to me a debugger file would be issued so we can see exactly what the faulting file is. This is a problem with FDC and FDC only on my system. Yes a buggy scenery caused the problem because FDC was running in the background when this happened but that doesn't negate the fact I shouldn't come here and ask for support when I've exhausted every other option. My whole FS9 is not the problem here it's only FDC after a series of unfortunate events. I'm sure with the right debugging file we'll find the problem file and I'll be free to fix whatever FDC is looking for within Windows.

It shouldn't be this hard to get support....