Name: PersistencePain Date: July 12, 2003 at 14:31:19 Pacific Subject: DatOptic Speedzter 2.5 USB DOS OS: DOS CPU/Ram: P4 / 524MB
Comment:
Hello,
I have a DatOptic Speedzter 2.5 that I'm trying to get to work with USB in DOS. Naturally, I'm trying to use the DatOptic drives (by MediaLogic), but it's not working. (I've tried the Panasonic usbaspi.sys & some others w/ no success.) It generates the following errors:
ERROR : EHCI memory mapped I/O can not assigned. ERROR : Target USB device not found.
Does anyone know how to get this working?
I'll post the entire verbose mode printout & some more details at my website.
I'm pretty sure the USB ChipSet is made by Intel. It's onboard. I don't know how to get a version #. The Dell GX260 is a fairly new machine.
I've spent a lot of time looking at www.mwpms.uklinux.net/usbfire.txt
I've tried: Panasonic DUSE Novac (Mhairu) Medialogic
DUSE seemed to get closest to working. Its error was something like "C Drive not installed", which didn't make any sense to me, but it seemed to properly initialize the USB. I tried "/late" followed up with "init" from autoexec.bat. That didn't help.
Since the Medialogic driver is distributed by DatOptic, the manufacturer of the Speedzter, one would think it would work. It's probably a matter of using the right switches. I've taken a stab at a few, but with no success. I can't find any documentation. Do you know what switches are available for the Medialogic driver? The only guess that has shown a different result is "/v".
Have you tried either the Panasonic or Novac in conjunction with the DI1000DD.SYS driver??
Also try the making a minimal boot disk, in the command promt window of windows SYS A: then adding the following lines at the begining of config.sys;
device=usbaspi.sys /v/w/u device=di1000dd.sys
I have found in one case that DOS was allocating a memory area used by these drivers, therefore against common practice load them before HIMEM.SYS & EMM386.EXE etc
btw were you using the Medialogic driver as the complete downloaded boot floppy?? or just extracting files required??
Definitely, GX260 is using USB2.0 from Intel's 845 chipset so obviously you want the DATOptic Speedxter to run at USB2.0 speed.
Some of the options in Panasonic's v2.06 driver do work in the Medialogic's v2.01 USBASPI.SYS driver.
From your website: > - This floppy, when loading the USB driver, generates the errors below. > - I can't find any documentation for the usbaspi.sys or any other file in this collection. > - I've also tried without success: - Panasonic's usbaspi1.sys ver 2.06 > The following text is produced when config.sys attempts to load usbaspi.sys with the /v switch during the USB boot sequence. > If the /v switch is removed, only the ERROR lines are generated. > If the /u switch is used, the EHCI error goes away. > I can't figure out how to fix the "Target USB device not found" error. As a result, the driver isn't loaded, the follow-on driver the HD won't load either. -------- ASPI Manager for USB mass-storage Version 2.01 Copyright (C) 2000-2002 Medialogic Corp. All rights reserved.
From your error message: 1. USBASPI.SYS cannot map your EHCI controller. What happens if you use /E option instead of /U ? 2. Do you have any add-on card (PCI) installed? Can you try removing it first?
I will try the drivers on a Dell and get back to you...
To answer all questions from above: - I'm using an external power supply for the Speedzter. - I turn the Speedzter on before booting the computer. - I'm booting from a floppy made by the DAT.exe on the DatOptic website. I've copied various other drivers to this disk so I can easily switch from one driver to another by editing config.sys.
I tried a few different switches.
/e - with Medialogic - generates another error "PCI UHCI/OHCI/EHCI USB controller not found". Despite "/v" text is severely chopped off. - with Panasonic - doesn't generate the above error, but the /v text becomes much shorter and it still can't find the target device /u - seems to be most promising. I'm pretty sure the Speedzter isn't capable of USB2 anyway. /slow - with Medialogic - illegal option - with Panasonic - tells me it's entering slow mode, but doesn't fix any problems
I tried using di1000dd.sys, but since the ASPI Manager is the problem, di1000dd.sys simply errors out "ASPI Manager not loaded". This is the same as what happens with nj32disk.sys (Medialogic).
When using the /u switch (either Medialogic or Panasonic), the only error which seems to be stopping the chain is "Target USB device not found". This is the first error to appear. The other error (which comes after this) is associated with the disk driver, not the USB controller driver.
Since it works on Windows, could you go to ControlPanel - System, enter Device Manager and check out what resources are used by each USB Host Controller (you should have UHCIs and an EHCI)?
Compare with what is reported by USBASPI.SYS
Finally, please look for any conflicts - click on resources by connection or type and see who are sharing I/O, memory or IRQ with the Enhanced Host Controller reported.
/u - seems to be most promising. I'm pretty sure the Speedzter isn't capable of USB2 anyway.
I think if you are really happy to operate in USB 1.x mode (max 12Mbps) then this is your best option. What it does essentially is allow operation of UHCI host controllers and disabling the other host drivers (EHCI and OHCI).
However, looking at the DAToptic website, all I see are USB 2.0 enclosures so you might be missing out on something.
Here is the result of my tests on TWO DELL OPTIPLEX PC's - one is GX260 (BIOS Rev A05) and the other is an L60 (BIOS Rev A00). Both use the 82801DB/DBM to provide USB 2.0 ports onboard.
In BIOS setup, both have under Interface Devices: USB Emulation = OFF USB Controller = ON While under PCI IRQ, both have 4 Intel USB Controllers each using interrupt 9, 11, 10 and 3 respectively.
With the DAToptic Speedzter disk, I got exactly what you reported with the Medialogic 2.01 USBASPI.SYS /V /W which is this: ERROR : EHCI memory mapped I/O can not assigned. ERROR : Target USB device not found.
However, when I replaced the driver with the Panasonic 2.06 USBASPI.SYS /V /W it WORKED and the UHCI controllers are I/O mapped while the EHCI controller was MEMORY MAPPED - for the USB2.0 host controller, you get a line going like this: Controller : 00-0n-n VID=8086h PID=nnnnh (nnnnh-nnnnh) EHCI : MEM=FFA00800h-FFA00BFFh(1024Bytes)
Your Resources by connection screen capture is actually displaying the USB 1.x UHCI host controllers (24C7, 24C4 and 24C2) but what we are looking for is under Memory - we need to see what address range the Intel PCI to USB Enhanced Host Controller (USB 2.0) is using.
I suspect 3 possibilities: 1. Because you are using a USB mouse, is your BIOS setting for USB Emulation ON? Would setting it OFF cause different operation? 2. You have a number of SCSI hosts - 5 different ADAPTEC controller entries, a Dell PERC, a Future Domain HA, HP NetRAID 1Si and a PCMCIA SCSI controller installed and one of them probably conflicts with the Intel EHCI standard memory map address FFA00800-FFA00BFFh. Can you remove all of them for a moment and check for conflicts by returning one at a time? 3. The PCI BIOS has already mapped EHCI to a non-standard address space and the only way to put it back to default is clear the BIOS config (and remove all add-on cards) - but this may cause Windows configuration settings to change drastically so this is NOT recommended.
I added a screenshot to my webpage for the memory section of Resources by Type.
I switched USB Emulation to OFF in the BIOS and used Panasonic /v /w. The USB mouse still works fine in Windows, and the EHCI error did not show itself when booting from the floppy.
The only error remaining is "Target USB device not found." This prevents the ASPI Manger from loading, which prevents the HD driver from loading as well.
madmaxUSB yes you are correct about FAT, with my external compact flash / smart media if I format them under XP, and I would presume W2K, they are not readable under real DOS, though they are recognised as drives and assigned drive letter. Great you achieved another device working!
Was the first comment directed at my web page??
PPain, would personally remove all PCI cards etc and unplug IDE's and USB mouse, just run from a boot floppy and try to see if recognise drive, to see if there is memory area conflict!
This computer doesn't have any PCI expansion cards. Everything is onboard.
The HD in the Speedzter was formatted Fat32 under Win2k. Unlike your experience, x86, the Speedzter isn't recognized as a drive or assigned a drive letter.
I've tried disconnecting the mouse.
I've tried moving around to different USB ports. I can get the Speedzter to move to different USB controllers, but not to the EHCI controller.
Oops - sorry for the misdirection - your Resources by Type shows the Speedzter with a Toshiba HD is actually just a USB 1.x device - at least the USB 2.0 functionality is now available in DOS ;-)
So the root problem was even with UHCI, we get "Target USB device not found."
Question - are you using the correct version of USBASPI.SYS from Panasonic - your webpage indicates ASPI Manager for USB mass-storage Version 2.01 when the latest is actually v2.06 ...
Note that USBASPI.SYS actually does see your Speedzter because scenario 3 has : |-- VID=07F7h PID=000Bh FS but scenario 4 doesn't.
So the problem is USBASPI somehow doesn't think of the device as a compatible mass storage device - which is in itself strange as the experience of others is it is usually recognized and mapped as an ASPI device but the next driver cannot map it to a disk.
There are a coule of reasons I can think of on why this is happening: 1. Something is non-standard about the partition created. Maybe if we open the case, connect directly to a PC IDE port, backup, repartition under just DOS, and restore, the problem would disappear...?
2. Or alternatively, if we open the case, connect directly to a PC IDE port, backup, remove all partitions on that disk and put it back in the Speedzter case. Then boot from DOS and load the USB drivers to see if we can get it to recognize the disk, and then create the partition. After a reboot, format the partition. If it all works, boot in Windows, connect the USB drive, map the external drive and restore all data.
3. Something is non-standard about the USB-IDE bridge (maybe early generation) making it incompatible with these drivers. Have you tried the other drivers like IOMEGA ASPIUHCI.SYS driver?
The v2.01 was a typo. Now corrected. I actually took digital photos of the screen as it scrolled by, so I've verified it's actually 2.06.
I think I'll reFDISK & reformat the HD under DOS on a different computer via firewire. Maybe that'll accomplish the same thing as your two HD removal options above.
If that doesn't work, I'll be asking where to find that IOMEGA ASPI driver. I hadn't heard about that one.