dencorso

It's a typo. tomasz86 missed a letter. He meant: %systemroot%\INF, of course, which is the same as %windir%\INF.

I think jaclaz would suggest getting the DSFOK utilities and using something like the following command sequence (under XP): fsz zeroes.000 51200 dsfi \\.\PhysicaldriveN 0 0 zeroes.000 dell zeroes.000 where N stands for the Physicaldrive number.

So, it's Kelly Theriot you're asking about!

Yes, you do. By using sed (and perhaps unix2dos to correct the line terminators depending on the implementation of sed you choose) almost any modification one can conceieve, however complex, can be performed fast. I put yanklines together to remove dupes fast, in a file, which is very far from the things sed does well. But while you want to reformat individual lines, one by one, no other tool is needed since sed is very powerful and time-proven. sed can be used as a filter, just like FIND. # delete leading whitespace (spaces, tabs) from front of each line # aligns all text flush left sed 's/^[ \t]*//' # see note on '\t' at end of file <...> USE OF '\t' IN SED SCRIPTS: For clarity in documentation, we have used the expression '\t' to indicate a tab character (0x09) in the scripts. However, most versions of sed do not recognize the '\t' abbreviation, so when typing these scripts from the command line, you should press the TAB key instead. '\t' is supported as a regular expression metacharacter in awk, perl, and HHsed, sedmod, and GNU sed v3.02.80. Reference: sed1liners

Well, VxDs are LE not PE files. I wrote VxDVer to help handle them under XP, I'm sure you'll find it useful.

+1. Driver Cleaner Pro 1.5 is precious!

New version! No tally yet, but a better output: If no command-line switches are given, only the non-matching checsums files are listed. For the various alternatives use /? or -?. Please test. VRFYPE2.7z

I guess you missed this part of my post, which is the more relevant, since it refers to a freely downloadable (true) DOS app. It uses native ATA commands to do the same that HDD Low Level Format v2.36 does, but in much less time, and more thoroughly. Do dowload it, read the documentation and test it, Multibooter! I bet you'll be impressed.

And that's why I recommend the PETimestamp, which is difficult to change, as the control date, instead of either of the three dates from the directory entry. Here I described two different oleaut32.dll V. 2.40.4519.0, while here is my tool for reading the PETimestamps.

Not easily, no. This kind of thing is better done with sed. sed is unix, of course, but there are countless ports of sed for Win32. I like the cygwin version, but that needs also cygwin1.dll, so probably something based on mingw may suit you better. And sed is very powerful, so I do think you should invest the time needed to get familiar with it.

True. But my reasoning was a 2 TB HDD is more useful if put to use for backups and the like... unless it's a spare part held in reserve for future use. In any case, the only expensive hardware I recommended is the Super Talent USB 3.0 Express RC8, which is a really notable piece of hardware, and probably the best pendrive for booting, right now, due to its outstanding 4 kiB random-write speed. While not as good, a 32 or 64 GB Kingston DT Ultimate G2 (or, much better, but hard to find nowadays, the G1, that also used an SSD controller), would do fine.

You also need HDDErase to zero-out the full 2 TB HDD faster than you can say Presto! twice, so you can start from scratch from time to time; a really fast 50 GB USB 3.0 pendrive based on an SSD controller, which reports being a non-removable device and can also run on USB 2.0, if needed. And an Express Card to USB 3.0 adapter, to help speed up things some more. A 50 GB pendrive is big enough for your tests and will allow you to do them more confortably then using such a big HDD, IMO.

REG.EXE is the windows NT-family command-line registry editor. Take care. The registries of the NT-OS family and of the 9x/ME family differ considerably in their internal-structure. I'm really sorry I cannot back-up the above statement with a reference right now, but I recall discussions from way back when about this. But I'm sure jaclaz, when he reads this, will have some references for it, since he also participated in those discussions, if I'm not mistaken.

Or UltraISO... or even... oscdimg.exe!

Try: sudo mkudffs --media-type=hd --blocksize=512 /dev/sdb1

+1. It makes sense.

Well, just after the line "copy fdisk.exe" , insert a new line with "pause". Those commands, of course, go into the batch without the qiotation marks.

Where you had put "copy fdisk.bat %RAMD%:\ > NUL" put instead "copy fdisk.exe" (and watch out for the message from copy, whether it is "1 file copied" or "file not found"), then, where you had put "call fdisk.bat %RAMD%" put instead just "fdisk". Test and report.

The above quotation is from this page (preserved by the Internet Archive).

Yeah... that's a really old issue that remains with us... I've given up enumerating like a)... Now I always do I), II)... or i), ii)... or a. , b. ... I'm sorry, but I wouldn't hold my breath waiting for it to be fixed.

What about a DDO that reads a GPT device and presents it to 9x/ME/2k/XP as a 4 KiB (or maybe 2 KiB) sectored FAT device? Wouldn't that solve all problems at the same time? Of course, a DOS patch would be needed, too, for 9x/ME.

This topic has been updated! What's New? on post #2: RLoew's #2 machine has been updated. Now it is the new RAM record holder for 9x/ME: 32 GiB RAM onboard! Let's keep the list up-to-date: If you are using 9x/ME with more than 1 GiB RAM, do PM me your info and you shall be added to the list!

Getting Win9x/ME and 2k/XP to understand and use 4 kiB sectors, in a manufacturer agnostic way, seems to me one of the most pressing projects, ATM, since 3 TB HDDs are already out there.

BTW, did any of you all notice the deja vu in the new logo? >===>

Ditto! As far as I know WriteUDF! is no longer available and, BTW, the Software Architects, Inc. is no more, AFAIK. Did you find an alternative?