For example: what kind of problems?But do mention the surge up front; it could've caused any number of internal problems in the computer that prevent the external modem from working properly.
And, can they be fixed?
For example: what kind of problems?But do mention the surge up front; it could've caused any number of internal problems in the computer that prevent the external modem from working properly.
Ah! excellent idea. I have several vintage machines that can carry Puppy-520 which is the system on the machine in question. I'll set one up tomorrow and give the new modem a try.But let's not get ahead of ourselves.
How about testing that external modem with another computer?
Code: Select all
dmesg | grep ttyUSB
so even " inbuild " with a slot for the SIM card my driver claims USB associations .[17118.675469] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB0
[17118.676902] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB1
[17118.688989] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB2
4.x .pet packages have been discontinued in the main repository, http://distro.ibiblio.org.What are the drawbacks to using Puppy 4.3.1. with it's kernel?
I forgot to ask:How come Puppy-520 kernel worked fine with Pupdial until ....?
That shouldn't matter in the context of this problem.Does it matter that that he was receiving huge picture files from friends who don't understand that he is on dialup and what that means as far as transmission times?
At the time I was struggling with the *Inode* issue I did a pfix=RAM. The *inode* issue according to our local tech was probably caused by a power surge. He noted many power surge problems coming into his shop the week the machine went down. The wiring system is questionable where the machine is used. And, the machine had an inadequate surge protector. We've had lightening storms unusual for this area.Have you tried Lucid-520 modem setup with the puppy pfix=ram boot option, minus the save file?
If the lupusave file is corrupt, then you'll need to delete it and make a new one.I can do a pfix=RAM on the machine without the lupusave present, but...if the lupusave file is corrupt then when I put it back
Honestly, I don't know.Also, can I somehow replace ttySL0 with ttyACMO in some control file somewhere?
I tried replacing it in etc/Wvdail.conf I *saved* etc/Wvdial.conf but that didn't appear to make any difference to Pupdial.
If the lupusave file is corrupt, then you'll need to delete it and make a new one.
I have reported this here : http://murga-linux.com/puppy/viewtopic.php?p=632972&search_id=505523010#632972I tried replacing it in etc/Wvdail.conf I *saved* etc/Wvdial.conf but that didn't appear to make any difference to Pupdial.
Pupdial owerwrites its /etc/wvdial.conf configuration file everytime, so
the suggestions written into it, to comment out lines
If the testing is too much hassle, just stick with 4.3.1.
After all, you know it works.
OK folks, I did set up 431 as a frugal install and upgraded SeaMonkey.That's exactly what I'm going to do.
I'll do a frugal install and add Shinobar's Seamonkey update .sfs.
When running from save file, can you get things working again by reprobing for modem in Menu / Network / Pupdial modem dialup?On the first try at Pupdial on the new setup, Pupdial connected with no issues.
But, then on the subsequence reboots and power ups, Pupdial failed with same error, modem not found on the tty port - "invalid argument".
When running from save file, can you get things working again by reprobing for modem in Menu / Network / Pupdial modem dialup?
Code: Select all
pgprs-shell