DOS setup for Orinoco wireless PCMCIA <--> Windows network

[Edward Mendelson]

Hello,

I've got a laptop with a Lucent Orinoco PCMCIA card, which works perfectly
under Windows. However, I'd like to be able to boot to DOS and use the
wireless card to send files back and forth to a Windows machine, using
either NetBEUI or TCP/IP.

Has anyone managed to set up a DOS system that works this way? If so, would
you be willing to post or send the relevant .sys, .bat., .ini, and .cfg
files?

Many thanks for any help...

Edward Mendelson

best address (without the spaces and with a real @ sign, of course):
emendelson (at) compuserve.com

[Tim O'Neill]

Think of wireless interface cards, or any network card, as after market
wheels and tires for your car. As long as you have the right size and bolt
pattern, you can install them on your car. If, however, you are driving a
sled, you have no place to install wheels or tires. DOS is a sled, network
wise.
"Edward Mendelson" <edward_m...@ziffinvaliddavis.com> wrote in message
news:%MSC9.30434$aB1....@nwrddc02.gnilink.net...

[Jeremy Parr]

Tim O'Neill wrote:

There are plenty of DOS network drivers. But the problem is, no DOS wireless
drivers AFAIK.

Jeremy

[John Roland Elliott]

There are DOS packet drivers for Orinoco and clones but the skills to get
Windows networking running over a packet driver are rare these days. If you
follow this thread

http://groups.google.com/groups?threadm=26cfcb15.0209100807.56ad7159%40posti
ng.google.com

you'll find a post by Halfton where he indicates that he had NetBEUI and TCP
working. Maybe he'll be of some help.

"Jeremy Parr" <js...@netbahamas.com> wrote in message
news:uvnrv7r...@corp.supernews.com...

[Halfton]

Q) are there dos "ndis2" drivers for Wavelan/Lucent/Orinoco cards ?
A) yes, you must also revert firmware
ftp://ftp.orinocowireless.com/pub/software/ORiNOCO/PC_Card/DOS/

Q) will it work with NetBEUI or TCP ?
A) yes, www.bootdisk.com www.bovistech.com

Q) how well does it work ?
A) not very
if you want to Ghost or Drive image a laptop get an ISA/16bit wired nic
"PCI/Cardbus can work if the mfg has Packet drivers or Point enablers, but
it's a hassle"

Note
the fastest way to Ghost or Image a laptop is to get an adapter to connect
your 2.5" drive up to a desktop IDE chain, these can be found locally at
most decent PC shops
http://www.tigerdirect.com/images/SKUimages/medium/C184-17705.jpg

hth & gl
Joe

[<phil>]

Well, not actually.
I have two MS-DOS machines here which I use for some silly stuff.
(one with v5.0 and the other running v6.22)
Both of these machines share the network in my house with the
following other "boat anchors":
A Mac Plus, an Amiga 2500, a win95 box, and a machine running win98se.

The v5.0 (DOS) machine is used as a packet sniffer, reporting all the
traffic on my LAN. The v6.22 unit is used to follow on-line chat
while I'm in my garage. (using Microsoft Workgroups for DOS)
I know with all the abundant wintel machines out there I could/should
be running winXP or 2Kpro on all my stuff, but where's the fun in
cookie-cutter computing?

I would gladly use a wireless card in the v5.0 box (it's an hp200lx)
but so far, the mindset of programmers is not support, it's "get the
money", so there's not much in the way of drivers.

"DOS" ain't dead, it's just been left behind by the population who
does nothing for themselves.

[John Roland Elliott]

Good for you, Phil. I, too, have wasted countless enjoyable hours fooling
with antediluvian networking artifacts. I miss the good old Tinker Toy
network construction set days.

What's the sniffer you're running on the DOS machine? What network interface
does it depend on? If it's packet driver or ODI, you could probably switch
over to wireless using an Orinoco wireless adapter with the drivers that
Halfton pointed to at
ftp://ftp.orinocowireless.com/pub/software/ORiNOCO/PC_Card/DOS/. (At the
risk of being labeled a nitpicker and a troll,) I didn't find any real mode
ndis drivers there, though.

"<phil>" <root@domain> wrote in message
news:3dfebf2...@news.net1.net...

[Halfton]

"John Roland Elliott" <JohnRolandE...@m-attbi.com> wrote in message
news:mrHL9.189269$pN3.16326@sccrnsc03...
snipped troll BS from ID-10T

yes, you are one Dumb Nitpicking Troll w/o one whit of a clue on how to find
anything, even when handed the starting points ;-)
ftp://ftp.orinocowireless.com/pub/software/LEGACY/CARDS/PCMCIA/v400/DISK/pcm400.txt

here's an excerpt just in case you don't know how to open notepad or use the
edit/edlin commands from a dos prompt

" DOS NDIS 2 driver:
\MSLANMAN.DOS\DRIVERS\WAVELAN\WVLAN09.DOS v.4.10
\MSLANMAN.DOS\DRIVERS\WAVELAN\PROTOCOL.INI
\MSLANMAN.DOS\DRIVERS\NIF\WVLAN09.NIF
\OEMSETUP.INF
\OEMSETUP.WFW
\OEMSETUP.IBM "

enjoy
Joe

[John Roland Elliott]

Thanks for correcting your error, Halfton. I'm glad I didn't waste any of my
time trying to correct it for you.

"Halfton" <hal...@pickup.invalid> wrote in message
news:pjML9.36924$4W1....@nwrddc02.gnilink.net...

[Halfton]

"John Roland Elliott" <JohnRolandE...@m-attbi.com> wrote in message

news:0t%L9.388465$WL3.116281@rwcrnsc54...
snipped troll bs

hey ID-10T
I didn't correct anything but your stupidity ;-)

enjoy
Joe

[John Roland Elliott]

Well, actually you're right when you say you "didn't correct anything". It
turns out the first link you posted didn't have any ndis drivers and the
second link you posted was for the "Legacy" adapter and that adapter doesn't
work with any 802.11b equipment, only with the legacy Lucent WaveLAN and
Digital RoamAbout lines, which both predate the 802.11b spec and are not
compatible with it. Want to take another try?

It turns out, counting your post about DWL-660 being a rebadged Cisco 350,
that's three times this month you were wrong. A good rule to follow when you
find yourself standing in a hole is "Stop digging."

"Halfton" <hal...@pickup.invalid> wrote in message

news:A65M9.32589$VA5.3...@news1.news.adelphia.net...

[Halfton]

"John Roland Elliott" <JohnRolandE...@m-attbi.com> wrote in message

news:J17M9.389927$%m4.1...@rwcrnsc52.ops.asp.att.net...
snipped troll BS

hey ID-10T
you are now a proven sore looser of an Idiot troll

lucent/agere/orinoco/wavelan silver/gold cards were, are and always will be
compatible with 802.11b standard, immaterial of driver used, now if your too
dumb to use the proper Firmware, that's "once again" your stupidity showing
through ;-)

enjoy
Joe

[John Roland Elliott]

Comments about the precious metal cards, while fascinating, are irrelavent.
The link you posted,
ftp://ftp.orinocowireless.com/pub/software/LEGACY/CARDS/PCMCIA/v400/DISK/pcm
400.txt, is for hardware that predates the precious metal designation, and
is incompatible with, the 802.11b standard.

It appears to me that you've made up your mind and don't want to be confused
by facts, but in case I'm wrong and you're actually interested, here's a
1999 Technical Bulletin from Lucent wherein they demonstrate that "WaveLAN"
is not synonymous with 802.11b like you seem to think:
http://www.novocomp.de/prod/wirl/WLAN/Bilder/Download/TB-023.pdf.

A short quote from that:
"When your WaveLAN network is based upon WaveLAN legacy products (typically
the WaveLAN 915 MHz product line) you may consider migrating to an IEEE
compliant network based on WaveLAN IEEE 802.11 compliant 2.4 GHz radio
technology."

The word "legacy", which also appears in your link, is the key. The legacy
stuff, while not always 915MHz --- sometimes it's 2.4GHz, is never 802.11b.

"Halfton" <hal...@pickup.invalid> wrote in message

news:WW8M9.32883$VA5.3...@news1.news.adelphia.net...

[Halfton]

"John Roland Elliott" <JohnRolandE...@m-attbi.com> wrote in message

news:cXlM9.397834$P31.145772@rwcrnsc53...
snipped ID-10T troll BS

hey ID-10T
Wavelan "Legacy" included both 900mhz 1mbps & 2.4ghz 2mbps hardware

the ndis2 drivers from previous link work on later 2.4ghz cards at 2mbps max
forceing the AP or AdHoc partner to 2mbps is the most that's needed for
interoperability

research better next time ;-)

enjoy
Joe