dencorso

jumper, would you be so kind as to make ImportPatcher compatible also with XP and 2k? I can envisage many uses for it on these two OSes, too. However, it always hangs and never finishes, when I try to use it on XP SP3. If set to Analyse, it hangs silently, after producing the ini and the log (I have to kill it, to terminate it). If set to Patch, it hangs before actually patching anything, and I get a box with an exclamation point saying: "Debug: CreateFileMapping"... my only option is to click OK, and whe I do it, the box closes, then reappears, keeping on this forever (so I have to kill it, to terminate it). If run from Dependency Walker with the problem file as the only command-line argument, it analyses the file (for a real lonng time), then, after producing the ini and the log, terminates with failure. The last lines of DW profiling are the following: 00:55:39.171: First chance exception 0xC00000FD (Stack Overflow) occurred in "n:\IMPORTPATCHER.29.EXE" at address 0x00401009 by thread 1. 00:55:39.187: Second chance exception 0xC00000FD (Stack Overflow) occurred in "n:\IMPORTPATCHER.29.EXE" at address 0x00401009 by thread 1. 00:55:39.234: Exited "n:\IMPORTPATCHER.29.EXE" (process 0xA8C) with code -1073741571 (0xC00000FD) by thread 1. 00:00:00.062: Entrypoint reached. All implicit modules have been loaded. BTW, you rock! Thanks a lot for ImportPatcher!

Boot the HDD to DOS, load Grub4DOS, chainload Plop at USB 1.x speed, then have Plop boot Win 9x/ME at USB 2.0 speed. It's tricky to implement, but quite possible to do. You'll will have to live with having no USB hot-plugging, however, because if you let the USB drivers load Windows will hang up in mid-boot. It seems it's possible to exclude just one hub, but I've never tried that. If you decide to try this, open a new thread about it, and we'll help you along the way.

I'm sure all the community joins me in telling you your kind grant is deeply appreciated. You have our wholehearted gratitude. Great! Done.

Uhh... It means Drugwash is right, his PM box is full. Well, that's not surprising, since he all but disappeared for a whole year, and people must have got nervous. That said, I'm sure Tihiy didn't mean to pilfer your theme in any way. He probably didn't read well deviantART's license, and so must have taken for granted that it would suffice to give you credit, as he did. He ought to have asked your permission, of course, that's for sure. But, in any case, Tihiy never did anything that wasn't given to the community for free, and his RP9 is part of what helps keep Win 9x/ME alive. I wasn't aware that your theme was inside the pack because I don't care for skining, so I use RP9 just to fix the resources issue and to give me the ability to lock the taskbar and to use his great <Crtl>-<Alt>-<Del> handler. My Win 98SE has the Classic appearance. We're a shrinking very small community of Win 9x/ME afficionados, and without RP9, those of us who like skinning wouldn't have access to it, and to all the other features I just mentioned above. So, I'd like to reason with you in the following direction: by posting your theme at deviantART, you were permitting people to use the theme for their personal machines, not to redistribute it. But it wouldn't be usable in an effective way for 9x/ME, because of the great differences between it and XP. By porting it to RP9, Tihiy effectively gave the opportunity to our small community to be able to use your beautiful theme. I have no means of knowing when (and, in fact, whether) Tihiy will be back, though I firmly believe he'll be back soon. However, due to MSFN's rules, in view of your posts, I'd have to take down altogether the RP9 package, because it contains non-redistributable material, and this would be a great loss to the community, probably contributing to accelerate its shrinking rate. So, in order to prevent this, and since you're the owner of the rights over your theme, I hereby ask you if you'd be so kind as to agree to authorize redistribution in this way, at least temporarily, that is, until Tihiy comes back and contacts you. I'm confident that all members of MSFN's 9x/ME community join me in this request to you. I'm really sorry things weren't done properly from the start.

Get a common SATA/PATA --> USB adapter, having an external power source. They're quite cheap nowadays. Then test the drive with it. I bet both your connectors are just below the 500 mA, which is common, and your drive is getting underfed. I do think now we've hit jackpot.

What error exactly? Can you PM me the message you're getting? BTW, Tihiy remains active in these forums, although he hasn't posted for almos one year, now. I'm confident he'll reply to your post in soon. However, he may be on a vacation right now, because his last log in was Dec 14 2011.

By writing him a PM. But don't worry, I've done it for you already.

You'd have to ask the Anonymous author himself. They'll maybe work, but you'll have English messages appearing in the system, instead of Spanish ones. Now, just to localize (=translate the messages), ResHacker, eXeScope and a lot of patience may win the day. There is something about it here, and other old posts by Petr may be useful, too. Searching the forum may give you some other leads, too. Personally, I only use English (ENU or EN-US) versions. I have really no interest in localization, nor in localized OSes, so I never studied the problem myself, but I know Petr did have lots of success at it, before he gave up on Win 9x/ME.

Well, the bible of WDM is Walter Oney's book, Programming the MS WDM, but his site has a lot of interesting info, too. This old version of WDMSTUB, when it was still a VxD, is also interesting. Then there is his classic article on WDM: Part 1, Part 2 and Errata. Enjoy!

Win 2k and XP drivers are WDM, all right. But the implementation of WDM differs somewhat between those NT-Family OSes and the 9x/ME-Family. So sound drivers and USB drivers are the most likely to work, although some need WDMSTUB.SYS to work correctly. Video drivers are among the least likely to work across families, because the video subsystem implementation is hugely different across families, I'm sorry to say.

Elaborate, please: is it being redistributed in the latest RP9 package, or is it featured on the Themes Megathread?

Francis, BTW is Cypher in Matrix, of course! Have you seen "Streets of Fire" ? If not, do add it to you list too. It's one of my all time favorites. I do love "Kiil Bill (part 1)" too, but I do feel part 2 didn't quite live up to the standars set by part one...

Falling Down is great beyond measure! Dr. Strangelove is great, too. And Memento, just to mention one that wasn't yet mentioned. If you've not seen it, go for it. It sure is worth the trouble.

Quite interesting trick... I'll sure try it next time I need to find why some driver is refusing to work on XP. @jumper: BTW, WDMCHECK's companion, Walter Oney's WDMSTUB.SYS, can make some WDM drivers work with 9x/ME, and might be updated to include more stubs inside it. It's like KernelEx, but caters for .SYS WDM drivers, specifically. it could very well be the long sought-for solution for getting the printer drivers to work. The sources are provided in Oney's drivers book.

Notice, however, that CABVIEW.DLL from Win 98SE is v. 1.00.601.1(PE Timestamp: 13:37:43 Fri Apr 23, 1999) and has 61,440 bytes, while that from Win ME is v. 5.50.4134.100 (PE Timestamp: 21:35:57 Thu Jun 08, 2000) and has just 45,056 bytes... to me that seems to mean it leaves out some functionality that, in ME, is provided by other modules, probably SHELL32.DLL, but the one from 9x had to provide itself. That would explain the bug nicely and also help understand why the file version 5.50.x.x was selected (= to indicate it needs other 5.50.x.x components). Of course this is just my wild guess, but I might as well be right...

Yes. They are English versions and you'd need to localize them first before using with Spanish Windows 98SE.

Nina Simone – I Got Life

Deep Purple – Burn

America – A Horse With No Name

Here's a cropped internet gathered image of the part of the label that was hidden under the overlaid P/N label. Your drive should be set as master, hence "drive 0", for working in the enclosure... so do unbend the pins away from each other, and let's see whether this has any effect, please.

Happy New Year for all of you!

It's a quite good pic. I've downloaded it and reattached it to this post, for everybody to have access to it, so that you can delete your attachment from your previous post (to prevent filling your attachment quota too fast). Later I'll get back to the subject, but now I'll have to go. Happy New Year! Later: here're the specs... this may be a small step forward, but a step forward it is.

Do you have a scanner? Put the HDD label down in the scanner (with the cover open) and scan it in 600 dpi (just remember not to look towards the scanner while doing it, because the light may har your eyes). Such a scan will be good enough as a pic.

Yes: Transcend has some CFs that appear as non-removable.

To be able to use Win ME VxDs in Win 98FE/SE it's necessary to downversion patch. So CDFS.VXD 4.90.3002 is created from Win ME CDFS.VXD 4.90.3001 by downversioning the VXD, then patching with RLoew's patcher. So, that is the file found inside "IOSYS98.EXE".