On Monday 24 January 2005 04:36 pm, [EMAIL PROTECTED] wrote:
> Thanks, will do. I like to leave this puter in linux at night anyway.
> The screensaver gives off more light to see my way to the john. It is
> also a nice level to wake your eyes up to. I use the linux slide show as
> screensave
Thanks, will do. I like to leave this puter in linux at night anyway.
The screensaver gives off more light to see my way to the john. It is
also a nice level to wake your eyes up to. I use the linux slide show as
screensaver.
On 24 Jan 2005 at 12:52, Mikkel L. Ellertson wrote:
> [EMAIL
[EMAIL PROTECTED] wrote:
I can tell you this much, the output is supposed to be three files of
information about the modem possibilities. I figured it was wrong
somewhere because of that and the gcc thing. I guess I need to know about
that also. I will try researching it on this end. Mayb
I can tell you this much, the output is supposed to be three files of
information about the modem possibilities. I figured it was wrong
somewhere because of that and the gcc thing. I guess I need to know about
that also. I will try researching it on this end. Maybe that would make
it wor
[EMAIL PROTECTED] wrote:
What I went through to import this output into this message you
wouldn't believe. First I typed it into my laptop, then saved it to a
floppy. Lastly my mail program allowed me to import it to a message.
Anyhoo this is the output I got from scandisk as well as
I cou
On Sunday 23 January 2005 20:31, [EMAIL PROTECTED] wrote:
>By golly ,it worked. It is in linux now. Now I have to
> figure out how to gunzip it. I assume it is done in a terminal,
> but as super user, root, or just plain me.
>Thanks for the drag and drop hint. It was telling me
> someth
By golly ,it worked. It is in linux now. Now I have to figure out how
to gunzip it. I assume it is done in a terminal, but as super user, root,
or just plain me.
Thanks for the drag and drop hint. It was telling me something about
can't read it, but when I looked the file was there.
O
On Saturday 22 Jan 2005 12:14 pm, [EMAIL PROTECTED] wrote:
>OK! It seems like more than one of you are suggesting I
> substitute something for the "a". I guess if I can see it then cp is
> the better route. If it works it shows some of our instructors need
> to go back to school or something
[EMAIL PROTECTED] wrote:
Still doesn't work. GR! This is exactly what I see as the path to
the file.
root
mnt
windows
temp
scanModem.gz
I tried in super user mode and logged on as root. It still won't work.
Maybe I should rename the file frustration.xxx:>) I will probab
On Saturday 22 January 2005 08:43 am, [EMAIL PROTECTED] wrote:
>Still doesn't work. GR! This is exactly what I see as the path to
> the file.
> root
> mnt
> windows
>temp
> scanModem.gz
>I trie
OK! It seems like more than one of you are suggesting I substitute
something for the "a". I guess if I can see it then cp is the better
route. If it works it shows some of our instructors need to go back to
school or something.
culatr2da = see you later today See I can get cryptic als
Eric Huff wrote:
What is this a:scanmodem.gz stuff? I just tried it on mine and
as expected, linux doesn't do anything with a:
Mine would be /mnt/floppy/scanmodem.gz
When running properly I believe it is supposed to read and
print out
what chip set you have in a winmodem. Very h
> > What is this a:scanmodem.gz stuff? I just tried it on mine and
> > as expected, linux doesn't do anything with a:
> >
> > Mine would be /mnt/floppy/scanmodem.gz
>When running properly I believe it is supposed to read and
>print out
> what chip set you have in a winmodem. Very hel
[EMAIL PROTECTED] wrote:
Handy explanation and it makes sense. I found out my problem is still
getting the file from either the floppy or the windows side of this beast.
Maybe when I get it into linux, then I can gunzip it and proceed. I just
can't make mcopy work. In my home directory I ca
Handy explanation and it makes sense. I found out my problem is still
getting the file from either the floppy or the windows side of this beast.
Maybe when I get it into linux, then I can gunzip it and proceed. I just
can't make mcopy work. In my home directory I can look to windows to te
[EMAIL PROTECTED] wrote:
OH! Then chmod involves an already decompressed file. I wasn't
aware of that but I believe it. I knew scanmodem.gz. was a zipped file,
but I did not know it had to be uzipped before chmod, whatever it's
function, could act upon it. Thanks I will definitely try
As I said in another post, mcopy finally worked AFTER I deleted a
directory named winDmodem, Why I don't know. I would expect it to ignore
the presence of other directories. It should have worked as it finally
did.
On 21 Jan 2005 at 10:09, Mikkel L. Ellertson wrote:
> [EMAIL PROTECTED] w
When running properly I believe it is supposed to read and print out
what chip set you have in a winmodem. Very helpful in trying to get linux
to see the modem.
On 21 Jan 2005 at 7:46, Eric Huff wrote:
> > > You may have to run "su" before running ./scanmodem - I don't
> > > remember if it
OH! Then chmod involves an already decompressed file. I wasn't
aware of that but I believe it. I knew scanmodem.gz. was a zipped file,
but I did not know it had to be uzipped before chmod, whatever it's
function, could act upon it. Thanks I will definitely try that.
On 21 Jan 2005 at
[EMAIL PROTECTED] wrote:
HAD a problem with the following sequence of commands. mkdir winmodem
cd winmodem
> mcopy a:scandisk.gz.***the file didn't existyes it did
You missed one step.
gunzip scanmodem.gz
> chmod +x scanmodem
> ./scanmodem Looking at the note above you
can see the file c
[EMAIL PROTECTED] wrote:
Nope, that didn't work either. All variations, including those on
the same hard drive, fail to get past mcopy. Hmmm, could it be since
I ran mcopy from a run box that the file is there but the message
only says it can/t read the file. I suppose it's worth a try when I
> > You may have to run "su" before running ./scanmodem - I don't
> > remember if it will run as a normal user.
> > All the instructions are for running in the command line
> > interface, and not from X, so you nead a terminal window, or you
> > need to drop to the command line. Now, as to what the
Nope, that didn't work either. All variations, including those on the
same hard drive, fail to get past mcopy. Hmmm, could it be since I ran
mcopy from a run box that the file is there but the message only says it
can/t read the file. I suppose it's worth a try when I wake up again this
a
[EMAIL PROTECTED] wrote:
You present some interesting possibilities. It sounds just like
m$dos5.0 or such. Gunzip being similar to pkunzip and chmod might be
change mode. All this came from the linmodems site. I think I will try
their directions as you say on a cmd line one after the othe
You present some interesting possibilities. It sounds just like
m$dos5.0 or such. Gunzip being similar to pkunzip and chmod might be
change mode. All this came from the linmodems site. I think I will try
their directions as you say on a cmd line one after the other with returns
in betwee
[EMAIL PROTECTED] wrote:
The instructions say to
1: in windows download this file to a floppy
2: in linux type these commands
2a: mcopy scanmodem.gz. ;should be a:mcopy a:.gz. I assumed it meant in a
run box and it did not complain
2b: gunzip scanmodem.gz ;they never say where, run box or
On Thu, 20 Jan 2005 13:26:32 -0500
[EMAIL PROTECTED] disseminated the following:
>The instructions say to
> 1: in windows download this file to a floppy
> 2: in linux type these commands
> 2a: mcopy scanmodem.gz. ;should be a:mcopy a:.gz. I assumed it meant in
> a
>
27 matches
Mail list logo
