dencorso

Just a heads up: there's a piece on drones in the Nov 2013 Issue of Scientific American.

The only major issue (pending, mostly, really, not yet very actual) is things that need SSE2. One of my main machines is a 3 GiB RAM Athlon XP 3200+ (so, likewise, no SSE2 or higher). All I need works OK in it, except the Linux versions of Flash 11.x (for some reason *just for the linux versions* v. 11.x requires SSE2), so I'm stuck with the last Flash 10, which is v 10.3.183.68, for running linux. Moreover, PaleMoon for Windows dropped non-SSE2 machines at 3.6.32, so I'm stuck with it, too, and that's somewhat more serious, because PaleMoon is my main browser (but I can move on to Firefox ESR, for instance, if needed). As it is, PaleMoon 3.6.32, plus IE8 (spoofed to say it's IE9) and the latest Opera 12.16 have been enough to satisfy my needs... but it's far from clear for how long that'll continue to be so. Of course, this is just a heads up... we should keep everybody posted on the status of this issue, but it still remains no endgamer, at this point.

Now, that was fast!!! Thanks a lot! You rock!

Hi, Fernando! I'm getting "Please update your browser", even for Opera 12.16!, from the hostsites you use. Could you please upload to Filedropper or the like, even if just temporarily, and post a link for your latest mod driver? TIA.

It's not much, but it's what we do know: nVidia GeForce and Win 9x/ME - Relevant Threads There may be some more bits of info scattered around after my latest update to that post, but not much. Welcome to MSFN!

ciao, jaclaz! To be able to compare in the exact same hardware Win 8 and Win 8.1 is what I consider exciting, albeit in a purely philosophical way... I wouldn't myself touch either even with a 10 yard pole, I've drawn my personal line in the sand at Win 7... but that's me. Fair comparisons, on the other hand, are always interesting, even exciting, and allow one to take better informed decisions.

Well, if I may... I think it'd be perfectly legal (provided the intended use is on the same machine, but it wouldn't work anyway in case it's not, I guess) to acquire a *forensically sound* image of your activated Win 8 and save it away. Then update to 8.1 and acquire a second *forensically sound* image of your activated Win 8.1. From this point on, you can downgrade back to Win 8 and return to Win 8.1 at will, in about one hour each time, by just alternating which image you redeploy, and keepeng activation. As long as just one of the images is deployed while the other is just stored out, my understanding is that this ought to be perfectly legal in all aspects. It's just well above the ability of an average user to swap full system images back and forth, but when one knows how to do it right, one can *really* compare the two OS editions in the *exact same conditions* on bare metal true hardware. I don't want to hijack the thread, so I don't think any discussion here about what exactly is a *forensically sound* image should be allowed here (and so a new thread may be opened or one of the older ones may be resurrected for this purpose), but would feel bad if I didn't remind you of this possibility (which I do consider exciting) at this point.

Svchostviewer, particularly when combined to Process Explorer (oe with Process Hacker) may be of great help. Do give it a try, then tell us whether it did help. I cannot do it right away, but I may be able to help you in determining which services are really relevant to your particular configuration and needs. Black Viper's page is great, and is very detailed, but is perforce somewhat generic and should be taken as a starting point only... much tweaking is in order to get really satisfactory results, IMO.

Care to elaborate, please! "Just solved it" posts are so very frustrating...

Here...

If LoneCrusader says it works, rest assured it does.

Philip K. Dick does rock! I do love his books! And I did read that, way back (and keep telling myself I should read it again, soon). Right now, I've just finished Arika Okrent's great book on Invented Languages (you might like it, if you haven't read it already). Now, when the subject drifted on to actions taken by unbooted OSes, the allusion was irresistible.

Now, then... a capping jumper is a good guess, especially since 32 GB = 29.8 GiB and OSes usually talk GiBs, while manufacturers talk GBs, of course... So the OP speaking of "the BIOS and OS calls it an 30Giger" would make some sense (then again, unbooted OSes don't talk, of course, but who knows whether they may dream?).

Aluminum and bottle glass are also viable. Iron and PET can break even when done right. The rest are urban legends. Sure. That's the way to go.

It's working again! They've fixed it! Heartfelt thanks to all involved in fixing it: you rock!

Philip K. Dick - Flow my Tears, the Policeman said.

This is a trimmed version of the 1st post: the table below lists only the non-superseded updates, all others were have been removed for easier reaference. Only those files related to USB that were actually updated after SP3 are mentioned here. None of these updates is known to cause any issues. ------------------948101v3-959765-2828030-2807986-2868038-2862330-2862335-2884256-3139398- -------------------HotFix--HotFix--HotFix-MS13027-MS13081-MS13081-MS13081-MS13081-MS16033- ========================================================================================== usbd.sys----------------------------------------------------6437-------------------------- usbccgp.sys-------------------------------------------------6437-------------------------- usbehci.sys-------------------------6368--------------------5778-------------------------- usbohci.sys---------5550------------------------------------------------------------------ usbuhci.sys-------------------------6368-------------------------------------------------- usbport.sys-------------------------6368--------------------6437-------------------------- usbstor.sys-------------------------------------------------------------------------7012-- usb8023.sys---------------------------------6352------------------------------------------ usb8023x.sys--------------------------------6352------------------------------------------ usbaudio.sys----------------------------------------6425---------------------------------- usbvideo.sys----------------------------------------6425---------------------------------- usbser.sys------------------------------------------------------------------6442---------- usbscan.sys---------------------------------------------------------6418------------------ rndismp.sys-----------------5716---------------------------------------------------------- rndismpx.sys----------------5716---------------------------------------------------------- hidparse.sys--------------------------------------------------------6418------------------ irbus.sys-------------------------------------------6425---------------------------------- ========================================================================================== -------------------HotFix--HotFix--HotFix-MS13027-MS13081-MS13081-MS13081-MS13081-MS16033- ------------------948101v3-959765-2828030-2807986-2868038-2862330-2862335-2884256-3139398-

Just a heads up: the just released usbccgp.sys 5.1.2600.6437 from KB2862330 may work with Win 98SE, so it might be of interest to the uSP (but no, I didn't actually test it).

Go to MDGx's and look around... there's some good info on iexpress there and further links to follow.

The 1st post was updated on Oct 09, 2013, to reflect the new USB driver updates in MS13-081 (KB2862330, KB2862335, KB2868038 and KB2884256).

I've added 127.0.0.1 ui.skype.com to hosts. Still, I remain unable to connect to server with my 1.4.0.84... There must be more to it.

I confirm Skype 1.4.0.84 isn't able to connect anymore! Well... As you can see, I hardly use Skype, ever... the latest time I had used it before this one, it did connect all right... Sorry if I was misleading...

Hi, Andrew T! Good to hear from you. I've got Skype 1.4.0.84 installed on my 98SE from way back, and it never gave me grief. Now, what Dude111 said makes sense: just find out which site the installer tries to access and redirect it (to 127.0.0.1, on 1st guess) through the hosts file... It may be enough. Or you actually may have to use a real IP, instead of 127.0.0.1 (but I really doubt that'll be necessary).

Spiderman (the 1st, for maybe the 10th time... and it still does rock!).

Happy Birthday, Tripredacus and puntoMX!