Looks like you guys will have everything figured out by the time my son comes home for Thanksgiving... there won't be anything left for me to figure out! ;)
To Peter: Were you able to install Win98SE with ACPI or did you use the "/p switch" to disable ACPI during the install?
If you're using APM, maybe that's why "the ACPI interface named tosrfec.sys could not be loaded" error message occurred? And maybe the older version is using APM?
I found the following Bluetooth driver:
http://web.belkin.com/support/download/download.asp?download=F8T001_v1&lang=1&mode= . It installs and the blue light flashes. I can't verify functionality, as I do not have bluetooth devices. This software looks better than Toshiba's. Interestingly, a newer version, F8T003_v2 from the same site (for another bluetooth stick) did install but then refused to start.
I tried ACPIOption=1, however it did no good, at least not to the windows in the state I have, and I backed out quickly. I got a ressource conflict in the ACPI system board devices and the USB mouse went to crawl.
After all, for my purposes USB2 is needed (because of the hub), but bluetooth isn't .
Were you able to install Win98SE with ACPI or did you use the "/p switch" to disable ACPI during the install?
Hello Rod, My Win98SE did not have ACPI enabled. It was copied over as a partition from my previous notebook, where it served as a reserve clean installation. It was from a 430TX chipset, had APM, and I deleted APM on the I6000.
I started from this partition, enabled ACPI, Run the control panel Hardware Wizard, let it run to end, and installed the chipset again. Now the USB mouse behaves jerky, and I have a conflict on the third of four "System Board Extension for ACPI (BIOS)", in the range 100A-1059.
There is also something strange with USB. The I6000 has four USB connectors. On Windows XP they appear to be on four controllers, four hubs. And Bluetooth should be on the fifth controller. On Windows 98 they are reported just on two hubs (I looked at this by connecting devices and checking Energy).
(added) In order to see what happens, I did a clean install of Windows98 into the empty disk C:\ (i.e. empty partition) without any MSBATCH.INF, but with the /p j flag for ACPI. The command was "E:\win98se\win98\setup /p j" . This got the same result in the device manager, ACPI is present, USB mouse is not smooth and there is a conflict of the third "System Board Extension for ACPI (BIOS)". I did then not proceed to the installation of our drivers.
Needless to mention this is on the same computer as my Windows XP, so it needs some tools and organization to switch easily back and forth.
Peter
Message Edited by PeterSwiss on 11-20-2005 02:27 PM
Peter, for some reason, I'm having trouble installing the Toshiba driver. Here's what I'm doing and hopefully you can tell me what I'm doing wrong:
1)double-click on "Tm1bt8.exe" and let it extract to C:\windows\desktop\Bluetooth.temp, then automatically run "bluetooth.exe",
2) system reboots,
3) I modified the file "tosrfusb.inf" located in C:\windows\desktop\Bluetooth.temp\Windows\ inf with the "my Bluetooth" modification you mentioned in a previous post. I added the line just before the "%TosrfUSB.DeviceDesc1%" line
3) upon opening Device Manager I have 6 "Other devices", 3 Composite USB Devices, PCI Card, PCI Communication Device and PCI Network Controller. These should be the Bluetooth device, modem and wireless card but I'm not sure which is which so I tried all three.
4) I double-clicked on each one and selected "Reinstall driver", then "Search for a better driver...", then "Specify a location". I entered "C:\Windows\inf", then "C:\windows\desktop\Bluetooth.temp\inf" and finally "C:\windows\desktop\Bluetooth.temp\inf\Win9x". Each time I got the message that Windows was unable to locate a driver for this device.
I get the same results when I tried the Belkin driver. I'm not sure that I'm looking in the right place for the drivers. Could you tell me how you got this to work?
PeterSwiss: I tried ACPIOption=1, however it did no good, at least not to the windows in the state I have, and I backed out quickly. I got a ressource conflict in the ACPI system board devices and the USB mouse went to crawl.
I had a hunch that might happen, but I was hoping that since the main drivers were already installed... ACPI "might" re-enumerate the devices (after restart) differently than it did during the Win98SE OS install. If I remember right... there were several fixes for ACPI problems with Win98SE.
PeterSwiss: (added) In order to see what happens, I did a clean install of Windows98 into the empty disk C:\ (i.e. empty partition) without any MSBATCH.INF, but with the /p j flag for ACPI. The command was "E:\win98se\win98\setup /p j" . This got the same result in the device manager, ACPI is present, USB mouse is not smooth and there is a conflict of the third "System Board Extension for ACPI (BIOS)". I did then not proceed to the installation of our drivers.
I myself, would like to try the"98SE2ME.exe transplant" ("click here"), since I use some WinME files for Win98SE, anyway. When I have the time... I'll give it a try...
It seems I neglected to investigate a little further. After I looked at Device Manager and discovered that all three "Composite USB Device" listings were gone. Also, when I look under Ports (COM & LPT) there are 11 Bluetooth Serial Port entries (COM3-13). Also, I opened "My Bluetooth Places", then "My Device" and was able to start the Bluetooth Serial Port, File Transfer, Information Exchange and Network Access services. The Dial-Up Networking and Fax services failed to start because no modem could be found. The Information Synchronization service failed to start because "The 'Save Objects in PIM' is not checked in the Configuration Panel". The problem now is that when I try to search for devices, nothing happens. I wondering now if everything installed OK, it's just that I don't have things configured correctly yet.
To finally answer your question about the DEV for the USB2 controller, it is indeed on
265C. Sorry, it took so long for me to find it. I'm sure you probably didn't need that any more since you were able to get USB2 working anyway.
Now, I'm going into the registry to see if I can determine what the other three devices are that are Unknown.
>Now, I'm going into the registry to see if I can determine what the other three devices are that are Unknown.
You can check in the Ressources tab of the device and compare to the Ressources tab in WindowsXP.
My proposal is:
PCI Card = Secure Digital Slot
PCI Communications Controller = Ethernet, or did you install that already
PCI Network Device = Wireless.
I got the same result as you described with the Belkin driver, and a similar from Toshiba. When I scanned for bluetooth devices, the blue light was on for the time of the scan. Otherwise, it flashes constantly. Do you have an external bluetooth device? (otherwise it is an exercise, and Bluetooth makes the computer slow. I went back to the non-bluetooth system for these reasons).
I'll try the unofficial Win98SE service pack on the clean Windows98 install, in the hope it does not upgrade "microcode".
I tried the unofficial Windows 98 Service pack, but it did not improve the relative situation, all the problems in the ACPI variant remain (USB mouse is updated 5 times a second, conflict on the mentioned ACPI BIOS device). Non-ACPI is still good of course.
I have the impression that the Belkin and the Toshiba Bluetooth drivers are the same at the transceiver level, just Toshiba complains about tosrfec.sys and Belkin ignores silently. User interface and services offered are however different.
It seems the Dell Latitude D610 owns a BCM5703 Gigabit Ethernet controller (10/100/1000). There is a complimentary reference driver at Broadcom, the download page is http://www.broadcom.com/drivers/downloaddrivers.php. The driver is named win_me_98-8.39.1b.zip (72kB).
it is remarkable that the graphics speed is just 100/120 MHz when on battery. I did not notice any slow-down. Maybe it makes the laptop more quiet even on AC with that setting (RadClocker) ?
USB2.0: I can't find the specs on what "USB 2.0 chipset" the I-6000d is using (might be found in WinXP’s Device Manager). But since I read somewhere that the "ALi / NEC USB 2.0 Chipset" might be the most used... I'm guessing the new USB 2.0 drivers upgrade at the top of
"this page"
, might work.
Rod, you were right at that early time, when you posted it. File U2v2_3.exe from that link is what was needed, although it is not ALi and not NEC but Intel. :-) And it does match the chipset thru a strange CC_ instead of VEN_ & DEV_ .
I try another attack on the wireless, as it will be helpful, instead of cabling. I'm yet a bit sceptical, as the INF file contains little registry entries in comparison, but a "coinstaller" and a different "enumproppages".
Sorry, I've been quite busy lately with other things and unfortunately have not been able to spend much time working on my computer. I still am unable to load drivers for Bluetooth, the modem and the wireless.
I did some poking around in my regestry (98 partition) to try and figure out what the 6 devices were that were not loading. As I previously mentioned, I have a PCI Card, PCI Communication Device, PCI Network Controller and 3 Composite USB Devices listed in Device Manager. Peter had proposed the following in an earlier post:
My proposal is:
PCI Card = Secure Digital Slot
PCI Communications Controller = Ethernet, or did you install that already
PCI Network Device = Wireless
This was mostly correct. The PCI Card is my Conexant D110 modem. The PCI Communication Device is a GemCore Based SmartCard Container, and the PCI Network Device is the Intel PRO/Wireless 2200BG. The three "Composite USB Devices" are all related to Bluetooth.
I then started looking at the .inf files associated with each of these in XP and found that the modem and Bluetooth .inf files are Win98 files (their signature is $CHICAGO$) and the wireless and smartcard .inf files are NT based (signature = $WINDOWS NT$). My question is: can the two $CHICAGO$ .inf files be modified slightly so that XP will accept them and load these devices? I am going to mess around with those and see if I can get it to work.
Peter, do you have all your devices working now or are you still having problems?
Hello Bobby, you do not need adaptions from Windows 98 to Windows XP (why). The chicago and Windows_NT signature are both understood by Windows 98 and Windows XP.
For Modem you need the reference driver mentioned earlier in this thread from Conexant. Then you have to modify both the..M2.inf and the MM.inf for the device ID. That's it.
Regarding Bluetooth, first you need USB2. That you already found. Then you need a Bluetooth stack. We mentioned two that install and seem to work.
I do not exactly understand why there could be problems with modem and bluetooth, please precise if there are.
For Smartcard I believe there are chances for ordinary modding, for Wireless chances are less.
Regarding smartcard slot, respectively I do have an SD Card slot, probably a Ricoh R5C821, I did not find a windows98 driver and I am still in the process of going backwards. This is supported generically in WindowsXPSP2, and Ricoh does not provide free reference drivers. I do not yet give up. The difference between W98 and WXP is in the way how the driver module (some xxx.sys) is declared in the INF file (Service directives versus Devloader and DeviceVxds directives). The drivers are uniformly "services" in Windows XP, where in Windows 98 the directives depend on the kind of device. However I do need to do it more carefully, short of studying the DDK!
Regarding Wireless, it does not look easy. The INF file references a so-called coinstaller, that is a module which does all the essence of the installation (named w29NCPA.dll). The coinstaller mechanism was introduced for Windows 2000 and therefore can't possibly be understood in Windows 98. A few wireless drivers for Windows98 already resisted my attempts. I still have the Intel Wireless5000 family for Windows 98 driver before me. Could be that the BG2200 resp. 2915, 2100 are completely new designs. And then the best bet for Wireless is to obtain an external USB wireless dongle, or simply a wired ethernet connection.
I tried your suggestions regarding the modem again and it worked! I don't know why it didn't work the previous times I tried it (obviously operator error) but at least now the modem loaded correctly and I can communicate with it. I will have to try dialing out later tonight. Thanks for your help and thanks for the information regarind the .inf files. I'm still going to work on the Bluetooth and wireless but at least I have one less device to figure out thanks to you.
Akule50
385 Posts
0
November 19th, 2005 22:00
Aloha Peter & Bobby,
Looks like you guys will have everything figured out by the time my son comes home for Thanksgiving... there won't be anything left for me to figure out! ;)
To Peter:
Were you able to install Win98SE with ACPI or did you use the "/p switch" to disable ACPI during the install?
If you're using APM, maybe that's why "the ACPI interface named tosrfec.sys could not be loaded" error message occurred? And maybe the older version is using APM?
Just incase it's needed:
"Enabling ACPI features in Windows98"
"ACPI-ON.EXE is used to update the Registry for Windows 98"
"How do I install or enable Advanced Configuration and Power Interface (ACPI) in Windows 98 Second Edition (SE)?"
But, if the older Toshiba Bluetooth Stack version functions desirably, with no problems... then there's really no need for ACPI.
Aloha,
Rod
PeterSwiss
99 Posts
0
November 20th, 2005 01:00
PeterSwiss
99 Posts
0
November 20th, 2005 01:00
PeterSwiss
99 Posts
0
November 20th, 2005 10:00
Message Edited by PeterSwiss on 11-20-2005 02:27 PM
texasboiler
8 Posts
0
November 21st, 2005 12:00
Peter, for some reason, I'm having trouble installing the Toshiba driver. Here's what I'm doing and hopefully you can tell me what I'm doing wrong:
1)double-click on "Tm1bt8.exe" and let it extract to C:\windows\desktop\Bluetooth.temp, then automatically run "bluetooth.exe",
2) system reboots,
3) I modified the file "tosrfusb.inf" located in C:\windows\desktop\Bluetooth.temp\Windows\ inf with the "my Bluetooth" modification you mentioned in a previous post. I added the line just before the "%TosrfUSB.DeviceDesc1%" line
3) upon opening Device Manager I have 6 "Other devices", 3 Composite USB Devices, PCI Card, PCI Communication Device and PCI Network Controller. These should be the Bluetooth device, modem and wireless card but I'm not sure which is which so I tried all three.
4) I double-clicked on each one and selected "Reinstall driver", then "Search for a better driver...", then "Specify a location". I entered "C:\Windows\inf", then "C:\windows\desktop\Bluetooth.temp\inf" and finally "C:\windows\desktop\Bluetooth.temp\inf\Win9x". Each time I got the message that Windows was unable to locate a driver for this device.
I get the same results when I tried the Belkin driver. I'm not sure that I'm looking in the right place for the drivers. Could you tell me how you got this to work?
Thanks,
Bobby
PeterSwiss
99 Posts
0
November 21st, 2005 15:00
Message Edited by PeterSwiss on 11-21-2005 11:16 AM
Akule50
385 Posts
0
November 21st, 2005 16:00
I had a hunch that might happen, but I was hoping that since the main drivers were already installed... ACPI "might" re-enumerate the devices (after restart) differently than it did during the Win98SE OS install. If I remember right... there were several fixes for ACPI problems with Win98SE.
As I mentioned before, try the "Unofficial Windows 98 SE Service Pack 2 (SP2)" since it contains over 70 Hotfixes for Win98SE. Alternatively, at least checkout the "WINDOWS 98 SECOND EDITION (SE) ESSENTIAL FREE UPGRADES + FIXES" for fixes that might pertain to your issues.
A few HotFix articles from MS:
"WMI Does Not Return SMBIOS Data"
"USB Enumeration Problems with OpenHCI Controller on Fast Computers"
"Fatal Exception Error Message in Openhci.sys When Devices Connected to USB Controller"
"General USB Troubleshooting Issues Specific to Windows 98 Second Edition"
And a "Win98SE USB Guide" ("click here").
I myself, would like to try the"98SE2ME.exe transplant" ("click here"), since I use some WinME files for Win98SE, anyway. When I have the time... I'll give it a try...
Aloha,
Rod
texasboiler
8 Posts
0
November 21st, 2005 16:00
It seems I neglected to investigate a little further. After I looked at Device Manager and discovered that all three "Composite USB Device" listings were gone. Also, when I look under Ports (COM & LPT) there are 11 Bluetooth Serial Port entries (COM3-13). Also, I opened "My Bluetooth Places", then "My Device" and was able to start the Bluetooth Serial Port, File Transfer, Information Exchange and Network Access services. The Dial-Up Networking and Fax services failed to start because no modem could be found. The Information Synchronization service failed to start because "The 'Save Objects in PIM' is not checked in the Configuration Panel". The problem now is that when I try to search for devices, nothing happens. I wondering now if everything installed OK, it's just that I don't have things configured correctly yet.
To finally answer your question about the DEV for the USB2 controller, it is indeed on
265C. Sorry, it took so long for me to find it. I'm sure you probably didn't need that any more since you were able to get USB2 working anyway.
Now, I'm going into the registry to see if I can determine what the other three devices are that are Unknown.
Thanks,
Bobby
PeterSwiss
99 Posts
0
November 21st, 2005 17:00
PeterSwiss
99 Posts
0
November 21st, 2005 19:00
Hello Bobby and Rod
I tried the unofficial Windows 98 Service pack, but it did not improve the relative situation, all the problems in the ACPI variant remain (USB mouse is updated 5 times a second, conflict on the mentioned ACPI BIOS device). Non-ACPI is still good of course.
I have the impression that the Belkin and the Toshiba Bluetooth drivers are the same at the transceiver level, just Toshiba complains about tosrfec.sys and Belkin ignores silently. User interface and services offered are however different.
It seems the Dell Latitude D610 owns a BCM5703 Gigabit Ethernet controller (10/100/1000). There is a complimentary reference driver at Broadcom, the download page is http://www.broadcom.com/drivers/downloaddrivers.php. The driver is named win_me_98-8.39.1b.zip (72kB).
Greetings, Peter.
PeterSwiss
99 Posts
0
November 23rd, 2005 08:00
PeterSwiss
99 Posts
0
November 25th, 2005 13:00
I can't find the specs on what "USB 2.0 chipset" the I-6000d is using (might be found in WinXP’s Device Manager). But since I read somewhere that the "ALi / NEC USB 2.0 Chipset" might be the most used... I'm guessing the new USB 2.0 drivers upgrade at the top of "this page" , might work.
texasboiler
8 Posts
0
December 2nd, 2005 16:00
Sorry, I've been quite busy lately with other things and unfortunately have not been able to spend much time working on my computer. I still am unable to load drivers for Bluetooth, the modem and the wireless.
I did some poking around in my regestry (98 partition) to try and figure out what the 6 devices were that were not loading. As I previously mentioned, I have a PCI Card, PCI Communication Device, PCI Network Controller and 3 Composite USB Devices listed in Device Manager. Peter had proposed the following in an earlier post:
My proposal is:
PCI Card = Secure Digital Slot
PCI Communications Controller = Ethernet, or did you install that already
PCI Network Device = Wireless
This was mostly correct. The PCI Card is my Conexant D110 modem. The PCI Communication Device is a GemCore Based SmartCard Container, and the PCI Network Device is the Intel PRO/Wireless 2200BG. The three "Composite USB Devices" are all related to Bluetooth.
I then started looking at the .inf files associated with each of these in XP and found that the modem and Bluetooth .inf files are Win98 files (their signature is $CHICAGO$) and the wireless and smartcard .inf files are NT based (signature = $WINDOWS NT$). My question is: can the two $CHICAGO$ .inf files be modified slightly so that XP will accept them and load these devices? I am going to mess around with those and see if I can get it to work.
Peter, do you have all your devices working now or are you still having problems?
Best regards,
Bobby
PeterSwiss
99 Posts
0
December 2nd, 2005 17:00
Hello Bobby, you do not need adaptions from Windows 98 to Windows XP (why). The chicago and Windows_NT signature are both understood by Windows 98 and Windows XP.
For Modem you need the reference driver mentioned earlier in this thread from Conexant. Then you have to modify both the..M2.inf and the MM.inf for the device ID. That's it.
Regarding Bluetooth, first you need USB2. That you already found. Then you need a Bluetooth stack. We mentioned two that install and seem to work.
I do not exactly understand why there could be problems with modem and bluetooth, please precise if there are.
For Smartcard I believe there are chances for ordinary modding, for Wireless chances are less.
Regarding smartcard slot, respectively I do have an SD Card slot, probably a Ricoh R5C821, I did not find a windows98 driver and I am still in the process of going backwards. This is supported generically in WindowsXPSP2, and Ricoh does not provide free reference drivers. I do not yet give up. The difference between W98 and WXP is in the way how the driver module (some xxx.sys) is declared in the INF file (Service directives versus Devloader and DeviceVxds directives). The drivers are uniformly "services" in Windows XP, where in Windows 98 the directives depend on the kind of device. However I do need to do it more carefully, short of studying the DDK!
Regarding Wireless, it does not look easy. The INF file references a so-called coinstaller, that is a module which does all the essence of the installation (named w29NCPA.dll). The coinstaller mechanism was introduced for Windows 2000 and therefore can't possibly be understood in Windows 98. A few wireless drivers for Windows98 already resisted my attempts. I still have the Intel Wireless5000 family for Windows 98 driver before me. Could be that the BG2200 resp. 2915, 2100 are completely new designs. And then the best bet for Wireless is to obtain an external USB wireless dongle, or simply a wired ethernet connection.
Best regards, Peter
texasboiler
8 Posts
0
December 2nd, 2005 18:00
I tried your suggestions regarding the modem again and it worked! I don't know why it didn't work the previous times I tried it (obviously operator error) but at least now the modem loaded correctly and I can communicate with it. I will have to try dialing out later tonight. Thanks for your help and thanks for the information regarind the .inf files. I'm still going to work on the Bluetooth and wireless but at least I have one less device to figure out thanks to you.
Best regards,
Bobby