dencorso

Moreover, if I counted right, 22 out of 36 machines in the list are running with > 1 GiB without the help of RLoew's RAM Limitation Patch. For RAM > 1 GiB, up to 2 GiB this is relatively straightfoward. For > 2 GiB it gets trickier... RLoew's patch allows Win 9x/ME to actually access all that RAM, is really easy to apply, and makes the system generally stabler. But one can do without it, with lots of patience. I had my own machine running without that patch for a long time, with 1.5 GiB and my problems really began when I decided to go above 2 GiB. Video cards with 512 MiB are, apparently, only usable with RLoew's patch, AFAIK. But very few users investigated it, so I would not be surprised if someone found a way to use them without the RAM Limitation Patch. But for machines with a 256 MiB or less Video Card and not more than 2 GiB RAM, it's clearly optional. And to run with 1 GiB is exactly as easy as to run with 768 MiB RAM. In both cases one can just tweak SYSTEM.INI, or use Xeno86's FREE modded VCache.VxD, without bothering with SYSTEM.INI.

Yes, you can. But I don't really think it's a good idea if the BIOS doesn't recognize it. It'll be a PITA to configure bios and/or run true DOS. I'd say go for another PS/2 keyboard. My own favorite is an 1993 IBM model M (1391401) PS/2 original keyboard. They're still findable used at reasonable prices, from clikykeyboards. But they lack the "Windows" keys. If you must have those keys, a contemporary version of the model M is produced by Unicomp. IMHO, these are the best keyboards money can buy, at reasonable prices. But this is a matter where YMMV wildly. HTH

For more (lots, in fact) info about installing Win 9x/ME with > 1 GiB RAM and/or > 137 GB HDD, please refer to the threads pointed to in my signature. You'll find there more info on RLoew's patches, too. HTH

Please, do stop posting in bold Georgia. Unwarranted formatting is frowned upon here at MSFN. Read the Rules, particularly #11. Consider yourself warned!

He won't flame anybody else, from now on. @jaclaz: "Rag speaks ill of cloth strip", perhaps? Thanks to you, I've learned a new saying today...

It *is* for IE6SP2 and up only. The reason that that is not spelt up is that MS considers IE6SP2 the only valid IE6, for some time already. When they meant IE6SP1, they've always said it in full. It's over. I'm sorry!

Since I mentioned 98SE2ME, I think I should've also mentioned that the Win ME TCP/IP stack is one of the things from Win ME that actually *cannot* be backported into 9x, exactly because it's too different from the previous implementation. IIRR this is precisely one of the features that were investigated very thoroughly by MDGx, during the development of the 98SE2ME project. Sorry!

@Multibooter: It seems to me that increasing MaxInstance to 8 and letting it stay at 8 for TCP/IP under 9x is a safe bet, in view of the MSKB documents indicated by MDGx. @wsxedcrfv: There are many places where ME is (sometimes much) better than 9x... That's why 98SE2ME gives one probably the best compromise achivable.

Yes. BTW, *don't* double post! I've removed your duplicate thread from the General Discussion forum, because here is the appropriate place for your question.

Hi, Joe! Welcome to MSFN!

Give TrayMin also a try. While it may not be what you're asking for, you may find it satisfies your need well enough. Look for it, as well as for info on it, in this thread, starting in post #4.

Dave, while you still have the cards, would you please check I'm interested in finding out which (if any) of the issues you have are due to the (bad) interaction between the cards.

The problem, with all due respect, is that wsxedcrfv is interpreting erroneously how IPD works. There always is, inside the package, a bigger compressed file... in the present case (KB2286198 for XP), this is _sfx_0003._p (2,520,543). This file is the one which, after being decompressed, is used as the base, from which all the others in the package are generated by patching. Which name has the bigger file changes from package to package, and I don't know how the base file is recognized (maybe just by size). In other words, all IPD packages contain exactly one compressed base file and patterns to modify it to create all the others. That's all. KB828030 is one example of MS documents which are terse to the point of being misleading, because one of the files is not a delta, but instead the reference on which the deltas are applied as transforms. If you dont believe me, try to unpack one such file for XP while on Vista or Win 7: neither contains any XP files, and yet the result of the unpacking operation is the same when the package is unpacked under either Vista or Win 7, and is identical to the result obtained in XP (any SP, BTW). You can get the same results under Vista PE and 7 PE, too. This proves categorically that no file from the underlying OS is used as the reference, and is consistent with the description I just gave of how IPD works.

You might use regshot to compare the registry before and after removing the binding, to find out how and where in the registry it's done. Then set them by hand or using a set to reg files created just for that purpose.

Yes. From DOS.

Don't uninstall anything. Reinstall NUSB 3.3 over your current installation, accepting to overwrite any file it may prompt you asking whether to keep or overwrite. Reboot. Let's see what happens.

For those interested on RLoew's Multicore SDK, some more info is available here.

1) No. 2) I don't know. AFAIK, it just won't work. For all about GMA900 read this thread: Asus Eee PC and Windows 9x... the Eee PC 4G is an Intel 910GML/915GM(S) & ICH6-M machine, so all that's said there applies. I searched around and, by now, I'm pretty convinced the Northbridge is actually a 910GML, to be exact, but all the Northbriges in that family do differ only in very minor details.

It's a virus, all right! And a pretty new one, at that: Worm.MSIL.Arcdoor, according to MS.

Hi, jassenna! Welcome to MSFN! I have two suggestions: 1)Don't remove nVidia drivers with Add/Remove applet or unistall, since neither does do a really thorough job, in this case. Do it, instead, by using the great freeware Driver Cleaner Pro Version 1.5 (*NOT* Driver Cleaner .NET !!!). 2)Very old cards require very old drivers... I strongly suggest you try their drivers from the 22.40 up to the 29.42.

It would be a good idea to submit the actual file to VirusTotal, too.

Bob Dylan - Hurricane A wonderful song 8m 33s in full! No one does extended songs like that anymore!

It's OK. I thought you were keen on updating the BIOS. Let it be.

No.

How many threads do you need to open for the same subject, frogman? Threads merged. Consider yourself warned!