Ninho

Ah, PsycoUnc... now at least I feel less lonely... Since my last post here, I too have tried the NUSB2 thing, plus the part of 98SEtoME that supposedly upgrades USB 2 support and even replaced the shell and shell32 components. And it has changed nothing The USB 2 controller is still handled (?) by the OrangeWare, and not used by the actual devices... A couple questions still - is this normal ? I fancied that, after going to NUSB2 and 98SEtoME, I would no longer need the OrangeWare but the chipset would be handled by drivers from MS. Yet if I uninstall Orangeware I don't find new drivers for my SiS USB 2, or am I not pointing Windows to the right place ? Is there a low level driver sleeping inside the ME cabs which I need decompress by hand or what ? - can someone tell positively if Windows ME ( the real thing) does handle our SiS USB 2 chipsets properly ? Not that I will ever install ME itself, but if the answer to this question is positive, then it maybe worthwhile pursuing. Thanks again to everybody on this great board -- Ninho

All and any of you who think they have the OrangeWare drivers supporting their MoBo's USB 2.0 (not any add-on USB 2 card), can you please provide details ? And first of all, check under Device Manager to see that the actual USB 2 capable devices are shown as connected to the Orange EHCI host, not to one 1.1 OHCI or UHCI host controller ? In my case the OrangeWare drivers installed and do "handle" the USB 2.0 host in a way (I'm saying this because windows doesn't pop-up asking for drivers at launch time) BUT any USB 2 device is still in fact hooked to the "old" USB 1.1 system :-( Browsing the developpers' section of the OrangeWare site ISTM their drivers are intended not to work with unsupported (=unpaid for) devices. Please please Gurus help clear this mess.

Please help : I have OrangeWare installed, ISTM, correctly : the "PCI Class USB 2.0 Enhanced Host Controller", as well as the "USB 2.0 Root Hub Device" show in Device Manager as OK. But both my USB 2.0 capable devices were first hooked to that system BEFORE I installed the OrangeWare. Windows 98 SE memorised them and they still connect to the USB OHCI, giving USB 1.1 speeds :=( I think I shoud remove all trace of these devices from the system so they can be redetected and, hopefully, "captured" by OrangeWare. Right ? So my question is : how do I remove the devices ( one external HD enclosure plus one "key ring" flash memory device) so that Windows 98 loses all memory of them ? 1st option : physically hook devices - open Device Manager - "remove" the devices there. Will it suffice ? 2nd option : Registry chirurgy. I'm not scared, but need instructions ! Thank you very much in advance, this has to be a life saver !

Hi again ! Been peeking inside the Win 98 SE Registry, here's what I find from OrangeWare; does it seem OK (Petr ?) Should I look at other sections of the Registry for potential problems ? If it looks OK, I could uninstall my USB 2 memory *devices* (1 external HD "Profil 35" by QPS, and 1 non-name USB 2.0 disk-on-key) and reinstall them; they were both hooked to system BEFORE I found the OrangeWare drivers, maybe that's why they won't use OW ? -------- OrangeWare USB 2 : HK_Enum key ------------------------------------------------------- [HKEY_LOCAL_MACHINE\Enum\{B8139C20-CF94-11D5-AEF7-0002B30625C5}\ROOT_HUB20\PCI&VEN_1039&DEV_7002&SUBSYS_70021849&REV_00&BUS_00&DEV_03&FUNC_02] "Capabilities"=hex:84,00,00,00 "HardwareID"="{B8139C20-CF94-11D5-AEF7-0002B30625C5}\\ROOT_HUB20" "DeviceDesc"="USB 2.0 Root Hub Device" "ClassGUID"="{B8139C20-CF94-11d5-AEF7-0002B30625C5}" "Class"="OWCUSB" "Driver"="OWCUSB\\0001" "Mfg"="OWC" "ConfigFlags"=hex:00,00,00,00 "Serial"=hex:2c,00,00,00,00,00,00,00 ---------------------------------------------------------------------------------------------------------- Yours truly, clueless... Ninho

@Eck You're not interfering in any way, by Jove, your input is precious as Petr's is. I need time to digest it all ;=) @Petr & Eck & All I think I shall go the way of : removing OrangeWare and try AsRock supplied, intended for Windows 2k, driver. Crossing fingers. I've also requested the localised updates Q239696 & Q291362 from Microsoft support. In case someone is interested in having these files in French, he may contact me. [Edited : ooops ! MS or their subcontractor sent US-English files and say it's all they have ! A shame, esp. concerning the central user interface files :=( ] Back later ...

Petr, your patience is admired. The PCI device in my chipset is indeed 1039/7002. Checked again using a PCI identification utility. Vendor ID : 1039 , Dev ID = 7002 , Subsystem = 7002 , Sub-vendor ID : 1849. == Is there something wrong with Orangeware or this SiS controller ? Not sure I grasped what you are trying to explain - I'm really sorry ! (Edited:) Would you advise me removing the Orangeware and retrying ? Or removing it altogether, but what to replace it with ? -- Ninho

How's that, "unsupported", Petr ? what's wrong with that new OrangeWare EHCI ? In addition to the 3 lines for USB/EHCI I listed earlier, I still have the lines for Open HCI showing in device manager. They were untouched by the Orangeware install : - Contrôleurs de bus USB = Concentrateur USB racine = Concentrateur USB racine = Contrôleur d'hôte ouvert PCI vers USB SiS 7001 = Contrôleur d'hôte ouvert PCI vers USB SiS 7001 And the orangeware added for EHCI : -Universal Serial Bus controllers =PCI Class USB 2.0 Enhanced Host Controller =USB 2.0 Root Hub Device The only thing troubled me a little is they don't come under the same header in Device Manager listing, but isn't it just because the languages differ ? Why is this made so difficult ! Oh, yes, I think I have an idea why it is ;=)

Hats off to those involved in this great development ! I have Win 98 SE (French). Does someone know where I could find the files off Q23696 & Q291362 ? Concerning the NUSB22E.EXE : may I pick & extract & replace the files one by one (using WinRAR for instance), so that I can be sure it doesn't replace newer files ? Is there something to update in Registry in addition to replacing files in their respective directories ? Is the NUSB22E (and its updated .inf file) sufficient for USB 2 storage to work ? I mean, without also doing the MDGX "98SEtoME" modification ? I don' t like the idea of going for the latter, esp. since he does not provide non US versions, and I am nervous about how that would interact with Windows Updates, and finally because I do not want some of his replacements - the Scandisk from ME for instance is definitely not good for 98 SE (doesn't work with Drivespace). But I am digressing... Do I have to "remove" all my USB storage devices before I install NUSB22E (or the files within) ? What is the manual way for "removing" the devices in question ? Do I simply remove them in Device Manager, or must I also clear the Registry (I think so...) and, please, which registry keys would have to be removed ? Or can I trust the uninstallers for the respective devices ? Sorry these are many questions :-(

@Eck : your experience is an encouragement indeed; you wrote : Which CD was that ? The one from MoBo makers ? Are yous ure youwere able to install the drivers intended for Win 2k under 98 ? Also, did you check your devices achieve USB 2.0 speeds alright (not difficult to assess, try to transfer a 1 Gigabyte file... if it takes a couple minutes, it's USB 2 , else if 20 minutes, well, you see the point)..... @Petr : I now have the Orangeware driver installed. Device manager shows it thusly : -Universal Serial Bus controllers =PCI Class USB 2.0 Enhanced Host Controller =USB 2.0 Root Hub Device Shall I also upgrade the Windows 98 files, like USBSTOR.SYS ... ? What should my next move be ? Could you please point me to accurate instructions ? Concerned also about the fact that my Win 98 SE is a non-US version. I don't mind if some messages come out in English instead of French, but I want to be sure it'll work alright after all the changes. TYIA

No microcode updating is possible on the K6-x, but several important optimisations which should be done by the BIOS and are not always - including write allocation & extended write merge buffering... there are several utilities which help setting the K6 up, running either under DOS or in Windows. Unfortunately I don't have my K6-2+ running any more, but googling for K6+"write allocation"+"EWB" should give you plenty of ideas. Optimisation of the chipset is another area which often needs some tweaking and can bring important overall improvements. HTH -- Ninho

Hi Petr! Yes of course I have. The same "driver" exists on the CD which came with the MoBo : Unfortunately, it is a fake : it does nothing, but launch a small program in Autoexec.bat which disables the USB 2 (EHCI) controller in the SiS 963 L. The purpose being to inhibit windows 98 SE from (re)discovering the EHCI upon each boot and asking for the missing driver. Dirty trick, isn't it ? I'll have to check your Orangeware thingie - that would be what I'm after, only I need check the PCI id of the USB 2 function in my chipset before. Thank you very much, I'll report failure or hopefully, success with that ! [Edited ...] Well, the Orange USB 2 drivers installed successfully : thank you! thank you, thank you ! I now have drivers for the USB 2 in Device Manager. The devices themselves are still using USB 1.1 however. Do I have to install part of the "SE to ME" thing in order for my external USB drive to recognise and use the new EHCI drivers, or do I simply uninstall and reinstall said USB drive using its manufacturer's disc ? -- Ninho

Hi ! This is my first post, and I have searched but do apologise for n00bieness ! I desperately need to activate USB 2.0 function in Windows 98 SE, motherboard : ASRock K7S41 (SiS 963 L southbridge). Neither MS, nor the MoBo or chip makers, nor the makers of my USB 2.0 capable appliances provide the needed low level drivers for EHCI. As a result, my USB 2.0 external hard drive, and USB 2.0 disc on key, work only at painfully slow USB 1.1 speeds under W 98 SE (but do work at USB 2.0 speeds under windows 2000 SP 4 - tested) Is the "Unofficial Service Pack" a solution to this problem ? Or does it not provide the EHCI chipset drivers, and if not, who will ? Thanks in advance -- Ninho