----- Original Message -----
From: "Jean-Pierre Radley" <jpr@jpr.com>
Newsgroups: comp.unix.sco.misc
To: <distro@jpr.com>
Sent: Thursday, February 09, 2006 11:56 PM
Subject: Re: need some help copying a VOL.000.000 from floppy to HD
> IT Geek-dude typed (on Thu, Feb 09, 2006 at 08:25:05PM -0800):
> | This might be simple to the UNIX gurus but I need help copying a file
> | to the /tmp directory.
> | I notice there is like over a dozen mounted fd0, rfd-135ds18, etc...in
> | /dev
>
> None of them are mounted by default. Typing 'mount' doesn't show you
> any floppies mounted, does it?
>
> | SCO is different from linux and this is very frustrating. I just want
> | to be able to copy the drivers on to my hard drive. I can't figure out
> | for the life of me how to access the floppy drive in SCO 5.0.5
> | openserver.
> |
> | the driver installation notes calls for: Download VOL.000.000 and place
> | in /tmp. run 'custom'
> | and "install new" from 'media'. Easier said than done. Can anyone help?
> | I need to get this machine talking on the network with a 3com905c-tx
> | adapter.
>
> You probably have only one floppy on a modern machine, and you can mount
> it using
>
> mount /dev/fd0 /mnt
>
> But you probably don't want to mount it anyhow, because you can only
> mount filesytems, and you're implying that yuou have a copy of a VOL file
> on the floppy, not a filesystem. BTW, how did you write the VOL file
> onto the floppy?
>
> Try:
>
> dd if=/dev/fd0 bs=18b of=/tmp/VOL.000.000
Not to mention, if he's got a vol floppy (perhaps created by 3com and came
with the card) Then all he needs to do is stick the floppy in and type
"custom"
no mounting, no copying, no dd, etc...
But from the insufficient problem description he provided we can never the
less be the oracles he wishes for and deduce that what he probably did was
download a vol file from windows and write it to a floppy, which means he
has a file on a msdos filesystem on a floppy. (hint, that is the kind of
info you should have provided, not the typical user quality report of "it
doesn't work")
In which case he can do either
mount -f msdos /dev/fd0135ds18 /mnt
ls /mnt
cp /mnt/3C905.VOL /tmp/VOL.000.000
Or in the particular case of a dos/win floppy, no mounting at all.:
dosdir a:
doscp a:3C905.VOL /tmp/VOL.000.000
Then follow the custom directions for installing from media images.
Or he can go back to windows, use rawwritewin.exe to write that vol file he
dounloaded to a floppy as if it was a floppy disk image.
He claims to be familiar with Linux, so this should no problem, in fact, in
that case he should have no problem using a linux box to (w)get the same vol
file from wherever he got it, and use dd to write it to the floppy.
Then just put the floppy in the sco box floppy drive and run custom and
choose software, install new, from localhost, floppy drive.
If he thinks this is "frustrating" because it's "not linux", wait till he
tries to configure and use that nic he's trying to install.
With no brainless screen with a field where you can type in the default
gateway on 5.0.5...
And the brainless screens that there are, don't work well enough, such that
you have to know to go and look at, possibly doctor up a couple files
yourself after running netconfig but before rebooting.
Which brings to my attention that I have to take back part of the bad error
report shot, because he managed to say the os version, which doesn't matter
for the floppy access, but matters somewhat for the next step of configuring
networking to use the nic.
Brian K. White --
brian@aljex.com --
http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!