I was happily flying along in my newly serviced VA DC3 all going well from EGLL to EGGP when suddenly the whole she-bang collapsed and I was left looking at a blue screen informing me that 'A problem ahd been detected and I should restart my computer and check my 'BIO' updates.
Can anyone tell me what may have happened?
At the time I had FS9 running with FlyNEt, FsNav, ASv6 and a CD palying in the tray to keep vitual pax happy.
Computer restarted OK and I the ran the XP defragmentation program twice.
Computer crash 'BIO' problem?
Moderators: Guru's, The Ministry
- DaveB
- The Ministry
- Posts: 30457
- Joined: 17 Jun 2004, 20:46
- Location: Pelsall, West Mids, UK
- Contact:
Hi James,
Sri but no logical answer to this. Putting PY to maint is a very simple and straight forward thing. Flynet keeps a log of it's previous flights and returns the maint to 100%.. no more, no less.
While I couldn't guarantee that FlyNET wasn't responsible in some way.. it does seem very unlikely. Perhaps another pilot can be of help but nothing springs to mind for me I'm afraid :think:
ATB
DaveB :tab:
Sri but no logical answer to this. Putting PY to maint is a very simple and straight forward thing. Flynet keeps a log of it's previous flights and returns the maint to 100%.. no more, no less.
While I couldn't guarantee that FlyNET wasn't responsible in some way.. it does seem very unlikely. Perhaps another pilot can be of help but nothing springs to mind for me I'm afraid :think:
ATB
DaveB :tab:


Old sailors never die.. they just smell that way!
Computer crash 'BIO' problem?
For Dave:
I agree. I do not think that FlyNET caused the problem.
I had spent much of the evening prior to the crash in attempting to deal with duplicate afcads as outline by Peter elsewhere in the forum. I began with 47!!! Many are in Free Flow scenery but I concentrated on UK and Eire as most likely to possibly effect my VA flying. Perhaps I have done something wrong - After renaming some of the default bgls containing AFCADS I put them in the 'recycle' bin. Maybe they should while remaining renamed xxxx.bgl.dis be returned to their original default location.
I agree. I do not think that FlyNET caused the problem.
I had spent much of the evening prior to the crash in attempting to deal with duplicate afcads as outline by Peter elsewhere in the forum. I began with 47!!! Many are in Free Flow scenery but I concentrated on UK and Eire as most likely to possibly effect my VA flying. Perhaps I have done something wrong - After renaming some of the default bgls containing AFCADS I put them in the 'recycle' bin. Maybe they should while remaining renamed xxxx.bgl.dis be returned to their original default location.