• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Development Computer Died...

CanadaKen said:
Does the dead PC have an old PS2 keyboard jack? I had a friends PC lock up the same as yours but I ran home and grabbed an old PS2 keyboard....it booted.....ran a Windows Repair from the disks....all was well.
Click to expand...
Unfortunately, no it does not. I still haven't taken the time to look at it any closer as I'm still in the reconstruction stage...

I had quite a fright a few days ago when bloody overnight Windows updates forced a reboot. The "old hard drive" was still in my docking station, and apparently during the reboot the computer "saw" a Win7 Pro installation on the "old HD" and attempted to load from it rather than the master "C" drive! From that point on every reboot of the system would stall with an enigmatic message about "winload.exe is either missing or corrupt" and would then ask which "Win7 Pro" version I wanted to load. After choosing #1 the system would then proceed to complete booting normally. :banghead:

Using BCDEdit.exe I opened up the boot loader and noticed that there were two entries now for the two operating Win7 systems, the #2 of which did not have a path to winload.exe present. An hour of so of Google research led me to MSConfig.exe as a way of removing the errant #2 entry, after which everything reverted to normal operations. :wizard:

I've now configured this system to not download and install updates automatically, I need to remember to physically remove the "old HD" from the docking station before rebooting the system! :rotfl:
 
Bill, EasyBCD is a great alternative boot configuration editor should you need one. I swear by it (which is better than swearing at MS system tools, tsk tsk)

ah – free for non-commercial use, $30 otherwise :oops:
 
That's good to know, Tom. Thanks. Fortunately, MSConfig.exe accomplished my desired task with one mouse click, which was to completely delete the unwanted #2 operating system entries...
 
You must log in or register to reply here.
Back
Top