Here's a new one (another error message!!)

[philipg]

Well to fix the winaspi.dll

If you run sfc.exe from within windows and extract win98 version it may fix it.

or

You could do a find and it may find two or more copies on the system. save the one under windows by another name then replace it with the other one.

One one of these should fix that blue screen error.

[Danzego]

I'll give that one a whirl tonight when I get back from going out. Just checkin my mail and such real quick now, but I got another error message when starting up the ole beast. This one read "Insufficient memory to start windows". I turned it off and rebooted and all was okay (except, of course, that blue screen message, though it wasn't followed by the WINASPI.DLL remark this time). What causes the insufficient memory thing?

[StarWatcher]

Danzego, A couple of suggestions:

1. Try putting this line as the very first line in your Config.sys file-device=c:\windows\himem.sys

2. Also, do you have a fixed swap file? I only have 64Ram and a fixed swap of 100 min/max. I have not received an out of memory message since. Go to this site for info on how best to set a fixed swap file http://epsilon.silicon.net.my/adrian/

Windows has a nasty habit of grabbing memory and not releasing it. If you have been running a program such as, Word etc., you must re-boot before windows will release the memory. Also, make sure there are no open files in Clipboard.

Hope this helps.

[Danzego]

(previous post applies)
Well, got another error message today. I'm trying to decipher this one and I hope I'm on the right track (then again, maybe not). Nonetheless, I haven't been able to break my system down to just display adapter just yet, and I recieved this message. When I start up the 'puter, I get a blue screen that states "Invalid VxD dynamic link call from APIX(01) + 00002E96 to device "33FC", Service 3. Windows configuration is invalid." It then gives me an option to go ahead and start W98 in an unstable state or tells me to run setup. If I go ahead with windows, I promptly get as window that states something along the lines of a program I used changed or loaded older files into "WINASPI.DLL" and to run setup. I really don't want to run setup again because as you know (if you read my previous post) that all I'm going to have is the same problems again. Now I know that ASPI refers to my SCSI card (TEKRAM 390F) and as soon as I get a chance I'm going to pull it and reload (I sniffle at this because I have a SCSI CDRW), but does anyone think I'm on the right track? Windows has rewritten my registry multiple times since my last reload, so could this have introduced the older files? And, did it do so because my SCSI adapter could be the problem device? I know this is really open to debate or speculation, but if someone has seen these messages before, any advice would be helpful. Reply if you have any ideas even if you haven't seen these and want to offer some goodwill. TIA!!