>Is there a way to network a DOS laptop to a Win98 computer without
>resorting to DOS mode? The laptop currently has no hard drive and is
>networked to a laptop with a 193MB-compressed hard drive and a broken
>floppy and screen. The Win98 computer has a boot-sector virus,
>though. I will wait until I can free it of the virus before
>implementing any suggestions.
Looks like a lot of work ahead.
Why do you want to contact the DOS laptop with the Win98 computer?
--
**** WARNING **** The web-hoster Globat.com steals money from your
credit card account. If you are a customer of Globat.com, never give
them any credit card information. If you can't erase the information,
then do delete the old card and get a new one! **** WARNING ****
> Is there a way to network a DOS laptop to a Win98 computer without
> resorting to DOS mode? The laptop currently has no hard drive and is
> networked to a laptop with a 193MB-compressed hard drive and a broken
> floppy and screen. The Win98 computer has a boot-sector virus,
> though. I will wait until I can free it of the virus before
> implementing any suggestions.
If you just want to do a one off file transfer, it's easier to take the hard
drive out of the machine and mount it (I assume it's Drivespace rather than
Doublespace or something else) in Win98. If you want to network it there's
some instructions at
http://technet.microsoft.com/en-us/library/cc750214.aspx (about halfway
down, after the instructions on copying the files from NT) and the actual
network client disks can be downloaded from
ftp://ftp.microsoft.com/BusSys/Clients/MSCLIENT/
mh.
--
http://www.nukesoft.co.uk
http://personal.nukesoft.co.uk
From address is a blackhole. Reply-to address is valid.
You misunderstand. One laptop has no hard drive. The other has a
hard drive but no working floppy and a broken display. I want to use
the Win98 computer as a hard drive instead and still be able to work
on it. BTW, I'm using a parallel cable to connect the computers.
I'm quite confused too, on which is which and what have what. Let's just
assume that the laptop that has no hard drive (and good display) is
called laptop A, and the other laptop that has a hard drive (and Win98),
no floppy drive, broken display is called laptop B.
AFAIK, there's nothing much you can do with a parallel/serial direct
connection without an OS on both laptops.
For laptop A, it's basically a dumb computer unless it has a network
interface (NIC, not parallel/serial port) which has a boot ROM, AND the
laptop BIOS can boot via network. Of course, this will require laptop B
to have a bootp server and an NIC too. With this, you can boot your
laptop A into Win98 via network using laptop B as the server.
> On Aug 10, 7:19�pm, Marcus Houlden <s...@nukesoft.co.uk> wrote:
>> If you just want to do a one off file transfer, it's easier to take the hard
>> drive out of the machine and mount it (I assume it's Drivespace rather than
>> Doublespace or something else) in Win98. If you want to network it there's
>> some instructions athttp://technet.microsoft.com/en-us/library/cc750214.aspx(about halfway
>> down, after the instructions on copying the files from NT) and the actual
>> network client disks can be downloaded from ftp://ftp.microsoft.com/BusSys/Clients/MSCLIENT/
>
> You misunderstand. One laptop has no hard drive. The other has a
> hard drive but no working floppy and a broken display. I want to use
> the Win98 computer as a hard drive instead and still be able to work
> on it. BTW, I'm using a parallel cable to connect the computers.
If I've got this right, you have two non-functional machines, one with no OS
and one with no way of using the OS. How exactly do you intend to get either
of them to do anything? You won't be able to set up sharing on the Win98
machine if you can't use the display and once you've got a floppy with a
basic OS and drivers, that doesn't leave room for much else. You could
probably attach an external monitor to the Win98 machine, but if you decide
to go for interlnk, you have to run intersvr in DOS mode with nothing
else running. It is also extremely slow and if it's a FAT32 disk it can
destroy data. Realistically I think your best option is to salvage the HD
from the Win98 machine and replace them both with one that actually works.
Would CTTY work? The Win98 machine would handle the FAT32
filesystem that way. The other laptop would be a dumb terminal
class machine then.
Regards,
Steve N.
Are you on drugs dude?
If you have a boot disk with fdisk you might want to try fdisk /mbr
and if you do not then you could download a boot disk image but you
will need to add fdisk.exe to it...
http://www.filegod.netfirms.com
--- news://freenews.netfront.net/ - complaints: ne...@netfront.net ---
I wrote this a long time ago, so the references are a bit dated, however it
still applies (at least with Win98) - You may need to enable NETBEUI
protocol on the Win98 box as it is far simpler to get working.
--------------------------------------------------------------------------------------------------------------
Q: How can I access as windows network from DOS?
Microsoft has the Lan Manager client for DOS, which provides access to
MS networks. I don't know if it is still available as a product, however
I found it in the CLIENTS directory of the WinNT4 server evaluation disk
that came with Microsofts "Internet Information Server" evaluation kit.
There is another DOS client called "The Workgroup Connection". I found
it in the software library samples of an older (Dec95) MS TechNet CD.
If you have Windows For Workgroups, you already have everything you need
to access an MS network from DOS. If you already have WFW setup on the
machine (and plan to leave it there), you don't have to do anything...
Just use the NET command to activate the DOS network client outside of
windows.
If you want to use the DOS client without having the rest of windows
hanging around, you can distill it down to a minimum set of files.
Note that is provides a client only... you have to run WFW to share
resources on your machine:
WFW files needed to access network from DOS:
NET.EXE
NET.MSG
NETH.MSG
IFSHLP.SYS
NDISHLP.SYS
PROTMAN.DOS
PROTMAN.EXE
WFWSYS.CFG
SYSTEM.INI
PROTOCOL.INI
You also need the real mode driver for your network card, which will
be listed in the netcard= entry of the [network.drivers] section of
SYSTEM.INI. In my case, I use NE2000 compatibles, and SMC/WD 8013's,
which use one of the following:
NE2000.DOS - NE2000 Compatible
SMCMAC.DOS - SMC/WD 8013
If you want to trim SYSTEM.INI, you need only the following sections:
[Network]
[network drivers]
[Password Lists]
Make sure the devdir= entry under [network drivers], and all
of the entries under [Password Lists] point to the directory
where you have setup these files.
You have to load IFSHLP.SYS in CONFIG.SYS at boot time, just
as you do for WFW.
Once setup, you can use the NET command to start the network,
make connections etc. Use /? for help: NET /? | MORE
--
dave09@ Low-cost firmware development tools: www.dunfield.com
dunfield. Classic computer collection: www.classiccmp.org/dunfield
com