Hi again
If the system can boot into Safe Mode, try using msconfig to inspect the startup files. If you can find the NAVAP.vxd in there, you should be able to manually edit it out (from within msconfig, by selecting the Edit button in the relevant startup file). I think glc's reply might mean it's likely in the system.ini file.
If you can't get to msconfig, try SysEdit again.
Here's an old article with the default system.ini values listed in it: you can use it to help compare your neighbor's current file with the defaults.
http://printers.necsam.com/public/pr...ft/Q140441.htm
If the new board has onboard sound, you'll of course have to disable it in the bios - if you're planning on re-using an add-in PCI sound card from the previous install. If it's the same sound card as before, try reinstalling those sound card drivers in Safe Mode & see if that takes care of the EMM.386 messages. I believe it's just legacy memory management for older games. When needed, there are usually lines in the config.sys file that read something like:
DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
The whole scenario is covered a little in the MSKB article
http://support.microsoft.com/default...b;EN-US;q75592
If you can't get into Safe Mode to reinstall the sound drivers, you could try editing the config.sys file. You'd either edit to include the memory manager lines [which have to be in a certain order, that's all in the EMM.386 MSKB article (the 2nd link above)] --- or edit to REM out any lines for the DOS memory managers & DOS drivers --->and let a later reinstall of the sound drivers take care of things.
See if that does it.
. . . Gary