Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: RedWarrior on August 28, 2016, 05:14:06 AM
-
Hey guys-
I searched compactflash.device on this site, as I imagine this is a fairly common subject, but the search engine returned zero results... so I apologise if this is a regular question!
"Amiga... where nothing is simple." is my new proposed tagline for these machines. :D
This "I'm almost finished" feeling has been dragging on for weeks- I'm now trying to get my CF PCMCIA reader to read... on my a600 this was a reasonably simple process, but my 1200 isn't cooperating so far.
I have the Fat95 file in the L: folder, and the CF0 file in the Devs: folder... I had hoped that simply clicking CF0 in devs would make the PCMCIA card appear on Workbench... but no.
I tried copying my old Mountlist file from my a600 to the 1200, but that hasn't helped. I get the feeling I'm going to have to wrestle with block sizes, baudrates, binddrivers and a bunch of weird things I don't understand...
Do I need to do something special to the mountlist to make it work on this system? Does Fat/Fat32 make a difference? (fat16 no longer an option in Windows7)...
My brain hurts.
Input greatly appreciated. thanks guys =)
I'm guessing the error message after "mount cf0:" is significant?
-
The Compactflash.device file can by found in this packed file:
http://aminet.net/disk/misc/cfd.lha
You have to copy the compactflash.device in the DEVS: directory.
-
I already have that...
Nothing is showing up on Workbench... not even NDOS:
Please take a look at the images attached above?
-
Does your Amiga 1200 has an Accelerator card in it?
Then you have to change the mask transfer value to 00x1fe00 with HDToolbox.
If the value is higher then, the files wil be corrupted.
-
Does your Amiga 1200 has an Accelerator card in it?
Then you have to change the mask transfer value to 00x1fe00 with HDToolbox.
If the value is higher then, the files wil be corrupted.
No accelerator, this is a stock standard A1200. HDToolbox isn't showing anything other than the internal (CF) drive. Nothing detected related to the PCMCIA slot...
Shouldn't I have the basics here to at least get an icon showing up in Workbench? I tried running the Install95 command from a cli window... no idea if it did anything or if I did it correctly...
Anything obvious I'm missing? :/
-
- device names are case sensitive. It should be compactflash.device, not CompactFlash.device.
- you can use either devs:mountlist or devs:dosdrivers, you should not mix both.
If you use devs:mountlist (deprecated), the entry should look like this:
CF0:
FileSystem = l:fat95
Device = compactflash.device
Unit = 0
Flags = 0
LowCyl = 0
HighCyl = 0
Surfaces = 1
BlocksPerTrack = 1
BlockSize = 512
Buffers = 20
BufMemType = 1
BootPri = 0
Stacksize = 4096
Priority = 5
GlobVec = -1
DosType = 0x46415401
#
Mountlist entries begin with the drive name and end with a #.
If you use devs:dosdrivers (recommended), you should just copy the CF0 file from cfd.lha to devs:dosdrivers. The contents is like this:
/* compactflash.device $VER: 1.21 (19.10.2002) */
/* fat95 file system by Torsten Jager */
FileSystem = l:fat95
Device = compactflash.device
Unit = 0
Flags = 0
LowCyl = 0
HighCyl = 0
Surfaces = 1
BlocksPerTrack = 1
BlockSize = 512
Buffers = 20
BufMemType = 1
BootPri = 0
Stacksize = 4096
Priority = 5
GlobVec = -1
DosType = 0x46415401
Dosdrivers files must not contain the drive name and must not contain #.
- with the mount command, you mount the drive, not the driver. Therefore it should be mount cf0: or mount devs:dosdrivers/cf0, not mount compactflash.device. A double click on devs:dosdrivers/cf0 or a reboot should be sufficient.
-
Brilliant - thank you!!
I did just try the DosDrivers instructions there... not sure if I accidentally missed something, but now I'm getting a boot to workbench and a "Wait" mouse cursor that never goes away....
I'm not sure if this counts as progress... but at least something different happened! =)
-
Your second screenshot above shows "compactflash.device: already mounted". Where is that compactflash.device and what does it contain?
The original compactflash.device from the cfd.lha archve is a program and belongs to devs:. It can neither be edited nor mounted. So if you somehow used an editor to create a text file called compactflash.device, delete that and copy the original driver from cfd.lha to Devs:.
-
The compactflash.device has a line of text:
$VER: compactflash.device 1.25 (17.07.2004)
and then a bunch of garbled (compiled?) code after it. The file size is 7656 bytes.
-
Seems like you have an old version. Try the latest one: http://aminet.net/package/disk/misc/cfd
To ensure that you have all the right files in the right places, open a dos window and enter this commmand:
list sys: all files lformat="%8l %d %t %p%n" p="(fat#?|compact#?|cf0#?)"
The result should look like this:
3> list sys: all files lformat="%8l %d %t %p%n" p="(fat#?|compact#?|cf0#?)"
8280 31-Dec-80 23:00:00 sys:Devs/compactflash.device
2431 19-Apr-02 15:48:48 sys:Storage/DOSDrivers/CF0.info
420 19-Oct-02 21:43:40 sys:Storage/DOSDrivers/CF0
26868 01-Mar-80 04:19:38 sys:L/fat95
3>
-
Seems like you have an old version. Try the latest one: http://aminet.net/package/disk/misc/cfd
To ensure that you have all the right files in the right places, open a dos window and enter this commmand:
list sys: all files lformat="%8l %d %t %p%n" p="(fat#?|compact#?|cf0#?)"
The result should look like this:
3> list sys: all files lformat="%8l %d %t %p%n" p="(fat#?|compact#?|cf0#?)"
8280 31-Dec-80 23:00:00 sys:Devs/compactflash.device
2431 19-Apr-02 15:48:48 sys:Storage/DOSDrivers/CF0.info
420 19-Oct-02 21:43:40 sys:Storage/DOSDrivers/CF0
26868 01-Mar-80 04:19:38 sys:L/fat95
3>
I typed that in as best as I could... the drive light flickers for a while, but nothing comes back.
To update the CF0 file means i have to open my machine again and use Winuae again etc...? :(
no other possibilities with existing files?
-
I mis-copied your text there- I thought it was an "l", but it was a "1"...
I have a lot of files with similar names. what do you make of all this? =) (image attached)
-
I have a DosDrivers folder in Devs, as well as Storage... might that make a difference I wonder. Will try and copy your setup... ;)
CF0 - drag the icon (from the archive that Thomas linked to) to Storage/DOSDrivers.
fat95 goes in L:
compactflash.device goes in Devs
Things in Storage don't activate or mount - giving you the freedom to click on them when required, or to move them for permenant activation by moving them to their corresponding drawer in Devs. It's all in the Workbench User Guide.
http://aminet.net/package/util/boot/CardPatch (http://aminet.net/package/util/boot/CardPatch)
http://aminet.net/package/util/boot/CardReset (http://aminet.net/package/util/boot/CardReset)
CardReset is required on A1200's unless you have a hardware fix. Otherwise it won't work unless you coldboot with card removed and then insert card (iirc), but putting those in your Startup-sequence will solve that problem (or run CardReset manually if you like once in Workbench). CardPatch - this may be the reason for your busy pointer. Read the docs on cfd, cardpatch and card reset, and also fat95.
Amiga's are actually very elegant in how they work, the simplest most elegant OS in existance. It's so easy to do things that most don't bother writing installation scripts for their programs etc - once you learn the basics you'll realise this yourself.
-
CF0 - drag the icon (from the archive that Thomas linked to) to Storage/DOSDrivers.
fat95 goes in L:
compactflash.device goes in Devs
Things in Storage don't activate or mount - giving you the freedom to click on them when required, or to move them for permenant activation by moving them to their corresponding drawer in Devs. It's all in the Workbench User Guide.
http://aminet.net/package/util/boot/CardPatch (http://aminet.net/package/util/boot/CardPatch)
http://aminet.net/package/util/boot/CardReset (http://aminet.net/package/util/boot/CardReset)
CardReset is required on A1200's unless you have a hardware fix. Otherwise it won't work unless you coldboot with card removed and then insert card (iirc), but putting those in your Startup-sequence will solve that problem (or run CardReset manually if you like once in Workbench). CardPatch - this may be the reason for your busy pointer. Read the docs on cfd, cardpatch and card reset, and also fat95.
Amiga's are actually very elegant in how they work, the simplest most elegant OS in existance. It's so easy to do things that most don't bother writing installation scripts for their programs etc - once you learn the basics you'll realise this yourself.
I'm sure I'll love this machine again once it's working... but I'm not a coder by any means, so this is really pushing my limits of technical ability (and patience!) ;-)
Should I delete the dosdrivers/keymaps/datatypes/moitors/printers folders from Devs? I seem to have duplicates in Storage as well as Devs...
-
Delete storage/dosdrivers/compactflash.device.
I mis-copied your text there- I thought it was an "l", but it was a "1"...
It should be an l (lower case L). %8l will print the file size with 8 digits. %81 will print %81, completely pointless.
-
I'm sure I'll love this machine again once it's working... but I'm not a coder by any means, so this is really pushing my limits of technical ability (and patience!) ;-)
Should I delete the dosdrivers/keymaps/datatypes/moitors/printers folders from Devs? I seem to have duplicates in Storage as well as Devs...
No, don't delete those. Storage is for storing those things, and you drag what you need into Devs. Just don't delete anything from Devs. Stuff not needed in Devs should be kept in tgeur corresponding Storage drawer. This is Commodore's way. Doesn't matter if you have duplicates in Storage, Storage isn't used by the operating system.
-
"Doesn't matter if you have duplicates in Storage, Storage isn't used by the operating system. "
I have a strange knack of taking the worst interpretation of things sometimes... I read that and concluded that I ought to have whatever was in the storage/dosdrivers/ folder in the devs/dosdrivers folder... I copied everything in there to devs/dosdrivers....
and rebooted to a dead CLI limbo with nothing mounted and nothing normal at all...
I did manage to launch my file manager and delete the files I copied into devs/dosdrivers/... but the damage is done! How do I get my system back?
I even unscrewed by amiga and copied all those recommended latest files for CFD etc... (didn't make a difference, still no CF0 drive coming up...) :(
What am I doing wrong? (besides everything?)
-
Looks like I did something to make the RAD: drive enabled all the time. I tried a boot with both mouse buttons, and now RAD: is in there (wasn't before). If I cold boot, the bloody thing comes back...
How can I turn off the RAD drive? It's also chewing about half of my RAM now...
Man I'm bad at this...
Thanks for your input/pity/charity =)
-
Looks like I did something to make the RAD: drive enabled all the time. I tried a boot with both mouse buttons, and now RAD: is in there (wasn't before). If I cold boot, the bloody thing comes back...
How can I turn off the RAD drive? It's also chewing about half of my RAM now...
Man I'm bad at this...
Thanks for your input/pity/charity =)
Turn off RAD by dragging it out of Devs/DOSDrivers and into Storage/DOSDrivers. :laugh1:
You may have more than one RAD - move any that you see. Then turn your Amiga off at the powerbrick, wait 10 seconds, then power back on. I won't mention the remrad command which if run will save that reboot.
-
I have a strange knack of taking the worst interpretation of things sometimes... I read that and concluded that I ought to have whatever was in the storage/dosdrivers/ folder in the devs/dosdrivers folder... I copied everything in there to devs/dosdrivers....
and rebooted to a dead CLI limbo with nothing mounted and nothing normal at all...
I did manage to launch my file manager and delete the files I copied into devs/dosdrivers/... but the damage is done! How do I get my system back?
I even unscrewed by amiga and copied all those recommended latest files for CFD etc... (didn't make a difference, still no CF0 drive coming up...) :(
What am I doing wrong? (besides everything?)
Do you mind if I call you Frank Spencer? :lol:
Have a look from Page 50 of the Workbench 3 User Guide, tells you about Devs and Storage:
http://www.google.co.uk/url?q=http://www.bombjack.org/commodore/amiga/amiga-commodore/Workbench_3.0_Users_Guide.pdf&sa=U&ved=0ahUKEwiHzK_ymebOAhUGM8AKHca8AusQFggXMAI&usg=AFQjCNFD65bkyYufKk9FpHjZ7unyftYNLg (http://www.google.co.uk/url?q=http://www.bombjack.org/commodore/amiga/amiga-commodore/Workbench_3.0_Users_Guide.pdf&sa=U&ved=0ahUKEwiHzK_ymebOAhUGM8AKHca8AusQFggXMAI&usg=AFQjCNFD65bkyYufKk9FpHjZ7unyftYNLg)
Is your Amiga booting again yet? What version of Workbench are you running? Did you install it yourself (Workbench)?
-
I think it might be Workbench 3.0
Installed? No... copied from a system that was running the display screens in a train station... I saved a few of them from being thrown away.
-
I think it might be Workbench 3.0
Installed? No... copied from a system that was running the display screens in a train station... I saved a few of them from being thrown away.
Very commendable indeed! That's really interesting... Where abouts is this train station? What's it called?
-
ok. system back (phew!)
but still no CF0... I've tried a few different CF cards... I can't even get CF0:NDOS to show up...
Would anyone feel like possibly talking me through this? ICQ? Skype? Doing my head in...
-
Plot twist: Running the PrepCard tool shows that there is a CF card in the PCMCIA slot... Some info appears when I insert the card & goes blank when I remove it.
Of course nothing actually works when I try to initialise it... ;)
-
Plot twist: Running the PrepCard tool shows that there is a CF card in the PCMCIA slot... Some info appears when I insert the card & goes blank when I remove it.
Of course nothing actually works when I try to initialise it... ;)
This CF card you're using, do you have data on it? Is it formatted? It needs to be FAT32 formatted. You can do this on your Amiga or elsewhere. Refer back to previous posts and check you have those files in the correct places.
compactflash.device (Devs)
fat95 (L)
CF0 (move to Devs/DOSDrivers to have it automatically mount on every boot)
Don't forget the CardPatch and CardReset too.
-
CardPatch and CardReset... I have tried running those as commands... nothing happens... is something meant to happen? The card is/was in my Amiga600 and I tried to format it under winuae with pfs3 (as per your earlier recommendation, as I have done for the internal CF)... though it returned with "OUT OF MEMORY" and rebooted when I tried to perform pfsformat.
I tried adding more memory via winuae settings, but made no difference. I think it is lying about being out of memory. Oh- it might be the DosType... I didn't know what to put as the dostype. It's a 4gig CF card...
Though surely it would at least show up as CF0:NDOS and let me fix it on the Amiga?? :/
-
Does the CF0: card reading thing care if it's an Amiga formatted Card (PFS3) or Fat32? Will it read both? or only Fat95?
-
FAT95 will only read FAT-formatted cards.
Check with Info and Assign commands if CF0 is actually mounted. Assign should list CF0 under mounted devices and Info should list CF0 with a status like "no disk in drive" or "not a dos disk".
-
The card is/was in my Amiga600 and I tried to format it under winuae with pfs3 (as per your earlier recommendation, as I have done for the internal CF)...
You're not supposed to format it with pfs3. Just format it on your PC with FAT95.
-
Finally managed to get pfsformat to work on this CF card I was planning to use as a transfer card.... (borrowed from my A600)
Luckily I didn't just wait an hour for nothing...
:D :D :D :D :D :D I want to cry.
-
Finally managed to get pfsformat to work on this CF card I was planning to use as a transfer card.... (borrowed from my A600)
Luckily I didn't just wait an hour for nothing...
:D :D :D :D :D :D I want to cry.
I'm afraid you did. A quick format would have sufficed. I must say, I'm more confused than you now I think. LOL.
Traditionally, compactflash.device / CF0 is used to transfer files between PC's and your Amiga (or Unix box or Mac or whatever). Fat filesystem is used because it's the default filesystem used on flash devices, because all computers can understand the fat file system so therefore it's used widely to share files, including cameras, audio recorders, mp3 players etc. There are more up to date ones now which are used for higher capacity flash media and hard drives but I'm just trying to give you a bit of background.
I thought you were trying to use a CF card reader with your CF, but now it seems you're attaching it to the internal IDE?
-
Does the CF0: card reading thing care if it's an Amiga formatted Card (PFS3) or Fat32? Will it read both? or only Fat95?
CF0, the actual file I mean, is a mountlist which is mounted by the AmigaDOS command 'Mount'. You can view its contents with a text viewer (More or Multiview for example) and you can edit it with an editor such as Ed. CF0 is tailored to using fat95, you'd have to edit it to use a different filesystem, but you should really stick with fat95, as then you can put the CF card into your PC or laptop and easily transfer files to and from your Amiga, where WinUAE isn't required.
-
Queensland Rail. Groovy!!
-
Yeah I think I got confused and wanted to try everything I could think of... as you can see the format failed anyway, so I let Windows format the card as FAT32... and the Amiga still didn't read it anyway...
I didn't use diskpart this time... is that important? I can't remember- it's all a blur...
-
CardPatch and CardReset... I have tried running those as commands... nothing happens... is something meant to happen? The card is/was in my Amiga600 and I tried to format it under winuae with pfs3 (as per your earlier recommendation, as I have done for the internal CF)... though it returned with "OUT OF MEMORY" and rebooted when I tried to perform pfsformat.
PFS hasn't been mentioned in this thread. For internal IDE use yes, by all means use PFS.
-
I tried ASSIGN - and this is what came back...
When I double click the CF0 in Devs/Dosdrivers - it tells me it's already mounted...
Maybe there are different kinds of "mounted"?
-
Trawling google, it's quite disturbing how many similar threads there are out there like this... they just trail off and there's no solution. I wonder what happened to those poor people? Am I next?
...what was that?!...
-
No, there's only one sort of mounted. Everything in Devs/DOSDrivers will get mounted during the boot sequence, just as the printers, datatypes, keymaps, monitors do etc. Which leads us perfectly down the path towards Storage. Storage is where you keep those unwanted keymaps, printer drivers, DOSDrivers (like RAD) and monitor drivers. You see, if they're in Storage you'd have to click on that RAD to mount it, or that printer, or monitor driver. I hope this helps!
So CF0 is mounted, that's good. Run CardReset, and if the card is fat formatted it should show up. If nothing shows up, run the Format program in System, and Quick Format CF0.
That noise... that was the sound of the disk motor bearings straining in your CF card from that Full Format you subjected it to. :)
-
Yeah I think I got confused and wanted to try everything I could think of...it's all a blur...
You've confused us all... :confused: :insane:
Have a cold brewski and go do something else! :drink:
-
I have always found it best to do things the following way with PCMCIA - CF card adapters:
1. Turn on the Amiga
2. When Workbench has loaded, mount CF0: (if it's not already done)
3. Insert CF card into adapter (if it's not already done)
4. Insert adapter into PCMCIA port
After a few seconds, the icon of the CF card should now appear on the WB screen.
-
You're right... it SHOULD appear... :D
Weird that on my (now dismantled) a600 I could pop any card in the PCMCIA port and it would at least show up on workbench... even as CF0:NDOS if it didn't like it.
On my 1200 nothing shows up... ever. (Though Cardprep does confirm that it can identify the card- so it can't be a hardware problem)
I'm using a hackjob OS - from the workbench311 hardfile that comes with WinUAE... would that have any bearing on the situation?
-
Please run this: http://thomas-rapp.homepage.t-online.de/downloads/hddreport.lha
and attach the report here. It should give some hints where the problem could be.
-
Please run this: http://thomas-rapp.homepage.t-online.de/downloads/hddreport.lha
and attach the report here. It should give some hints where the problem could be.
Ok- thank you! Lots of info in there! photos attached....
-
more pics
-
come on, you got the lha archive to your amiga, so you can move the txt file the opposite way and attach it here as a single file. I refuse to read text from blurry photos.
-
come on, you got the lha archive to your amiga, so you can move the txt file the opposite way and attach it here as a single file. I refuse to read text from blurry photos.
I also had to unscrew the case, being careful not to tear out the keyboard ribbon cable whilst holding the underside of the computer with my face and insert the CF card... This is kind of why I really want to get the CF card working. I'm sorry for the poor screen quality- it's the "easiest" setup I can manage at this point running composite RCA into my very old laptop. I'm trying to avoid opening and re-opening my 1200 as much as possible... I'm just tempting fate.
-
Ok I copied it... text file attached.
-
Does anyone use IRC anymore by any chance?
-
I also had to unscrew the case, being careful not to tear out the keyboard ribbon cable whilst holding the underside of the computer with my face and insert the CF card... This is kind of why I really want to get the CF card working. I'm sorry for the poor screen quality- it's the "easiest" setup I can manage at this point running composite RCA into my very old laptop. I'm trying to avoid opening and re-opening my 1200 as much as possible... I'm just tempting fate.
Opening the case for each file is a bad idea, that's true. Don't you still have this A600 where everything worked? You could have saved the txt file to a floppy disk, put it into the A600, copy it to CF card and then carry it to the PC. No need to open a case.
Or use a 720K PC-formatted floppy disk to transfer the file directly to the PC.
-
Ok I copied it... text file attached.
compactflash.device Unit 0 Version 1.32 NSD
TD_READ64 check failed with error -3 (command not supported by device)
HD_SCSICMD check failed with error 29 (no disk in the drive)
SCSI:
Vendor : Š„Š„Š„Š„
Product : Š„Š„Š„Š„Š„Š„Š„Š„
Revision : Š„Š„
Geometry:
SectorSize : 512
TotalSectors : 0
Cylinders : 0
CylSectors : 1257411600
Heads : 35460
TrackSectors : 35460
BufMemType : PUBLIC
DeviceType : Direct Access
Flags : REMOVABLE
Capacity : 0 KB
The report shows that the software is correctly installed and working. It's more a hardware problem now. It says there is no disk in the drive and the SCSI identify command returns garbage.
Check that the CF card sits properly in the adapter and the adapter properly in the Amiga and no pins are bent or pushed back.
-
Opening the case for each file is a bad idea, that's true. Don't you still have this A600 where everything worked? You could have saved the txt file to a floppy disk, put it into the A600, copy it to CF card and then carry it to the PC. No need to open a case.
Or use a 720K PC-formatted floppy disk to transfer the file directly to the PC.
Sadly no, I harvested the CF card from the a600 just as another option to test... (copied everything off though)
My 600 had gremlins of its own... certain keys on the keyboard have given up- so it's hard trying to run any commands whtn the colon : and P and U don't work... :D
I'll maybe start a thread "how to safely clean and maintain old floppy drives?" to deal with the current "disk-shredding" I'm experiencing... (floppies not an option at the moment)
So this has been a very slow and painful process so far... I'm still looking forward to maybe one day seeing what all the fuss was about AGA... (All 1200's are AGA, right?)
TExt file posted above... does it tell you anything useful?
thanks heaps for your help... this is rather gruelling =)
-
The report shows that the software is correctly installed and working. It's more a hardware problem now. It says there is no disk in the drive and the SCSI identify command returns garbage.
Check that the CF card sits properly in the adapter and the adapter properly in the Amiga and no pins are bent or pushed back.
Is there a way to look inside the actual card reader? (without breaking it?)
This machine still has all its shielding etc (still chrome shiny! - Made in France... my Made in Malaysia machine is rusted and busted) - I'm a bit reluctant to take the shielding off to look at the pins... The card adapter feels fine- smooth... like it's connecting... and the card is also snug...
-
Is there a way to look inside the actual card reader? (without breaking it?)
Not sure. A pocket lamp and a magnifying glass?
Does your "very old laptop" have a PCMCIA slot? You could test it there.
-
Oh I thought you meant the pins inside the Amiga PCMCIA reader? I have 2 CF to PCMCIA card adapters... I can test them on my pc... sure,...
Just tested- yep they both work fine.
-
Oh I thought you meant the pins inside the Amiga PCMCIA reader?
Sorry, I misunderstood your question. For me the PCMCIA connector inside the Amiga is not a "reader" but rather an expansion slot.
Yes, certainly the PCMCIA slot on the Amiga is also a candidate for bent or pushed pins.
Lamp and magnifier are still you best bet to look into it from the outside. Otherwise you have to open the case and remove the shielding.
-
Plot twist: Running the PrepCard tool shows that there is a CF card in the PCMCIA slot... Some info appears when I insert the card & goes blank when I remove it.
Does this still work? Can you take a screenshot of the info displayed?
BTW, doesn't your video software on the laptop allow to take a snapshot of what is displayed? This would be easier than to use a photo camera and would probably give a much better quality.
-
CardPatch and CardReset... I have tried running those as commands... nothing happens...
They shouldn't output anything. CardPatch applies some corrections to the system software and CardReset resets the PCMCIA port. They should be run in this order in startup-sequence, just after SetPatch.
-
I read this thread and am very confused!
Are you working on replacing an internal ide drive with a cf adaptor and cf card?
And are you also working at the same time on using a fat formatted cf card on the PCMCIA slot?
Why don't you just do one at a time?
Did you buy a "proven cd card"?
-
I think you said earlier RedWarrior that your A600 worked fine with a CF adapter and card - are you using the same CF card and CF adapter now as you did with the A600?
-
I read this thread and am very confused!
Me too, especially today lol
-
I think you said earlier RedWarrior that your A600 worked fine with a CF adapter and card - are you using the same CF card and CF adapter now as you did with the A600?
Yes. I have 2 adaptors and 2 cards... One of those CF cards was the guts of my A600, so it's out of action for now... I could put any old card into the a600 and it would at least give me an icon CFO:NDOS.
I'm confused about the comment from Thomas earlier suggesting it could be hardware or a bent pin on the a1200... Especially since Prepcard can identify the CF card... It's just workbench and the system that refuses to assign an icon and let me access the device.
I hope this misery and frustration is going to benefit someone else some day... =)
-
You still did NOT clarify...
Are you using a ide to cf adaptor with a proven cf card?
In this case, you use Hdtoolbox to format the cd card as a hard drive replacement!
And Are you using a PCMICA adaptor with a second cf card formatted as "fat"
In this case, you format the cf card with a pc using "fat" and you need several files for the amiga, like fat96 in the "L" drawer.
The easy thing is just to buy either or both, a setup ready to go cf card set from AmigaKit!
-
Cardreset usage?
The readme for cardreset is confusing... It says: "A PC Card must be plugged within the PCMCIA slot."
It also says it should be run as part of the startup-sequence... and I'm told to not insert the PCMCIA card until workbench is loaded?
Have run the command from a shell window: "cardreset TICKS 300"
(nothing happens... new line in shell)
I tried "cardreset TICKS 300 FORCE"
(nothing happens... new line in shell)
Is it meant to return some data? :-/
-
You still did NOT clarify...
Are you using a ide to cf adaptor with a proven cf card?
In this case, you use Hdtoolbox to format the cd card as a hard drive replacement!
And Are you using a PCMICA adaptor with a second cf card formatted as "fat"
In this case, you format the cf card with a pc using "fat" and you need several files for the amiga, like fat96 in the "L" drawer.
The easy thing is just to buy either or both, a setup ready to go cf card set from AmigaKit!
Sorry- this has been a multi-step process and I did get confused briefly there while trying multiple options.
Hard drive situation is sorted. IDE>CF converter working just fine... (another thread has my cheering reaction to this success)
PCMCIA situation is NOT sorted, and as such- my Amiga is completely isolated from the world.
I have Fat95 in the l drawer. Which "other files" are you referring to? I have compactflash.device in Devs and the CF0 file in devs/dosdrivers...
A card formatted as Fat or fat 32 or NTFS or whatever should still show an icon in workbench... worst case should be CF0:NDOS... but I'm not even getting the worst case outcome here.
Hardware seems fine- pins all ok and Prepcard even identifies when a CF is connected to PCMCIA... So why isn't the system detecting a card? :-/
-
It's why I asked if you had a "proven" cf card!
Some cf cards don't work. And Anything over 4 gigs needed extra care.
I use a AmigaKit set of a ide to cf adaptor with a pre-formatted 4 gig cf in three partitions.
Also from AmigaKit, My PCMICA adaptor to cf card is only 128 megs (plenty for Amiga)
The great thing was the install disk AmigaKit included in the set. It had all the files and installed them in the right places!
-
It's why I asked if you had a "proven" cf card!
Some cf cards don't work. And Anything over 4 gigs needed extra care.
I use a AmigaKit set of a ide to cf adaptor with a pre-formatted 4 gig cf in three partitions.
Also from AmigaKit, My PCMICA adaptor to cf card is only 128 megs (plenty for Amiga)
The great thing was the install disk AmigaKit included in the set. It had all the files and installed them in the right places!
I don't think you've been following as closely as the others here- this is not an issue with IDE>CF. That part is already working fine. This is a PCMCIA issue. I shouldn't need to be buying new cards that have worked fine before.
Also- this keeps getting weirder. I just removed the Boot drive contents and replaced with the old installation- mounted CF0: and tried to open it... No disk present. Then I swapped CF cards with a 16GB card I didn't expect to work at all and it gave me a DIFFERENT ERROR: "Not a DOS disk". Which is awesome, right?! Though still no disk icon on workbench...
When I switched back to the newer install- same "No disk present" error, no matter which CF card I had in there.
I think I need a different Workbench install- a reliable one... The WINUAE one is just dodgy perhaps...
Where might I find the Workbench 3.1 install disks? (still gotta run this through winuae)
Thanks again guys =)
-
I'm 99% certain this is not hardware... I just pulled another Amiga 1200 out of the garage to confirm. This one I'd used and confirmed CF (PCMCIA) was working when it had its old hard drive in it. So there's some weird bugs in the Workbench install I think...
-
True, I read thru the entire thread at once. I wasn't following because your starts and stops confused me. So I asked a first base question to get to "some" understanding.
Now, if it's software... what are the clues?
Without the cf card in the PCMICA adaptor...does the system boot from the internal cf card, which should be device CF0: (?)
If after the system boots to workbench, what do you see in the shell when you type "info"?
-
@RedWarrior
He (Thomas) means check the PCMCIA card slot on the A1200. Shine a torch in the side and just make sure there's no missing or bent pins. Just because it shows up in PrepCard doesn't necessarily mean that all of your pins are good.
http://aminet.net/package/disk/misc/cfd (http://aminet.net/package/disk/misc/cfd)
Are you using the latest CF0 and compactflash.device from the above link? Did you edit your CF0 earlier? If so please try the one direct from the above link.
-
(nothing happens... new line in shell)
You shouldn't ignore my posts and answer my questions.
http://www.amiga.org/forums/showthread.php?p=813273#post813273
And I agree with the others. You confuse people by jumping forth and back like you don't know what you're doing.
If you constantly change the starting position, it is difficult to follow a logical track.
I think I need a different Workbench install- a reliable one... The WINUAE one is just dodgy perhaps...
There is no Workbench coming with WinUAE. WinUAE is a free product under GPL license. Workbench is a commercial product, it is illegal to distribute it without a license.
If you've got Amiga Forever (which includes a workbench-311.hdf), Workbench install disks are included (as ADF files).
-
Where might I find the Workbench 3.1 install disks?
Here you go, for the princely sum of $14.25 USD:
http://amigakit.leamancomputing.com/catalog/product_info.php?products_id=1211
Also, this thread is nuts. I can't even. Might want to start over and clearly re-state exactly what you're trying to do, lol. ;)
(http://4.bp.blogspot.com/_aSlu4HgEgHo/S7PMAMhujII/AAAAAAAAALI/OSUUfk_me5Y/s1600/star-wars-darth-vader-sense.jpg)
-
OH! OH! OH! I know.
Red has a 600 which had a cf card as hard drive.
Red has a 1200 which has a bad floppy drive and moved his cf card over from his 600.
So Red tried to set up a cd card with winuae on a pc and plug it into his PCMICA slot.
It didn't work and he tried to make other things work instead!
-
You are correct Sir! :laugh1:
Gimmeeeee 5!
(http://24.media.tumblr.com/403b48a2c1ce00d058e7cc017a6a4919/tumblr_n3vm2d1oSl1ssbvp5o1_500.gif)
-
It isn't difficult - >
Copy - >
System:devs/compactflash.device
Copy - >
System:devs/dosdrivers/CF0
System:devs/dosdrivers/CF0.info
Done - Z CF card should work now - >
Copy - >
System:l/fat95
Done - Z Fat/Fat32 formated cf cards should work now.
Copy CarReset and CardPatch to you System:c folder
http://aminet.net/package/util/boot/CardPatch
http://aminet.net/package/util/boot/CardReset
Add these lines to you startup-sequence, after setpatch
C:CardPatch
C:CardReset
No other swicthes or options needed
Get small CF card like 128mb, or something like that. Format it to use FAT16 not FAT32
Open command prompt on your Win machine, type format E: (<-correct drive letter to this) /FS:Fat
If it doesn't work, you card is wrong / not supported, OR pins inside of PCMCIA connector on your Amiga is bend OR you are doing it worng