9 replies
by sgt_shultz
even if you could get the USB working (needs to be supported in the BIOS)I would throw up my hands at the wireless part. but check mfg website for dos drivers...
you need 16 bit drivers for everything. if not posted on mfg website, not worth it. just put in hardwired ethernet card with dos drivers. there are lots of them...
what program is this?
does it run in DOS Mode or DOS shell within Windows?
by sgt_shultz
by frogsnot
Thanks for your reply Sgt_Schultz. This program is a money wiring program for Western Union. I have already have the USB NIC. It is an AirLink 802.11g USB 2.0 Adapter. There are no 16 bit drivers on the CD, and I am having trouble finding support for this product. I sent an email to Airlink and got a reply right away that said:
"I am out of the office and will return on Monday 8/02/04"
Is it possible Airlink has only have one person working the tech support department? Hard to understand why I would have to wait 5 days for an answer. I think next time I will buy from a different manufacture.
by cg it
I agree with Sgt Shultz with the wireless thingy.... chuck it out the windows and go wired.
USB in DOS If that is all they got for modems is USB might be tough to find drivers maybe drivers.com might has something from way back when in their archives. Not sure if DOS 7.0 has USB support or not. might check out DOS 7.0 for USB support and if so grab a copy off of Ebay.
by willcomp
Even if you can finagle USB support in DOS, which is doubtful, there definitely won't be any drivers for you wireless adapter.
Configuring an ethernet DSL connection to a remote computer in DOS, even if possible, is beyond my expertise.
by mr-rich
This may take some tweaking with the Autoexec.bat and Config.sys files, as long as you have the drivers. I also believe you need to have the "USB Legecy" disabled in the BIOS and assign IRQ to USB host controller.
Now the hairy details for DOS old-timers like myself who actually enjoy editing config.sys.
The driver switches you can use are: device=(path)\USBASPI.SYS [/e] [/o] [/u] [/w] [/v] [/l[=n]] [/f] /r] [/slow] [/nocbc] [/norst] [/noprt]
The driver scans USB controller specs by default, but you can limit which controllers are enabled using these switches:
/e EHCI spec (USB 2.0)
/o OHCI spec (newer USB 1.x)
/u UHCI spec (older USB 1.x)
/w Wait, displays text message for attaching or swapping USB devices
/v Verbose, shows status messages - recommended
/l[=n] LUN, specifies highest LUN # to be attached to device ID (default=0)
CONFIG.SYS (sample):
device=c:\himem.sys
devicehigh=c:\emm386.exe
DOS=HIGH,UMB
lastdrive=Z
device c:\=HIMEM.SYS
devicehigh c:\=USBASPI.SYS /v /w /e
devicehigh c:\=??????(what ever your device is)
Hope this help, wish you the best.
by frogsnot
by cirvin
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending