| Home | Forums | Register | FAQ | Search | Today's Posts | Mark Forums Read |
|
Welcome to the misticriver forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
| Tags: t30, win98 |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Solution: getting T30UMS to work in win98
Hi
My name is Peter and I am from Toronto, Canada. I just want to outline how I got my T30 firmware 1.71UMS to work with Windows 98 First Edition using Usb 1.1 ports. I've noticed while lurking around here that a number of people were having the same problem that I had with Windows 98 and nobody seemed to have a solution. So here goes. I recently bought a T30 (refurb) and upgraded the firmware to the 1.71UMS version. I am running Windows 98 First Edition and tried to install the win98 drivers from the Iriver website. Specifically the T30umd.inf file. Plugging in the T30 to the USB port would bring up a dialog box identifying the device as an Iriver T30 and asking for the driver. I would point it towards the directory with the T30umd.inf file and try to install it. Unfortunately it would try to install but would crap out. I'm a bit hazy on the details but I think it installed an "unknown device" which of course wouldn't work. Anyways I couldn't really find anything about it on MisticRiver but did notice that a few other people were having the same problem. So I started looking offsite and got LUCKY. I entered the following search terms [t-30 t30umd.inf] at groups.google.com which returned exactly one post. Here is the text of that post: ==================== ========start of usenet post================ ==================== =============== Just posting this so that people with the same problems I had dont have to spend hours wasting their time - a google search should find this posting: Anyway, I bought an iriver T30 mp3 player here in Australia to connect to my Win98se ( windows98se ) computer. MisticRiver Once plugged in, control panel / system / device manager clearly shows the hardware is found, but it doesnt work because a driver could not be found for it. Why not? MisticRiverI ask myself... the CD that comes with the product clearly has a "Win98seDriver" directory with a T30umd.inf file... MisticRiverbut windows doesnt recognise it as a valid driver for that device. Much internet searching later, I come up with nothing useful. MisticRiver But to cut a long story short, a look through the windows registry shows that iriver has a vendor ID (VID) of 4102, and there are entries for 2 different product ID (versions?) of the T30. MisticRiver One has a PID of 1015, and the other has a PID of 1018. The driver supplied with the product is for the PID_1015, but the actual item in the box (as it turns out) is the PID_1018. MisticRiver Go figure. Of course windows was never going to use that driver. MisticRiver Soooo... the solution for me is to use the T30umd.inf driver supplied on the CD, but copy it somewhere else off the CD and make the modification in the file from: [iriver] %USB\VID_4102&PID_10 15.DeviceDesc%=USBST OR_BULK.install,USB\ VID_4102&PID_10 15 to [iriver] %USB\VID_4102&PID_10 18.DeviceDesc%=USBST OR_BULK.install,USB\ VID_4102&PID_10 18 (no text wrapping in the original file) All works fine now. cheers... ==================== ============end of usenet post ==================== ==================== ======== Now, luckily I had downloaded the following program for windows 98 that allows me to see view my Usb ports. You can download it from here Microsoft USB Viewer tool for Windows 98/ME [view USB devices connected to a PC; v4.10.1721] ftp://ftp.uni-linz.ac.at/Driver/Druc...cc/usbview.exe Using this program that views the usb port I plugged in my T30 and I got the following output: Device Descriptor: bcdUSB: 0x0110 bDeviceClass: 0x00 bDeviceSubClass: 0x00 bDeviceProtocol: 0x00 bMaxPacketSize0: 0x40 (64) idVendor: 0x4102 idProduct: 0x1019 bcdDevice: 0x0100 iManufacturer: 0x01 iProduct: 0x02 iSerialNumber: 0x00 bNumConfigurations: 0x01 ConnectionStatus: DeviceConnected Current Config Value: 0x00 Device Bus Speed: Full Device Address: 0x02 Open Pipes: 0 Notice the line with "idProduct: 0x1019". That is the id of the T30 for MY T30. Yours maybe different. In the t30umd.inf file we see PID_1015. So when Windows goes to install the device driver for the T30 it is looking, in my case, for a PID_1019 but sees a PID_1015 and craps out by installing an unknown device. So the solution for me was to change every instance of PID_1015 to PID_1019 in the t30umd.inf file. This occurred in the following areas of the t30umd.inf file. ( As opposed to our Aussie friend who did it only for the [iriver] portion. Maybe the file has changed since then.) [iriver] %USB\VID_4102&PID_10 15.DeviceDesc%=USBST OR_BULK.install,USB\ VID_4102&PID_1015 %SECUMS\DISK.DeviceD esc%=umspdr.install, SECUMS\DISK [Strings] MSFT="iriver" MfgName="iriver" USB\VID_4102&PID_101 5.DeviceDesc="iriver T30" SECUMS\DISK.DeviceDe sc="USB Mass Storage Device" Going back to the So I changed every instance PID_1015 in the above to PID_1019 and saved the file. I then removed the unknown device from my previous unsuccessful installation attempt and this time was able to successfully install the T30 driver. I am now able to use my T30 in UMS mode under Windows 98 First Edition. The only problem I am having is that sometimes when I plug the T30 in nothing happens. I have to unplug it and replug it in a few times to get it to take. I haven't played around with it enough to figure it out yet. I understand that win98fe may have had buggier usb drivers that were fixed in win98se. If anyone has had that type of experience or can comment i'd be interested to hear what you have to say. So, I hope this helps and I hope this isn't too long winded to be useful. Regards/Peter |