dencorso

As to being "VLK" or not, that's easy: just right click on "My Computer" and select "Properties". You'll see a window like the pic attached. The "xxxxx-yyy-zzzzzzz-zzzzz" in it represents a number, known as MS Product ID (do not post your machine's full MS PID), of which the "yyy" part is the Channel ID. Now, any Channel ID begining with 6 (usually from 640 to 652) should mean "VLK". Just give it a look and you'll know for sure.

Too many questions... too little answers. I do suggest we should wait for papatwan to reply to the many already posed questions before proceeding...

Join the club with the database error causing double posts. I wonder if the admins of the forum know about this? We sure do know and are working to solve it for some time already...

Wow! RoboBee, indeed... It exists, weighs about 80 mg, takes off and flies controlledly (for a time) then crash-lands, at present. However, it's still tethered because power source and computer-flight-control are not onboard. It weighs 80 mg! The reference is: Ma et al., Controlled Flight of a Biologically Inspired, Insect-Scale Robot, Science 340, 603-607 (3 May 2013); DOI: 10.1126/science.1231806

jaclaz is right (of course!): pin 9 is "KEY", being usually not connected (viz. "NC"), or, less commonly, grounded. Now, pin 10 is absent (= missing), so that one can immediately recognize which pin is pin 9 (because it's the only one that has no conterpart). Reversing "Data +" and "Data -" causes the port not to work, but usually causes no damage, so it can be corrected (this seems to me to be the problem with your machine). Now, reversing "Power +5V" and "Ground" can kill the motherboard, so take care with what you do, and don't do anything unless you're sure of what you're doing!

Or refer to this pic (from the ASUS A7V600-X):

Super Pi, for a stress test?

Boot from a Live Linux CD (I recommend Porteus) and delete any and all files you need to delete. If I were you I'd delete the problem files/folders, then delete RECYCLER for good measure. Then go back to windows. It'll automagically recreate a working, empty Recycle Bin.

+1 A crashing startup process is never harmless: instead of it, it's a harbinger of bad behaviour down the road. It must be uprooted, not left alone and taken for granted.

You mean... like this?

Right! I had in fact forgotten about that page, but it's bona-fide, of course! However, the post quoted below, from a parallel thread, suggests perhaps the best overall choice may be 45.23...

Great! Glad to see it worked!

I've used the driver mix described below for a long time, before moving on to the 77.72 I presently use. IIRR. before I added Rloew's RAM Limitation Patch (with the /M switch), that driver mix was the highest version drivers that didn't cause neither the shutdown issue nor "the Restart in MS-DOS and back" issue for my GeForce 2 MX 400.

I believe it should be possible to create some exclusion in Proxomitron's rules for the Wayback Machine. But I'm no expert in it so, we'll have to wait for herbalist to chime in about it sometime (btw, I've see no posts by him since last year, at least... hoe all is well!). In any case it should be pointed out that links to content inside the Wayback Machine are one of the rare occasions in which url redirects are used on purpose, with no sinister intent behind them.

So you yourself provided the answer you seek: to use the crappy hardware (no disrespect intended: you yourself said it was low quality) you want to support you need sp3. Now, you don't want to update to sp3... but you really don't need to, in principle. All you need is to update the USB stack to sp3 and. preferably, even post-sp3 level. That means updating all the hid*.sys and usb*.sys to sp3 level, fist of all and checking whether the OS still works OK. If so, there you have the solution you've been seeking.

The GeForce 2 series is from 2000. My point is one must go further back tin time to reach times before 98 FE.

I don't know but if I'm allowed to hazard a guess, I'd try 29.42-win9x-whql as a starting point. Guru3d has that one.

Both the 82.69 and the 81.98 drivers do not work OK with a a GeForce 2 MX (I shoulld know... I use an MX 400). You can get the 77.72 and/or even earlier drivers either here or here. And the thread "nVidia GeForce and Win 9x/ME - Relevant Threads" has pointers to some further interesting threads.

There's nothing to be sorry about... It seems my crystal ball is tuned great today! It's too bad it never lasts much, though...

Definitely, something is rotten in the state of Denmark... err... on your browsing or security configuration! All the links in my post #45 in the Free Software thread, as well as the left hand link on post #3 go through the Wayback Machine. The right hand link on post #3, however, does not. The fact that you can connect the Wayback Machine directly and perform a successful search therefrom shows there's nothing wrong with your ability to connect the Wayback Machine. Hence, I conclude something is set to remove redirects from your links at some stage during a connection attempt on your part. Let me explain it further: On my post #3, the left hand link is called by the text "This link goes through the Wayback Machine, and should work OK", and it contains the following url underneath it: http://web.archive.org/web/20050212215255/http://www.utdallas.edu/~jeremy.bryan.smith/articles/explorer_spy.html while the right hand link is called by the text "Now, this one does not (and shows the above message).", and it contains the following url underneath it: http://www.utdallas.edu/~jeremy.bryan.smith/articles/explorer_spy.html Now, since you get the same result from both, something somewhere must be removing http://web.archive.org/web/20050212215255/ from the former. Do you use Proximitron, perchance?

That's simply impossible! The result you're getting is the one anyone would get if trying to go directly to the old link, without using the Wayback Machine!!! This link goes through the Wayback Machine, and should work OK. -+- -+- Now, this one does not (and shows the above message). Both links simply cannot send you to the same place, or there's something really amiss with your browser or security settings...

Helamonster's UserAssist Spy. To know more about it read his article entitled: Yet Another Method Windows Uses to Log Your Computer Activity. Here are direct download links for UserAssist Spy v. 1.2.0.0 and v. 1.2.1.0.

Well, if so, I must point out that DETECT must not be run from a CD, because it'll attempt to write those files it creates (BIOS.BIN and BIOS.TXT) to the directory it was run from, and, in the case of a CD, it'll find out it's read-only and throw an error.

Why? Win 95 has its own CD/DVD drivers. You'd need it only in case you intended to work with CD/DVDs in true DOS. Do you?