Win98SE shutdown problem

[Sussed]

Hi,

I upgraded my old system with a new Antec ATX case/PSU, Asus P4PE motherboard, CPU etc.

It's a dual-boot arrangement, 98SE/XP.

XP is a fresh install but 98SE is the original install, upgraded with the latest Intel chipset .inf installer, and there's no hardware conflicts.

Now when I try to shutdown Win98SE it just gives me a blank screen and a blinking cursor, but the PSU will not turn off! I can still re-boot using Ctrl-Alt-Del so it hasn't crashed I believe.

If I shutdown from WinXP, it works fine, and turns the PSU off etc.

Is this a quirk with ATX PSU's and Win98? The original system used an AT case/motherboard.

Any ideas?

TIA.

[Mikki]

No issue with psu's....I know you don't want to hear this because it's a pain, but I'd do a fresh install....it's always good to do after a major hardware change...

[Sussed]

Hi Mikki,

Yes, I agree with you but if I can possibly get away without doing a re-install that would be nice!

[Monkey Hanger]

Have you got the "Shutdown Supplement" update from the Windows Update site?
I think it's Q239887.

[Sussed]

Originally posted by Monkey Hanger
Have you got the "Shutdown Supplement" update from the Windows Update site?
I think it's Q239887.

Hi,

thanks m8, the Wizard referred to at that site helped enormously!

I found out that it was the SB Live! Value that's causing the problem. More specifically the DOS drivers! (Yeah I know...but Frontier First Encounters still gets played sometimes here )

Now I have half solved the problem, but something mysterious is happening.

This is my original autoexec.bat file:

SET BLASTER=A220 I7 D1 H5 P330 T6
SET CTSYN=C:\WINDOWS
C:\PROGRA~1\CREATIVE\SBLIVE\DOSDRV\SBEINIT.COM
mode con codepage prepare=((850) C:\WINDOWS\COMMAND\ega.cpi)
mode con codepage select=850
keyb uk,,C:\WINDOWS\COMMAND\keyboard.sys
SET PATH=C:\PROGRA~1\ULTRAE~1;%PATH%

rem C:\PROGRA~1\COMMON~1\NETWOR~1\VIRUSS~1\40~1.XX\scanpm.exe c:\
rem @IF ERRORLEVEL 1 PAUSE

I removed the first 3 lines (installed by SB Live), then restarted the computer, and guess what? The first 3 lines keep being rewritten to the autoexec.bat file! ***?

The only solution I can find now is to delete or rename the DOSDRV directory to stop the drivers from actually being activated, and I can then shutdown properly.

But *** is causing those 3 lines to be continually added to autoexec.bat??? Also the DOSSTART.BAT file contains this:

C:\PROGRA~1\CREATIVE\SBLIVE\DOSDRV\SBEINIT.COM
c:\mouse\mouse.exe

Again, if I remove the first line it ALSO gets rewritten!

Anyone know why this is happening?

TIA

[Monkey Hanger]

Sussed,

If you have the DOS Legacy Emulation anabled, that will be what is writing the Autoexec stuff.
If you think about it's obvious, you only need the Autoexec.bat and config.sys when you are in DOS. Hence, that's why DOS loads them in that way.

Easy innit ???

[Sussed]

Originally posted by Monkey Hanger
Sussed,

If you have the DOS Legacy Emulation anabled, that will be what is writing the Autoexec stuff.
If you think about it's obvious, you only need the Autoexec.bat and config.sys when you are in DOS. Hence, that's why DOS loads them in that way.

Easy innit ???

No, sorry, I still don't get it I'm afraid. Could you elaborate on what you mean by 'DOS Legacy Emulation enabled'?

If you mean the 'Creative SB16 Emulation' in the device manager that was there before the DOS drivers were installed, and it certainly didn't write anything to the autoexec.bat before. Is that what you meant?

I was under the impression that it was the 3rd line that activated the DOS drivers?

But how come the same 3 lines get re-written to autoexec.bat after I've deleted them completely, as the DOS drivers would no longer be enabled after a restart?

I'm really confused! LOL

Any ideas?

TIA.

[Monkey Hanger]

I have a PCI128 and if your card is similar then these are the steps.

Device Manager
Select Sound card under Sound video and game controllers
Take Properties; then Settings

And I see a check box for "Legacy Emulation Enabled" under Configuration.

Do you not have something similar?

If I active it then an extra entry appears in Device Manager called Creative Soundblaster PCI128 Legacy Device. Merely de-activating that will not do. It must be unchecked from the stage above.

[Sussed]

Hi Monkey Hanger,

No, there's no options like that under any of the Creative listings in the Device manager for the SB Live! Value.

[Monkey Hanger]

Originally posted by Sussed
Hi Monkey Hanger,

No, there's no options like that under any of the Creative listings in the Device manager for the SB Live! Value.

I should have Googled it in the first place. Here's your answer.

[Sussed]

Yep, that's the lil bugger m8!

Well done, and thanks VERY much for your help and all your efforts.

Now WHY did it work OK before with the Supermicro P6SBA and not with the P4PE? LOL

When I do a major re-install in a few months time it'll be interesting to see if this process needs to be gone through again.

Thanks once again

Best regards

Sussed.

[Monkey Hanger]

Like the trains, we get there in the end!

[parasite]

Dont feel bad I hate to reinstall windows me because you lose the start up program in dos for both operating system and you will have to reinstall windows xp.

[kevman_abx]

I have a PCI128. I'm running WIN98 but the PCI128 don't work in DOS. I have the SBINIT.COM called in AUTOEXEC.BAT and the SET BLASTER and SET SBPCI lines. Do I need anything set up in CONFIG.SYS ?

I'm trying to play EF2000 (Eurofighter 2000. Flight sim in DOS). its still a great game.

Cheers

Kev

[wallijonn]

Originally Posted by Sussed

Now WHY did it work OK before with the Supermicro P6SBA and not with the P4PE? LOL

It worked because you had set ACPI on the old mobo before you installed the OS. When you changed the mobo new ACPI drivers had to be installed because the ACPI is handled by a different chip. How did you set the new mobo for, S3, etc? If you boot into W98 Safe Mode and open up your device manager you will find all the old chipsets and peripheral devices. Get rid of all the old stuff and uninstall any old software associated with those devices, run msconfig and make sure no old drivers are being run. Then get rid of all the old drivers which you found when you did a Properties of in Device Manager. Clean the registry of all the old stuff. Then reboot. It should find new devices and ask for new drivers.