Hey all you Win 2k gurus - how 'bout a hand?

[zepper]

Hi all W2k Owners. I've been trying to reinstall W2k and the CD I have is acting strange with hangs and such. I know my hardware is OK as I run Linux (both Live CDs and installed) and W98SE with no problems. memtest and prime can run for a day or two without any problem. A funny thing is that I don't seem to get the same total bytes on the CD for about any method I use - verrry strange... Anyhoo, here's what I get when I use the Properties in Win Explorer on it: 389,677,056.
. Anyway, the CD I have is a retail one (not OEM anyway) with SP3 integrated. The file dates are 7/24/2002 at 12:00:00 PM. I was wondering if anyone would be willing to run either a checksum or an MD5 hash against their CD and post the results here (or attach it to an email for me). That way I can confirm that my CD is OK. I will be glad to either send you the little DOS program I use to run the checksum as an email attachment (but apparently there a a few files on there that are too big for it to read or something), or here's the link to the MD5 hasher program: Linkage .
. Does anyone know if there is a list of checksums or hashes on the M$ site for each of the CDs they made? That would certainly do it.

.Thanks!
.bh.

[sm8000]

My 2000 CD with SP3 slipstreamed (from MS) shows 391,917,568 bytes.

I also have this CD copied to a folder on my hard drive, what's the command to get the hash for either it or the CD itself? Here's a shot of an attempt on the local folder, not sure if I did it right....

[zepper]

Thanks, but that just got the root folder. Here's the syntax:

fsum p:*.* f:name /R where p: is the path to the files to be hashed and f: is the path and file name for the hash log file to be written and the /R parameter recurses the subdirectories.

The size of my hash log file was upwards of 360kB...
. And what are the file date and time on your files?

Thanks again,
.bh.

[sm8000]

Calculation summary:
Processed 6181 files in 194 folders with total size 365.73 Mb.
Elapsed time: 00:01:16 Average speed: 17.00 Kb\Sec.
Result written in c:\hashlog

My file date/time shows the same date, but at 8:00:00 AM. My hashlog.txt is 352k. I've just emailed it to the "Email Me" address on your webpage.

Bear in mind I couldn't run it against my (burned) CD, so I ran it against my local folder.

[elroy]

Don't ask why because I haven't a clue but my Win2k would hang also UNTIL I disabled the USB in the bios. Then after installing Win2k I turned the USB back on and everything was ok.

[zepper]

Thanks SM8000 - it looks good. Of course now I won't be able to do a simple FileCompare on the two files as yours has the 8:00 am time so I'll have to do a Search & Replace first...
. That's a pretty cool little MD5 hasher program, isn't it? If you have interest in such things, KarenWare also has a Hasher program and her DirectoryPrinter program also can do the MD5 hash on each file as well as lots of other neat stuff. Free for the DLing...
. If you know of any hasher program that can do a whole CD or drive letter resulting in a single cumulative MD5 hash for the whole shebang, please LMK! I know I could do an ISO on a CD and then do the hash on that, but it's a PITA...

Thanks elroy!
. I'll try that too if I don't find any corrupt files. USB was pretty new when W2k came out, so I can imagine it might have a problem with some of the new USB that's out there now and isn't in its driver database. I think I installed this before without any USB problems - but now that I recall, it may have been on a different mobo.
.bh.

[sm8000]

Thanks for the link zepper, looks like some neat stuff there - glad I could be of help. Hey elroy, was the USB you disabled 2.0? Because Win2k was the first OS (from MS anyway) to have USB 2.0 drivers written for it, though I'm not sure they'd have been in the original driver package. They ought to have been by SP3 though.