Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: Niding on October 27, 2014, 12:09:51 AM
-
http://www.vesalia.de/e_amigaslimcddrive%5B8287%5D.htm
When I Scan using "FindDevice" im told I have 1 Matzhita CR Rom CR-175 Revision 5NCC
Its powered, spools up during the scan but the OS doesnt seem to find it (nor when using Dopus)
I do have the preinstalled IDEFIX that came with AmigaKit CF HD.
Any ideas as to how I can mount the CD rom?
A1200/30
Rom 3.1
WB 3.0 (39.29)
Kickstart 40.68
-
http://www.vesalia.de/e_amigaslimcddrive%5B8287%5D.htm
When I Scan using "FindDevice" im told I have 1 Mat%&$#?@!%&$#?@!%&$#?@!%&$#?@!a CR Rom CR-175 Revision 5NCC
Its powered, spools up during the scan but the OS doesnt seem to find it (nor when using Dopus)
I do have the preinstalled IDEFIX that came with AmigaKit CF HD.
Any ideas as to how I can mount the CD rom?
A1200/30
Rom 3.1
WB 3.0 (39.29)
Kickstart 40.68
What have you got set as, Master or Slave?
-
How is it connected?
-
After installing IDEFix97, and the setup program completing, is the mount file in the DEVS: DosDrivers directory, or the Storage:DosDrivers? The typical mount command in the Startup-sequence will only mount the ones in DEVS.
-
http://www.vesalia.de/e_amigaslimcddrive%5B8287%5D.htm
When I Scan using "FindDevice" im told I have 1 Mat%&$#?@!%&$#?@!%&$#?@!%&$#?@!a CR Rom CR-175 Revision 5NCC
Its powered, spools up during the scan but the OS doesnt seem to find it (nor when using Dopus)
I do have the preinstalled IDEFIX that came with AmigaKit CF HD.
Any ideas as to how I can mount the CD rom?
A1200/30
Rom 3.1
WB 3.0 (39.29)
Kickstart 40.68
Have you installed a cd filesystem to use the drive such as ASIMCDFS etc?
-
I dont think he has anything installed.
We dont preinstall IDEFIX, the setup files are on HDD: for you to decide if you want to install it or not.
Once he installs IDEFIX, then it will work fine.
-
When FindDevice brings up weird names like that it's usually due to a failing CD drive. Replace the drive and FindDevice should pick up the right name and you can continue the installation.
-
When FindDevice brings up weird names like that it's usually due to a failing CD drive. Replace the drive and FindDevice should pick up the right name and you can continue the installation.
Thats the problem it cant continue install, if he hasnt even run installer.
-
Thats the problem it cant continue install, if he hasnt even run installer.
FindDevice is launched during installation. The problem is the hardware, not the software.
-
One can run the FindDevice program alone by clicking its icon; I too have the suspicion that the poster has not run through IDEFix97 program, hence my questions. Screwed up firmware results can be caused by a loose cable, too.
-
Hi All. I bought the same drive from Vesalia I had same problem, after i contacted them found out it was seup as a slave. i never could get it to work! I gave up!
bluewater41
-
I doubt it wouldn't work because it was set as a SLAVE, (did you get out the leather bindings, chains and whips?)
-
Hi All. I bought the same drive from Vesalia I had same problem, after i contacted them found out it was seup as a slave. i never could get it to work! I gave up!
I'm not familiar with this particular drive but nearly all IDE devices can be changed from Master to Slave configuration (and vice versa) with a jumper. Typically on an A1200 (unless you've added some additional type of controller) you only have one channel. Your hard drive would be Master, and CD drive would be Slave. Problem is there's so many different ways of attaching a drive to an A1200, different drivers & software packages, and even what version of the OS you're using (3.1 vs 3.9, for example), can make a big difference.
It pretty much comes down to trial and error, although I will say that in my experience with Amiga CD drives, the easiest way to configure them was in OS 3.9. I'd just boot off the 3.9 recovery floppy and it would detect the drive automatically and install the rest of the software off the CD. I had no problems with long filenames or extensions like I did under 3.1, with various other software packages. Your mileage may vary, good luck, try posting a picture of the jumper settings on the back of the drive might be my last bit of advice right now! :)
-
Hah, I posted the original post without previewing it.
The wordfilter scrambled it.
Going thru the suggestions in this thread.
Ah now it comes back to me.
The install floppy provided by Vesalia; installation seemed to work out until putting in registration provided on front of floppy. It didnt progress past that.
Now im trying to install from the CF drive provided by Amigakit. The script "Installsoftware (0%). Working on installation Starting AddIDEfixstartup.
Just stays on 0%.
The drive doesnt have a "slave" jumper like the old harddrives got.
-
Quick question, are you installing a CD or a CF drive?
-
The CF drive worked from the get go. No problems at all :)
The cable got additional slot for IDE drive, so I got a CD Rom drive to use.
The CD rom drive doesnt have jumpers, so if thats the issue, then im screwed :)
I have ordered Jens's USB hardware, and already got the CF transfer kit from Amigakit, so getting stuff from the Inet aint much of an issue. Installing stuff from CD rom on the other hand...
-
*Then try running the IDEFix software (it has a registration code on Cloanto's Amiga Forever disc, too) and see what happens. All my CD and DVD drives are Slaves, with the hard drives as their dominatrix.
-
In the startup sequence, the lines;
IF EXISTS SYS:C/IDEFIX
C:IDEFIX
ENDIF
This freezes the loading of workbench. Once I ; them out, workbench loads normally.
-
Yeah, don't know why that is there, but remove it as stated and reinstall IDEFix'97; it will replace the faulty logic behind crap like that and likely get you running.
-
Some CF's and CD ROM drives dont mix and when IDEFIX starts its kills system.
You dont need IDEFIX to use CD ROM. If its on same channel as long as you have CD0: and filesystem, it will work fine.
If its on the second channel then use atapi.device to activate second channel along with CD0: and filesystem.