[Steven W]

Assuming everything else is okay, that line in apps.inf should force *anything* that's processed by command.com to go fullscreen. So, I'm kinda weirded out as to why it would fail.

[Steven W]

A thought occurs, you say you installed all options with the Service Pack. Is CMD.EXE set to take over any of this stuff?

[Steven W]

SPUPDATE.INF:

HKLM,"Software\Microsoft\Command Processor","AutoRun",,"set comspec=%13%\CMD.EXE"

[PROBLEMCHYLD]

Nothing is failing I'm just saying I have to use both methods for exe and bat files to work. Everything is fine

[PROBLEMCHYLD]

I can confirm, I need both methods. One works with .exe files while the other one don't and vice verse.

Can you clarify, I'm confused.

I needed to create the _DEFAULT for exe files and change the command.com for bat files hence both methods are needed.

[Steven W]

I needed to create the _DEFAULT for exe files and change the command.com for bat files hence both methods are needed.

Okay, your referring to it as 2 methods threw me off. I was thinking you were doing something like creating PIFs for every .exe or something. I'm glad to finally (it has been nearly a year that I figured this out) see verification that this works. I'm surprised nobody else has posted saying it works or that I've messed up their computer.

[PROBLEMCHYLD]

This is the last version to work in Qemu

Realtek Semiconductor Corp. AC'97 Sound System Software Version: A 3.62

The VXD version crashes MS Hover! Hard restart is needed. This is the only WDM thats works which is latest for Win98 SE. I tried all others and they crash the system.

[Steven W]

This is the last version to work in Qemu

Realtek Semiconductor Corp. AC'97 Sound System Software Version: A 3.62

The VXD version crashes MS Hover! Hard restart is needed. This is the only WDM thats works which is latest for Win98 SE. I tried all others and they crash the system.

I take it that you're referring to WDMex? I think you meant this for your thread (SP3), but eh... I highly suspect if rloew was getting anywhere with that, he'd not have abandoned it when he did. Even if it gets a handful of devices to work, I guess I'd question if those devices could be made to work without the overhead of WDMex (modding INFs, yadda, yadda, yadda). I'm not claiming to be some expert on WDMex, but I've yet to see a compelling reason to use it. When you brought it up, I did a search, as I mentioned and in addition to the stuff I spoke of, I saw some 'redditors' saying something to the effect of "I INSTALLED WDMex, I CAN MAKE MY DEVICES WITH XP/VISTA DRIVERS WORK"....I just rolled me eyes. Speaking of stupid shit on the internet, I'm sure you're already aware, the number of Youtubers installing your Service Pack who apparently don't understand what 'Install Separately' means, is shocking.

[Steven W]

By the way, does Hover work with VBEMP 9x, or did you get QEMU to emulate another card?

[PROBLEMCHYLD]

By the way, does Hover work with VBEMP 9x, or did you get QEMU to emulate another card?

Hover works fine, it only crashes with AC97 VXD driver so I found a working WDM driver. WDMEX is not needed and the newer AC97 drivers doesn't work beyond A3.62