LLXX

XP CDs don't have copy protection on them. If every CD you burned has a different file-copy error, I suspect the media you're using is defective. Try burning at a lower speed.I've had this problem too... burned 3 of them with various errors but the fourth one worked perfectly.

You're using the wrong DOSKEY. You're using the one that is used in protectedmode command prompt. What you need is the realmode TSR - get it from a win98 or winME disk. What version of kernel are you using? Use VER command to find out. It's probably a 4.10.2222A.

All CD-ROM drives are not created equal. Some have better chances of reading slightly non-standard discs than others.

Of course that would work... you're just limiting the amount of RAM it can use.

A little Googling goes a long way... MSH263.DRV? That would be this? http://members.driverguide.com/driver/deta...?driverid=24858 Or, is it an H.263 codec?

I'm assuming your drives are FAT32 or your boot disk contains an NTFS filesystem driver, otherwise it's pointless to boot from a DOS disk to e.g. repair an XP installation. LFNs are not supported by the standard DOS kernel for bootdisks (98se v4.10.2222A/MS-DOS v7.10), you need LFNDOS or similar utilities to manipulate them. Auto-complete? Include DOSKEY utility on the disk.

According to your explanation, you just fried your video card. You connected the +12v to the +5v input. You fried your mobo too. Putting 12v into the video card also put 12v through the PCI-E and into the mobo's 5v circuitry.

Reinstall it over your current installation. That should overwrite the modified files.

If you delete the CD-ROM drive from the device manager, Windows should re-detect and reinstall its driver on the next reboot... that might fix the problem with it.

Couldn't you just format the new HDD and copy *all* the files over, or do an Image copy? That's worked for me when I changed drives... after copying the files and FIXMBR'ing and FIXBOOT'ing the new drive from a final boot to the console on the old drive, just boot from the new drive.

Pro has many more features that require extra/different files than home. If you FC the files in the Pro distro and the Home distro, you'll find quite a few differences. See here if you don't want to compare yourself: http://www.tacktech.com/display.cfm?ttid=104 Essentially what you get is an OS halfway between pro and home. Now MS wouldn't be so stupid as to include Pro files on the Home CD?!?! However... turning Pro into Home is much more feasible

http://www.dnsstuff.com/tools/ptr.ch?ip=212.134.155.211 Do you have a firewall? Is it logging any incoming connection attempts?

You mean packet logger? Try Ethereal.

I still use floppies, for transfers of small files and other things that are too small to put on a CD. I still have a large box of them containing various older programs and data... and I'm one of the few to have a 2.88M drive and some diskettes too. I still have a 5.25" drive in my system between the DVD±RW and the CD-RW, and I'm trying to get an 8" floppy drive installed to read some *very* old 8" floppies someone gave me... I like full backwards compatibility

Probably your mobo doesn't support that much RAM then... and you're using a highly modified version of 98se too... my success with 2Gb was on a nearly virgin install, with only MaxFileCache=524288 and some other customisations that have absolutely nothing to do with RAM (changed color scheme, explorer view settings and context menus...) Are you using any Win95 system files? I know that is a common modification - to replace some Win98 components with Win95 components. That might be the cause of this as well.

Don't worry about DOS support. DOS 7 will run on anything newer than a 386 since it does not deal directly with chipset/video/other hardware, rather it uses the BIOS to do so.

Custom Build: CPU: Pentium 4 Mobo: Lintech ??? VIA chipset (the only English words on it, the rest is in Chinese...) RAM: Generic HDD: Western Digital Case: Generic

They also have to be stronger to withstand the forces of 10,000 RPM rotation.

You are very wrong. If you read my previous post you would've seen that I was able to, for 3 months, run 2Gb of RAM on a (nearly) stock install of Win98se with absolutely no stability problems. The official value recommended by Microsoft, and the one which works perfectly well, is 524288 = 512 * 1024. Why not just physically remove the RAM? That has the same effect - namely, making the area above 1Gb non-existent. What we are concerned with is whether or not Windows will use more than 1Gb, and in my experience it is definitely possible.

Your fan bearings are dying. What you need is a set of new ones.

I think Longhorn sounded better. Or even "Windows 2006"... Vista sounds very generic and boring...

2Gb with borrowed RAM for 3 months with no problem here I'm going to see if I can borrow another gig and try 3GB, since that's what my mobo claims to support. The addressing limit of every CPU since the i386 was 4Gb, but the design of the PC architecture limits it to approximately 3Gb of physical memory. The upper 1 Gb is reserved for I/O ports and other miscellaneous items.You don't need the unofficial service pack to work with lots of RAM - it's all in the MaxFileCache setting. A stock install of 98se will work as long as you set MaxFileCache=524288 or less.

First of all, your laptop is going to feel warmer. Maybe even a lot warmer. Make sure you have an adequate thermal solution. Laptops don't have much ventilation in their cases. For the bridging jumper, you'd need a very fine piece of wire, approximately the width of a hair. If it's too thick the pin won't go into the hole with it. It is possible to break the pins, so be careful. (I've heard that Celerons tend to be very overclockable... myself having a desktop 2.4GHz unit that's now running at 3.6 with stock cooling for over a year now)

Because the ultimate limit is how fast the data is read or written to/from the disk platters, which spin at the same speed on sata or pata hdds. This limit is much lower than that of the interface itself.

A special-purpose disk-eraser. Here's one: http://killdisk.com/