How do I mount a zipdrive at the parallel port?
How do I mount a zipdrive at the parallel port?
is there a way to mount a zipdrive at the parport (printerport) in puppy?
searched all the forums, but didn't find a solution...
searched all the forums, but didn't find a solution...
Re: zipdrive parport
In short, yes. First, we would need to know (I think) whether the drive is parallel port, USB, or SCSI (or is it IDE for internal drives?)mclien wrote:is there a way to mount a zipdrive at the parport (printerport) in puppy?
searched all the forums, but didn't find a solution...
If the drive is a parallel port drive, as mine is, you would go to a command line and type the following:
Code: Select all
insmod imm
Code: Select all
insmod ppa
Next, put a disk in the Zip drive. Then, go to the Start menu, click on Utilities (I think - I'm writing from memory, as I'm at work), and select the Mount Drives utility. The Zip drive should appear as one of the drives which can be mounted. Click on the button marked Zip and, in a few seconds, a ROX window should appear listing the files on the Zip disk.
If it works, that's all you need to do. Run the utility again to unmount the drive before removing the disk. Every time you want to use a Zip disk, simply put a disk in the drive, then run the mount drives utility. No editing of fstab required.
If that doesn't work, you can try running the following to ensure the necessary module is present:
Code: Select all
modprobe imm
Code: Select all
modprobe ppa
Walt
Now that you point it out to me, the answer seems painfully obvious.
Now that you point it out to me, the answer seems painfully obvious.
One thing I didn't mention is that those instructions assume you are saving the configuration on the hard drive (i.e., in a pup001 file). Otherwise, you'll have to run modprobe or insmod imm (or ppa as needed) each time you want to use your Zip drive.
Walt
Now that you point it out to me, the answer seems painfully obvious.
Now that you point it out to me, the answer seems painfully obvious.
ok this is a parallel port drive.
I'm useing puppy 1.0.4 as hdd installation on an rather old maschine
but..
I get errors in any case (modprobe and insmod):
and here what comes from /var/log/messages:(while modprobe)
and here what comes from /var/log/messages:
(inserting the zip disk ignoring the message)
any ideas?
Thanks
I'm useing puppy 1.0.4 as hdd installation on an rather old maschine
but..
I get errors in any case (modprobe and insmod):
Code: Select all
# modprobe imm
Note: /etc/modules.conf is more recent than /lib/modules/2.4.27/modules.dep
/lib/modules/2.4.27/scsi/imm.o.gz: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.27/scsi/imm.o.gz: insmod /lib/modules/2.4.27/scsi/imm.o.gz failed
/lib/modules/2.4.27/scsi/imm.o.gz: insmod imm failed
# modprobe ppa
Note: /etc/modules.conf is more recent than /lib/modules/2.4.27/modules.dep
modprobe: Can't locate module ppa
and here what comes from /var/log/messages:(while modprobe)
Code: Select all
Aug 24 14:03:30 (none) syslog.warn klogd: imm: Version 2.05 (for Linux 2.4.0)
(inserting the zip disk ignoring the message)
Code: Select all
Aug 24 14:04:11 (none) syslog.notice klogd: sdb: Unit Not Ready, sense:
Aug 24 14:04:11 (none) syslog.warn klogd: Current 00:00: sense key Not Ready
Aug 24 14:04:11 (none) syslog.warn klogd: Additional sense indicates Medium not present
Aug 24 14:04:11 (none) syslog.warn klogd: sdb : READ CAPACITY failed.
Aug 24 14:04:11 (none) syslog.warn klogd: sdb : status = 1, message = 00, host = 0, driver = 08
Aug 24 14:04:11 (none) syslog.warn klogd: Current sd00:00: sense key Not Ready
Aug 24 14:04:11 (none) syslog.warn klogd: Additional sense indicates Medium not present
Aug 24 14:04:11 (none) syslog.warn klogd: sdb : block size assumed to be 512 bytes, disk size 1GB.
Aug 24 14:04:11 (none) syslog.warn klogd: sdb: Write Protect is off
Aug 24 14:04:11 (none) syslog.info klogd: sdb: I/O error: dev 08:10, sector 0
Aug 24 14:04:11 (none) syslog.warn klogd: I/O error: dev 08:10, sector 0
Aug 24 14:04:11 (none) syslog.warn klogd: unable to read partition table
Aug 24 14:04:11 (none) syslog.info klogd: Device not ready. Make sure there is a disc in the drive.
Aug 24 14:04:11 (none) syslog.warn klogd: I/O error: dev 08:10, sector 0
Aug 24 14:04:12 (none) syslog.warn klogd: I/O error: dev 08:10, sector 0
Aug 24 14:04:13 (none) syslog.warn klogd: I/O error: dev 08:10, sector 0
Aug 24 14:04:14 (none) syslog.warn klogd: I/O error: dev 08:10, sector 0
Aug 24 14:04:15 (none) syslog.warn klogd: I/O error: dev 08:10, sector 0
Aug 24 14:04:16 (none) syslog.warn klogd: I/O error: dev 08:10, sector 0
Thanks
I didn't have to pass any parameters other than running insmod imm to get my Zip drive running in Puppy 1.0.4.
You might try running modprobe parport. I don't remember having trouble with parport in Puppy, but I know it does happen from time to time. (I did have trouble with it initially in Xandros.)
You might also try running the insmod imm command with a disk in the Zip drive (if you haven't tried that already).
Otherwise, someone with Puppy actually installed on the hard drive (as opposed to simply having the pup001 file will have to speak to whether anything changes in terms of paths or what not which could affect this.
I don't remember having to do this, but you might also try downloading and installing the modules pupget.
You might try running modprobe parport. I don't remember having trouble with parport in Puppy, but I know it does happen from time to time. (I did have trouble with it initially in Xandros.)
You might also try running the insmod imm command with a disk in the Zip drive (if you haven't tried that already).
Otherwise, someone with Puppy actually installed on the hard drive (as opposed to simply having the pup001 file will have to speak to whether anything changes in terms of paths or what not which could affect this.
I don't remember having to do this, but you might also try downloading and installing the modules pupget.
Walt
Now that you point it out to me, the answer seems painfully obvious.
Now that you point it out to me, the answer seems painfully obvious.
You may want to check the BIOS to see what the setting is for the parallel port (Bi-Directional, ECC/EPP [?], etc.) You do not want the bi-directional setting as I recall.
You might try cycling through the different BIOS choices for the parallel port, then running insmod parport and insmod imm to see whether that clears the problem up.
You might try cycling through the different BIOS choices for the parallel port, then running insmod parport and insmod imm to see whether that clears the problem up.
Walt
Now that you point it out to me, the answer seems painfully obvious.
Now that you point it out to me, the answer seems painfully obvious.
Walt should be right on the money. I have one of these in my closet.
I'll have to pull it out and see how it works. My ide zip drive is seen right off.
It used to be the case that you needed to have a zip disk in the drive on boot for the modules to get properly loaded.
I'll let you know what I find out.
These zip drives have some minor quirks. If the zip disk is formatted as a fat (Windows) disk, then you will see it as sda4.
If it is formatted as a Linux disk, sda1.
Of course, it has been a while since I did this.
For kicks, see my old article here.
Now you got me curious.
P.S. I just installed my parallel port 250 mb zip drive.
parport is loaded on boot. Make sure that there is a valid zip disk in the drive at boot. Do;
modprobe imm
Your drive should be seen by Puppy's drive mount utility as a zip drive.
I'll have to pull it out and see how it works. My ide zip drive is seen right off.
It used to be the case that you needed to have a zip disk in the drive on boot for the modules to get properly loaded.
I'll let you know what I find out.
These zip drives have some minor quirks. If the zip disk is formatted as a fat (Windows) disk, then you will see it as sda4.
If it is formatted as a Linux disk, sda1.
Of course, it has been a while since I did this.
For kicks, see my old article here.
Now you got me curious.
P.S. I just installed my parallel port 250 mb zip drive.
parport is loaded on boot. Make sure that there is a valid zip disk in the drive at boot. Do;
modprobe imm
Your drive should be seen by Puppy's drive mount utility as a zip drive.
I love it when a plan comes together
--Hannibal Smith
--Hannibal Smith
There are two modules that can be used, depending on the age of the zip drive.
The imm module is for the newer zip drives, all the 250 mb drives and some of the newer 100 mb zip drives.
If your drive is one of the older ones, then the ppa module will be needed. This one is not in Puppy, but can be added from the complete modules file that Barry has available on the download site.
If having the zip disk in the drive on boot and loading the imm module does not work, then let us know. I think I can walk you through extracting the ppa module to the right place and modprobing it. Maybe attach it to this thread so that you only need to place it in the right lib directory and modprobe it.
The imm module is for the newer zip drives, all the 250 mb drives and some of the newer 100 mb zip drives.
If your drive is one of the older ones, then the ppa module will be needed. This one is not in Puppy, but can be added from the complete modules file that Barry has available on the download site.
If having the zip disk in the drive on boot and loading the imm module does not work, then let us know. I think I can walk you through extracting the ppa module to the right place and modprobing it. Maybe attach it to this thread so that you only need to place it in the right lib directory and modprobe it.
I love it when a plan comes together
--Hannibal Smith
--Hannibal Smith
OK, of course it's an OLD 100MB drive and the imm module doesn't work.
So any help would be great.
Woouldn't it be a good idea to have the ppa module in puppy by default, because puppy is the best distro to make an old computer work?
Just to understand me right: I LOVE to show others that you don't neet to buy a new comp, if you just use the right Linux!!
So any help would be great.
Woouldn't it be a good idea to have the ppa module in puppy by default, because puppy is the best distro to make an old computer work?
Just to understand me right: I LOVE to show others that you don't neet to buy a new comp, if you just use the right Linux!!
Well, most of the Zip drives around are not that old anymore. Anyway let's see if this posts.
Place the module file in the /lib/modules/2.4.29/scsi directory.
In rxvt, type in;
depmod -a {hit the enter key}
Then try modprobe ppa
See if dmesg shows the parallel port zip drive and what the designation of the zip drive is, say sda4 if the disk is formatted as fat32.
Place the module file in the /lib/modules/2.4.29/scsi directory.
In rxvt, type in;
depmod -a {hit the enter key}
Then try modprobe ppa
See if dmesg shows the parallel port zip drive and what the designation of the zip drive is, say sda4 if the disk is formatted as fat32.
- Attachments
-
- ppa.o.gz
- (6.68 KiB) Downloaded 252 times
I love it when a plan comes together
--Hannibal Smith
--Hannibal Smith
I finally found time to try this and it works...
for a while, after changing the zip disk the computer chrashes and reboots allthe time.
But perhaps I have a hardware problem there (very old machine). so don't worry i think everything is fine exept my hardware
I'll try it out on a good machine some time and post the result.
Thanks for everything
for a while, after changing the zip disk the computer chrashes and reboots allthe time.
But perhaps I have a hardware problem there (very old machine). so don't worry i think everything is fine exept my hardware
I'll try it out on a good machine some time and post the result.
Thanks for everything