Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

MSDOS and VIA VT6212 USB 2.0 Contro

Original Message
Name: achim_compi
Date: March 26, 2006 at 13:36:52 Pacific
Subject: MSDOS and VIA VT6212 USB 2.0 Contro
OS: MSDOS 7.1
CPU/Ram: P4 1800
Model/Manufacturer: Jetway P4XFA
Comment:
Hello,

after two days of hard investigation on a old P4-1800 on Jetway P4XFA-Mobo with internal USB 1.0 and my new cheap external USB 2.0 Controller VIA 6212 connected to my new ICY-BOX IB351U, inside a Seagate 80 GB IDE-Disk, it works with MSDOS, especially Ghost 2003.

I tried following drivers under MSDOS 7:

ASPIEHCI.SYS V.13 (9 May 2003)+GUEST.EXE
ASPIEHCI.SYS V.07 (23 Apr 2002)+GUEST.EXE (delivered by Ghost)

USBASPI.SYS 2.20 + DI1000DD.SYS
USBASPI.SYS 2.06 + DI1000DD.SYS

DUSE 4.9

with alterning results - on one boot, it worked, on the next boot, it refused...

After all the following trials, for my environment, USBASPI 2.06 + DI1000DD seems to be the best.

To get reproducible results, I have to boot (Power-On or RESET-Switch, not CTRL-ALT-DEL !) with my rescue-cd (or boot-floppy), then, I have to wait until USBASPI wants me to plug in the disk, then I plug in then I press ENTER.

The last two days, I tried many things, Shadow-ROM/RAM off, Plug-Play on, disable internal USB and so on.

The only thing with my card is: the USB-Controller (better: the USBASPI.SYS ?) needs unshared IRQs.

I changed the PCI cards, so I found out, how my BIOS distributes the IRQs between the slots:
some slots are grouped to the same (then shared) IRQ, if a PCI-card wants more IRQs, BIOS shares them with the next slots/cards.

The boot-up-messages from BIOS became my main information source: the card needs 3 IRQs, two for the 2 UHCI-Controller and 1 for the EHCI-Controller.

In all cases, the EHCI-Controller must have an unshared IRQ. One of the UHCI-Controllers now also gets such one, but I'm not sure if this is a must-be.

I got the worst results when the EHCI device shared the IRQ with an ethernet adapter which was connected to a network - no USB detection at all.

The other experience that helped me was: the controller (or whatever) needs a real hard reset (Power-On, RESET-Switch) before plug-in the USB-cable. So I wasted much time with CTRL-ALT-DEL. I assume that the driver needs a "fresh" interupt at initialization to detect the device.

For testing, I got the best results in removing all PCI-cards except the USB controller and disabling all "internal devices" (internal USB, even COM: and LPT:), so the controller really will get an unshared IRQ and then boot with a MSDOS floppy with a boot-menĂ¼ to select the drivers, first, without HIMEM, CD-driver a.s.o.

After that, I changed BIOS and config.sys step by step towards my usual environment, hit the RESET button and watched what happened. From time to time I switched off power - surprise: again it didn't work, ok, go back one step.

Here now my config.sys (USBASPIO = 2.06):
device=himem.sys /v
buffers=80,0
dos=high,umb
lastdrive=z
device=VIDE-CDD.SYS /D:MSCD_O /L:GR /P:170,15
device=USBASPIO.SYS /v /w /slow /e
device=DI1000DD.SYS
...other stuff...

Hard to say: on my K8VX Athlon, UMBASPI worked immediately - even ASPIEHCI.SYS. In opposite to the P4-BIOS, K8VX initializes the internal USB 2.0 cards.

Maybe my experience of the last two days helps somebody in a comparable situation.



Report Offensive Message For Removal


Response Number 1
Name: franki
Date: March 26, 2006 at 22:23:35 Pacific
Subject: MSDOS and VIA VT6212 USB 2.0 Contro
Reply: (edit)
Why thankyou but see this is really aimed at Windows Ghost Users, if you search for posts on this forum by MADMAXUSB he has undertaken considerable testing of DOS USB.

VIA & ALi are not the most reliable of Chipsets on PCI Cards, NEC Chipsets seem to give less errors and conflicts.

Also if you list the USB ASPI etc as first lines in CONFIG.SYS you usually get less errors.

Personally prefer Acronis True Image which is Linux based and therefore has more mature USB Support.

If anyone wishes to try the Panasonic I have found a basic boot disk here, it is a Windows Self Extracting WinImage:

http:83.67.55.228/USBCDROM.EXE


Report Offensive Follow Up For Removal




Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: MSDOS and VIA VT6212 USB 2.0 Contro

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software




exessive internet traffic

ZoneAlarm Question. Blocked Connect

Windows Live Messenger Problem

Delete $Uninstall after SP3 updates

help for hp compaq laptop


The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC