dencorso

Well, thanks to jaclaz (and eidenk), I now know of an ext2 driver for Win 9x/ME: FSDEXT2, by Peter van Sebille, latter revised by Gerald Schnabel. The last revision of the driver is here: fsdext2_0163.zip and its source is here: fsdext2_0163source.zip. It claims explicitly to support Win 98. So, please, do test it. I'll do it myself as soon as a proper opportunity presents itself.

What downgrade are you talking about xRayeR? NUSB uses Win ME USBSTOR.SYS (v. 4.90.3000.1) since NUSB 3.1 and up to 3.3, so there's no downgrade in it (read again the 1st post in this thread). Check for yourself, here are direct download links to two bona fide sources for it: NUSB3.3 (at MDGx) and NUSB3.3 (at technical-assistance.co.uk). What version of USBSTOR.SYS were you using that suddenly stopped working? If you mean USBSTOR.SYS (v. 5.0.2195.6655) from NUSB 3.0, it also needs WDMSTUB.SYS, also from NUSB 3.0 to work. To install it, you might just drop WDMSTUB.SYS from NUSB 3.0 in your %windir%\Sytem32\Drivers directory and edit the line in USBSTOR.INF that reads:HKR,,NTMPDriver,,USBSTOR.SYS to read, instead: HKR,,NTMPDriver,,"WDMSTUB.SYS,USBSTOR.SYS" and redetect all USB devices. You can get NUSB 3.0 (here). Observe that all the links in this post are for English versions of NUSB, but WDMSTUB.SYS is language neutral.

Here's a true SSD: RunCore SSD 128 GB (mini-PCIe SATA) on Asus EeePC 900 (Win XP SP3) FAT-32 -------------------------------------------------- CrystalDiskMark 2.2 © 2007-2008 hiyohiyo Crystal Dew World : http://crystalmark.info/ -------------------------------------------------- Sequential Read * : 126.5 MB/s Sequential Write * : 81.3 MB/s Random Read 512KB : 120.7 MB/s Random Write 512KB : 63.2 MB/s Random Read 4KB : 16.3 MB/s Random Write 4KB : 2.0 MB/s *Test Size : 100 MB And, below, I quote some other older data I obtained with Gavotte Rramdrive and the Gigabyte i-Ram, on my main desktop (overclocked Athlon XP-M 2800+ @2415 MHz on an ASUS A7V600-X with 3 GiB of DDR RAM @256 MHz): As you can see, both our results on Gigabyte i-RAM compare well. The direct comparison between ramdrives is not fair, however, because mine is on underclocked DDR RAM, while yours is on full-tilt DDR II RAM and presumably on a much faster bus... But, anyway, on every hardware, the ramdrive wins, as expected.

I don't know of drivers for Win 9x/ME, but for the NT OS Family there are, at least, Ext2Fsd and Ext2 IFS for Windows, both freeware, and WDM.

Well, there is Inside the Windows 95 File System, by Stan Mitchell, available used at amazon.com at affordable prices. It's very comprehensive, and unique as a source, AFAIK. An one of the examples in the companion diskette is fsinfile, that implements a file system within a file, as a remote filesystem.

Enough! ModifyPE gives that error if you try to run it under Vista. It's known since 2007, and never resolved, up to now. See this post, over at siginetsoftware. You may try PEChecksum, from the CodeProject, or you may try the old freeware PEChksum v0.99.0, from Bitsum Technologies, findable inside the PESuite. I cannot guarantee either Bitsum PEChksum or PEChecksum from the CodeProject will run OK in Vista. It's up to you to try them and report your findings.

There's no hurry to do it, so take your time. I see no need to reformat, however. Moreover, reformating per se wouldn't change anything, since the problems identified are all in the MBR. You'd have to repartition and reformat. But, just by repairing the problems found by jaclaz, through editing those three bytes as described by RLoew, you pendrive should be fine again, so repartitioning and reformatting seem to me a bit of overkill. Moreover, anyone of us might do it for you in the MBR image you attached and attach it back, so that all you'd need to do would be to write the MBR sector back, using HDHacker (just make sure you are writing to the right disk, before actually doing it).

UDF is the best possibility. Multibooter is experimenting with it. ext2 (or ext2fs, one of the linux fs) is another possibility, supposing DiskInternals Map Drive works. Neither seem to me very good options, though.

So, a longer text would cause the production out of nowhere of the pre-existing text "Windows is loading files"? At first sight seems to me more like a conjuring trick than a "programming error". True. So the explanation must lie elsewhere. My guess is: Tripredacus is right when he says the text must have the same number of characters. If it wasn't so, it'd have been translated into Portuguese by Microsoft. If they left it in English, they probably had a reson for it, and the size of the translated string might well be it. And you're right in saying it cannot cause the string to revert to English by magic. But it can cause the edited file to be recognized as damaged and make the system get a backup pristine file from elsewhere. There's nothing uncanny to it, IMHO. BTW, yes, "O Windows está carregando os arquivos" is a correct translation into Portuguese of "Windows is loading files". Then again, "Carregando os arquivos ", with a trailing space has the same 24 characters as the string in English, and is a good enough, although not literal, translation, too, and might just work.

That's your pendrive all right! Now, one problem I can already see: the MBR has a single partition of type 1B (which means a hidden FAT-32 partition), no wonder nothing gets mounted. It ought to be changed to 0B. This is easy to solve, but I'll let jaclaz suggest what app you should use to solve it. I'd fix it with an hexeditor, but there are many less dangerous ways to do it.

If I'm not mistaken, there's a thread about WIA in the 9x/ME forum. Maybe looking at how it's done for 98 gives you some idea of what you'll have to do for 2k. Just a longhshot but, then again, there might be something to it. ... Found it: WIA for 9x/ME! I guess you'd need both XP WIA and PTP. BTW, did you check ptpusb.inf, ptpusb.dll, ptpusd.dll, and sti.inf and ptpusb.inf for missing dependencies? And, are you sure all of XP PTP is installed solely by ptpusb.inf?

It can mean it's a different compilation of the same source. Or so minor a update that warrants no version number change. As it's impossible to decide which, it's usually best to stick with the newest version. And, when in doubt, you can always use MiTeC EXE Explorer to find out the real (unless it's been deliberately spoofed, which is unusual, as it's not a very well known feature) compilation date, the "PE Timestamp" of any Win-32 executable.

I second that! µTorrent rocks!

Welcome onboard, jaclaz! Your expertise is much needed here! As for your suggestion to LoneCrusader to start a new thread, it's no longer needed, for I've just split all relevant posts into its own new thread.

The discussion about Strange Problems with Pendrives, which was started by LoneCrusader, is now split into it's very own thread, and you all can find it here: link.

With VID = 0951 PID = 1603 and a Skymedi controller, yours is a bona fide DataTraveler, so my suspicion it might be an el cheapo contrafaction turned out to be wrong. However, it may be formated as FAT-32 but may have a XP boot sector and/or Boot Sector (PBR). That might possibly be the problem. You may correct that with MBRFix, take a long breath and delve into cannie's tutorial, looking for info on MBRFix and its use. Also you may search the forums for posts by jaclaz on MBRFix. Give it a try, with MBRFix you may substitute the MBR and PBR, without having to reformat.

It's unrelated. But RLoew has released a freeware fix for the DVD issue. You can get it at his site: RLoew's Software Homepage. As for the pendrive, I'd suggest first you try the fix I suggested two posts above. If it doesn't work, save the 2GB of data elsewhere and accept Windows offer to reformat it. If it gets working again, OK. If not we can look deeper at it. Good luck.@RogerOver: ChipGenius doesn't work well on 98 anyway, but it even might detect the VID and PID for you, all the same, but it didn't. USBVIEW.EXE v. 5.1.2600.2180, available at MDGx's, on the other hand, works OK under 9x/ME and can tell you the VID and PID, too. Do try it. Unless the pendrive isn't getting even mounted, it should work.

But, then again, one could set a global policy not to check digital signatures, and then get rid of all .CATs. Just go to Security Settings/Security Options/Devices: Unsigned driver installation behavior and change this setting from "Warn but allow installation" to "Silently succeed".

For what it's worth, on the ASUS EeePC series, <Esc> gets you to the boot order menu and <F2> takes you to the full BIOS configuration menu, as in most ASUS boards. While <F2> is an easy guess, <Esc> is an unusual choice, not being an "F" key.

@RogerOver and LoneCrusader: Before anything, apply KB240075 UHCD.SYS hotfix and see whether that solves your problem. If that's not enough, post here the VID and PID of your Kingston pendrives, and we'll see what can be done. ChipGenius http://www.mydigit.cn/mytool/ChipGenius.rar, run under Win2k/XP (not under Win98), is probably the easiest way to find out the VID and PID of your Kingston pendrives, BTW.

Sure. vbemp9x (direct download). Note that the link I just provided you is bearwindows original russian download site, that remains active, as usual. @iWindoze:bearwindows has a subforum over at boot-land: bearwindows (as already mentioned by jaclaz), and a new site BearWindows Vault. He's a member here at MSFN, but comes here rarely, and is easier to find at boot-land or by e-mail (findable at his site). @jaclaz: Reocities! Indeed! Great news! Thanks for the heads up!

Your precaution may well have saved some of them from oblivion. Myself, I was taken by surprise, so I've searched around the net since HP's withdrawal of the drivers from their site, looking for alternate sources for them, and I've found two places which together still offer most of the missing HP drivers: 9x/ME PrinterDrivers and oldwindowsdrivers, although I cannot say for how long they'll remain active.

Welcome onboard! You've got a nice place at eng2ita, too... it's a pity I can visit there only from time to time.

Aren't that to be expected? They're being much more gentle than HP, that one day yanked all 9x/ME drivers from download all of a sudden.

Sure. vbemp9x (direct download). Note that the link I just provided you is bearwindows original russian download site, that remains active, as usual.