LLXX

What I meant was, just appending the two rename commands to the batch file already listed in the OP is the simplest solution. VBscript has its uses, but for a simple automation like this, a batch file is all that's necessary.

Wow, what I did with 2 rename commands you needed 8 lines of VB script... good work

What's the video card model/manufacturer?

ren *.wav.mp3 *.mp3 Edit: rename command didn't work as I expected it to Edit2: figured it out: ren *.wav.mp3 *. ren *.wav *.mp3

CBM1180/2080/2081 utility: http://4esky.68ab.com/cbm2080.rar Manual: http://www.crystalking.com.tw/Flash/PDF/eManual.pdf

Any idea what chipset the machine has? Look under System Devices in the device manager.

Windows uses the partition sizes that are reported in the MBR, I can demonstrate this by using disk editor to change the size of the partition to something that exceeds the physical capacity of the disk (e.g. 1.5 terabytes) and then viewing the drive properties under Windows. Maybe I'll post a screenshot of that on my next boot to DOS...

WinFile has a lot of other internal limits... All I fixed was _llseek and nothing more, it may enable older programs to read/write 2Gb+ files correctly. Problem with _llseek still exists in 2000 and above, I believe M$ didn't look too much into fixing legacy API. The problem probably still exists in Vista. However I doubt anyone using 2000+ OSs is going to be using older application that use _llseek, so it is not much of a problem.

As far as I know, nobody has managed to run IE7 on 98SE, so you'd be better off asking in another forum. What are you trying to do, use the IE7 rendering engine on 98SE? I highly doubt that would work.

Hard disk is probably dying. A corrupted VMM32.VXD is a first sign of this problem.

Is it detected in the BIOS?

I was referring to Petr's post... where he used a BIOS that did not support 48bit LBA and it worked fine. The BIOS shows as 8Gb, but Windows will use the information stored in the MBR. With some partitioners it is possible to create partitions manually and ignore BIOS information, or you can use a disk editor to do it.

Update: Added 4.10.1998 for those that wanted it.. Regarding the NOPs in the HDD driver (discuss this further in the Enable48BitLBA thread, not this one which has absolutely nothing to do with it...), I think they were originally a call to a logging routine for debug purposes, but was NOP'd out in the release version.

Well, Dells are based on PC architecture too, which means they use the same voltages (+12v, +5v, +3.3v, and -12v.) as a standard ATX system, although the pinouts may be slightly different. An easier way would be to get an adapter like http://www.endpcnoise.com/cgi-bin/e/std/sku=dellconverter or cut and splice the wires, as there are pinouts for Dell and standard connectors available everywhere on the Internet and all you need to do is match the voltages.

Run HiJackThis and post a log. Or maybe you'll be able to find it in the log already.

Couldn't find? I specified the exact name... http://www.google.ca/search?hl=en&ie=I...27%22&meta= (If you don't understand Chinese, "下载" means download.)

Yes, looks like it...

http://support.microsoft.com/kb/921914 Remove it and be done with it.

Check your RAM with MemTest86+.

http://www.msfn.org/board/index.php?s=&amp...st&p=541943 Same situation?

Micro$oft doesn't even sell 6.22 and older DOSes, not to mention support for Win98se was completely discontinued a short while ago.I doubt anybody is losing any profits from the distribution of this either. BTW a lot of this site is supposedly illegal anyway - the M$ license prohibits you from modifying their files. nLite is a good example. In this forum, Enable48bitLBA and Copy2Gb are as well.

I waited longer than that... I opened the system properties, was confused that the CPU info wasn't shown, and just left it open while I just browsed some web sites etc. I don't know how long but when I closed all the windows the system properties was still open and the CPU information was there again.

If you don't have a floppy drive, get one.

Looks just like a fine plastic polish to me...

Wait for some time after opening the system properties. I've had this happen before, after a few minutes it shows the information again.