dencorso

dencorso you add them to the list? All Sony devices in the XP SP3 USBSTOR.INF are present in the NUSB 3.3 updated USBSTOR.INF, plus there are two additional Sony devices not present the XP SP3 USBSTOR.INF... They were added by MD himself. The Casio camera, however, requires QV2KUX.SYS, a driver not present in NUSB (any version) and presumably not compatible with 9x/ME, until proof to the contrary. So, no, the Casio camera is not there. BTW, it's the one device present in the in the XP SP3 USBSTOR.INF and not present in the NUSB 3.3 updated USBSTOR.INF. The latter, however, has lots of devices not present in the XP SP3 USBSTOR.INF, being, thus, way more complete.

Either VT6202 or VT6212 are safe bets compatibility-wise. Then again, once you're looking for 9x/ME compatibility, performance should be secondary, but the VT6212 should be the best overal choice.

Sure. They're like water and wine. Search for all posts by PassingBy and read those regarding NUSB, and you'll get a better idea of what I'm talking about.

Description: VBscript to remove duplicate lines from plain text files. Programming Language: VBScript Usage: YankLines <input_filename> <output_filename> Well, I claim no originality here at all, all I did was performing some pretty basic good housekeeping, and joining pieces of great code written by others... I needed a program to remove duplicate lines from lists which I update by appending, such as the HOSTS file and some log files. These are too long to clean up by hand. I searched and found an awesome VBScript program, by Max Damage (at MS Technet's Script Center), that does it fast and reliably (reference: Remove Duplicate Lines From a Text File)... however it's not quite user friendly, because one has to modify the code each time it's used, because the filename is hardcoded in the script. So I added some quite standard code for it to recieve the source and output filenames from the command-line, to resolve this problem, and incorporated cluberti's clever subroutine RunMeWithCScript() to avoid getting lots of pop-ups from wscript. And that was it. But it works so well that I thought I should share it with all other users needing such a program, because I really didn't find anything like it free and readily available on the net. [Later edit: Thanks to tomasz86, the code has been improved: it turns out that the first posted version was case-sensitive, which, IMO, is undesirable. So, I've updated the script to correct this (just one more line added, including a comment on how to reverse it, when necessary). One page from the MS 2k Scripting Guide (Configuring Dictionary Properties), where the subject is further discussed is the relevant reference for this. Thanks also to jaclaz, for suggesting the alternative yanklinescs.vbs (case sensitive version), now added to the attached .7z. For the source of these improvements, see this thread.] Together with yanklines.vbs, in the attached 7z file, there is also believe.txt, a nice test file I copied from How Can I Remove All Duplicate Lines From a Text File? (by the Scripting Guy), which also presents another interesting way of solving the problem of the duplicate lines (which I didn't actually test because I'd already solved my problem using yanklines.vbs). yanklines_v3.7z

Can you attach a picture of the mobo indicating the position?

VID order is not mandatory, AFAIK. But if you have time for it, please do revise the usbstor.inf, for there are other items out of VID order, zip and attach it. Look for USBVIEW.EXE v. 5.1.2600.2180 at MDGx's. It runs OK both on 9x/ME and XP, and allows one to determine VIDs and PIDs, if that's what you're looking for. HTH.

Way to go, diskless! You rock! The updated usbstor.inf, for those who wish to test it, is in post #554, below.

I think, JorgeA, that it would replace the HOSTS file created by SSD during Immunization. Right now I'm not quite sure whether Immunization only creates a HOSTS file or if it does more things in addition to it. However, I, myself, do not swap HOSTS files. I make a backup of my current one (which I know is working well), then merge the new URLs to the old file, a time-consuming task I perform using Beyond Compare, so I don't do it as often as I'd like to. Then, I substitute the new one for the old one, keeping my eyes wide-open to hunt down any URL that may prevent my accessing places I trust (it's rare, but has happened in the past). As always, YMMV.

Quite true. And the best independent HOSTS file for this use is findable here.

Yes. Add the two lines DEVICE=C:\WINDOWS\IFSHELP.SYS DEVICE=C:\WINDOWS\DBLBUFF.SYS to config.sys; Then set BootGUI=0 Logo=0 in MSDOS.SYS. Your system will now boot to true DOS. In order to get to Windows, run win.com.

Apply Q311561 first, and then use the time-proven Reines [MFD] Patcher.

No. Use the free version of Active@ Kill Disk to fully zero it out. Then repartition and reformat. And let's see what happens. In case the pendrive is OK, this will get it pristine once again.

Unless you really need to use files > 4 GiB, stay with FAT32. Compatibility, IMHO, is the decisive feature.

Yes, but the one you can get at MDGx's is a newer version, although the one you've already instaled might be good enough. And, since RLoew says it at least seems to work, if v. 2.0 of the d-link driver doesn't solve it for you, you might as well try using the NTKERN.VxD from 98SE with either d-link drivers you've already got, before going fishing for older ones. You should use NTKERN.VxD v. 4.10.2224, which is part of KB288430... extract it from the hotfix and just drop it into C:\WINDOWS\SYSTEM\VMM32 (if you have a NTKERN.VxD in that directory do backup it first), and then reboot. Do *NOT* try this with the 98SE VMM.VxD that also comes in KB288430 or it'll cause your system to become unbootable (the VMM.VxD versions are really version specific!).

Since you really have 1.25 GiB and use Win ME, try adding to your system.ini: MaxPhysPage=50000 ; 1.25 GiB Read this: Offler on MaxPhysPage I'm suggesting you just put a directive limiting the available RAM to all you've got, which should be perfectly useless, but seems to be of help, both in what Offler reported and in my own experience, although I did not investigate it further at all, and both Offler and I observed this on 98SE.

I doubt Win 98SE ntkern will even work with Win 98FE. I'd go for 2.0 first, and if it doesn't work either, fish for an even older driver. I have really limited experience with 98FE, but I'm sure WDM drivers is the one place it differs most from 98SE. It's too bad PassingBy isn't around lately, because he's the real expert in those matters. If perchance you're reading this, PassingBy, please do chime in. But I'd bet one of the older drivers will eventually solve your problem. Also adding the update pack for 98FE might be of warranted here.

Big HDD & 48-bit LBA Thread Index (On using HDDs larger than 137 GB (128 GiB) with Win 9x/ME) STFF

@CrazyDoctor: Your first step should be to find yourself a lucky charm! I've never ever seen any one user so unlucky with HDDs as you are (you've got at least 6 problematic HDD's in just 3 months, if I'm not mistaken), judging from the number of HDD-problem threads you've started of late!

Yeah, thanks! The problem with setver.exe is that it loads too late to fool COMMAND.COM, while my driver can fool it all right. Wendy knows a lot about DOS, especially the latest versions... she may well be right, but there's lots to be learned about v. 8.00, still. And RLoew's decompressor opened up a novel window of opportunity to investigate the v. 8.00 IO.SYS, so interesting developments should be forthcoming.

Did you search using the Wayback Machine?

Well, since you're working with Win ME IO.SYS, here's something you may find interesting: a spoofing device driver that allows one to use MS-DOS 7.10 files with Win ME IO.SYS. All it does is to trap the IO.SYS replies to Version queries, changing its reply from "8.00" to "7.10". This permits to take advantage of the fact that Win ME IO.SYS already contains HIMEM.SYS, in creating a real minimalist boot disk. To use it, load VER710.SYS early from CONFIG.SYS (that is, put DEVICE=VER710.SYS as the very first line in CONFIG.SYS), and you're all set! Notice that you can accomplish that by directly patching an uncompressed version of Win ME IO.SYS, but this allows one to use also the compressed versions, which cannot be patched, unless someone creates a recompressor for IO.SYS. BTW, you'll certainly find this Boot-Land thread of interest, if you don't already know it (I suspect you do, but, in any case, here's the pointer just for the record). VER710.7z

The IO.SYS extracted from Windows XP SP3 diskcopy.dll can be uncompressed without any transplant from other files, and works OK both in the original compressed form and in the uncompressed form, AFAIK. Why did you find it necessary to transplant the initial 2k block? Please elaborate on it. Later edit: Now I understand... You mean to restore Win ME Real-DOS ability, as per this patch, right? My guess is it would be easier to collect Win ME COMMAND.COM and REGENV32.EXE and the IO.SYS extracted from Windows XP SP3 diskcopy.dll, and apply to these files their patch directly, and then use RLoew's IO8DCOMP.EXE on IO.SYS.

Let me guess: your only problem now is the D-Link dongle? Well, trying various different drivers usually solves it. Serach the net for them. D-Link Australia, New Zeland and UK all offer diferent drivers. And their sites are a PITA to find things in, sorry, but they usually actually do offer the right drivers somewhere. Here's a start: v2.04 (AUS) and V. 2.00 & v2.04 (USA). V2.00 may be what you're looking for.

Good bookmarks, better searchword choices and even better memory. ...But I'm just an amateur at it: jaclaz can beat me in this game hands down anytime! The latest certificates are always obtainable from this direct download link. And while I don't have the *slightest* idea of how to determine the date of the certificates you already have in your system, I do know how to determine the date of rootsupd.exe: just go to properties and check the date of its digital signature! And the one you can download form the above link (which has 336,280 bytes) is from May 03, 2010.

Even if it's not an answer to your questions, you might find this thread interesting.