dencorso

Don't worry! It's just an open -5V. This quote from one thread elsewhere seems appropriate:

Of course. But I think it'd be even more intrusive than adding a command-line switch to control whether it's case sensitive or not. Myself, I see case-sensitivity in yanklines more as a bug than as a feature. But I grant it may be useful in some select cases. All in all, I think the two versions of the script, as proposed by jaclaz, and which I've adopted already, by far the best solution.

Sure. NUSB35e is the english version of latest version of Maximus Decim's Native USB drivers for Win 98SE. Another thought: your board is said to have USB 1.0 support. Although any current USB 2.0 pendrive does support USB 1.1 and 1.0, the motherboard may come with some blorked version of USB 1.0 that's too much for the pendrives... and, in any case, is way too slow. Consider adding an add-on PCI USB 2.0 card (preferably one that adds 4 ports), if at all possible.

Welcome back to the fold!

Done. Thanks!

Doctor Ammondt - Esír Kušzagìnna (Blue Suede Shoes in Sumerian)

NUSB35e MD5: 86073921EBDAB9B75F4F50847E85CEFE CRC32: 6CA5320E

First of all: Disable "Antivirus Protection" on the BIOS, at least while you work on the disk. That option prevents one from modifying the sector 1 ( = LBA 0), and causes a lot of grief until it dawns on one it's set. As for partitioning, I do recommend The Ranish Partition Manager v. 2.44. Notice that it's a program that causes strong emotions: people either love it (as I do) or hate it... Do a forum search for "Ranish" and set the seach engine to return posts not threads, and you'll see what I mean, and also will find numerous posts about how to use it. One of those posts is the one I quote below, that summarizes the existing options. The Ranish Partition Manager, although it is not adequate to format the partitions it creates, because of defaulting to 16 kiB, still remains the best free partitioning tool. Nowadays, I'm convinced v. 2.44 is the best one to use. However, until recently, the only free formatting tool I knew of that's capable of reformatting using a user defined sectors-per-cluster number, regardless of how the partition was originally formatted, was Ridgecrop's fat32format (which is needs a NT-family OS to work), since the undocumented /Z switch of the MS Format refuses to work. This may have changed, thanks to Udo Kuhnt and his DR-DOS/OpenDOS Enhancement Project! As an afterthought: I'd give that machine a Pentium III (it's faster and has SSE). Nowadays it's quite inexpensive and you can probably find one that's a pin-to-pin compatible drop-in replacement to your current Pentium II.

With all due respect , the idea of updating is generally to "better" in the sense of "adding features/choices" or correct "wrong" behaviour, wouldn't it be more desirable to have a /I command line parameter/switch (not entirely unlike the batch IF /I one)? (or reversing the default a /CS one)? Yes, I considered that. However, I do think the case-insensitive behaviour is in line with the general behaviour of both DOS and Windows (FIND is an exception, there must be others...) and generally more useful. Now, since to restore the original case sensitive behaviour of the script is just a matter of changing a single "1" to "0" inside the script (and it's documented by a comment at that point), I decided adding a command-line parameter to control it would be an overkill, since it would entail many lines of code for a robust parsing of the command-line, which would add unneeded complexity to the code. That's just my 2 ¢, of course.

Since I think the case-insensitive version is more useful than the previous one, I've updated my original Yanklines.VBS post, to reflect this. Thanks for calling my attention to the problem!

Well, that settles it. ICH-4(-M) Southbridges do have USB 2.0 hardware support all right. And drivers are installed for it, too, since the device manager displays:

Cat Stevens - O Caritas

Locate this: Set objDict = CreateObject("Scripting.Dictionary") j = 0 and change it thus: Set objDict = CreateObject("Scripting.Dictionary") objDict.CompareMode = 1 'Text i.e. case insensitive j = 0 I'd also keep the "cmd /c" instead of "cmd /k" like you did in your first post, in addition to using hidcon. PS: setting: objDict.CompareMode = 0 'Binary i.e. case sensitive would restore case sensitivity. However, making it case insensitive does not ensure a consistent casing... Your example above results in: CopyFiles = System32.files CopyFiles = Fonts.Files because always the first occurence is the one preserved, regardless of casing, so do take care.

Do you know what motherboard is it you machine has? Of course pointertovoid is right: it may not actually have USB 2.0 hardware. NUSB 3.5 surely gives you the software drivers to use USB 2.0 hardware, provided it be available. Right-click on My Computer, go to Properties, then Device Manager, then expand the Universal Serial Bus controllers hive, take a screenshot and post it please.

Follow the advice on jaclaz's post #16 (and #18).

Read this. FILEVER is the reference, see post #24. Getver, which is no good for the NT-Family OSes, may be useful, if you're interested *only* in Win 9x/ME.

+1. Liquid Nitrogen should be enough, though, and it is way cheaper. Then again, MSFN is definitely not the place for advice on how to do it.

The Electric Prunes - Kyrie Eleison

Elvis Presley - Jailhouse Rock

Hey, folks! Take a look at this! Isn't it a starting point to become sort of the SYSTEM user in Vista+ NT-OSes?

Dependency Walker gives false results for WDM drivers on 9x/ME. It'll always show dependencies to one of or both hal.dll and ntoskrnl.exe, which are NT-OS only files. There are four known compilations of WDMSTUB.SYS v. 5.0.0.6, AFAIK: 1) PE TIMESTAMP Wed Jun 11 22:05:16 2003 (3EE7D1CC), 20480 KiB, MD5 69309403061DD2953D402015B6E4EFB1 is a debug build compiled from the source provided with W. Oney's Service Pack 3 to the WDM book 2nd Ed. (released June 12, 2003); 2) PE TIMESTAMP Wed Sat Mar 15 09:16:46 2003 (3E7319AE), 11520 KiB, MD5 3AA89DDB2B5FE621E0EB11F9D1FFBD39 is a release build that comes with some Honeywell drivers; 3) PE TIMESTAMP Wed Thu May 22 10:55:15 2003 (3ECCD6C3), 11520 KiB, MD5 1D7284E0F3CB98A189F0AC17C3F13337 is a release build that comes with the Garmin USB GPS drivers; 4) PE TIMESTAMP Sun Sep 24 19:05:20 2006 (45170120), 12767 KiB, MD5 9AA0AEA685F135C9D1409F8E3E5ADD10 is a release build that comes with NUSB30e. While the first three are functionally identical, despite being clearly different compilations, with some different optimizations, the fourth is an updated version that exports one more function. It is the one in general use and it is the most up to date one that I know of, and, of course, it shouldn't be versioned 5.0.0.6... And to answer the question you posed: yes, they're only used in NT-OSes.

You bet! CrystalDiskMark22_9x Sure. In the Members Projects Section, all right. And start by giving a detailed description of the hardware, including make and model of the motherboard, so we can hunt it's manual somewhere and add a link to it, for the convenience of all interested in participating in the thread. Let me suggest a title: "Resurrecting a 1999-Vintage Win98SE Machine". Do get yourself a disk imaging solution, to preserve images of every major step, it makes life much easier: either the free Partition Saving or the inexpensive Norton Ghost 2003 (which you'll find over on e-Bay or similar places).

Among the traditional XMS ramdisks, XMSDSK 1.9I by Franck Uberto rulez! Forget any others. The Gavotte works only under the NT-Family OSes, there's no version compatible with Win 9x/ME. RLoew's non-XMS ramdisk (link) is the only one of its kind, and it's not free, but if you can afford it's cost, it surely is the way to go. In a machine having 3 GiB of RAM, it'll allow you to use a 2 GiB ramdisk with 1 GiB RAM left for Windows. It's great!

It's not required nor implied, but is understood and will work. Either EMM386, or any of CEMM, 386MAX, QEMM or NETROOM. None are good ideas with Win 9x/ME so, if you cannot live without UMBs, and have an AMD based machine, the best solution (which is not so good) is to keep using EMM386. If you have an Intel based machine, UMBPCI is the way to go. HIMEMX has some bugs (at least four, I think, but I'm not finding my notes on it), but none are really serious. I don't think it'd cause any problems in Real Mode DOS. The problems it may cause in windows were already described by RLoew, some posts above.I think this answers the questions your experimentation hasn't already answered. Now, enough of thread hijacking. If you want to discuss anything outside the scope of this thread's title, please do open another thread.

Yes. a XMS ramdrive will wind up using memory from the System Arena, which is limited to 1 GiB and is also used by the DOS boxes, VCache and all the OS Ring-0 components (drivers, VxDs and the kernel proper, and some hardware like the graphics aperture of AGP video cards... so, at the end of the day, one'll not be able to use much more than about 350 MiB for the ramdisk, else crashes follow. A Non-XMS ramdisk does not use memory from the System Arena nor anywhere inside the memory managed by windos, and can be as large as 3.5 GiB, without any problems.