WB 3.1 will not boot on A2000!?

[Findlarn]

Spitballing here, but is JP2 enabled?

You mean autobooting? Yes, it is set to "AUTO"...

[wlemonds]

But what I don't understand however is that the A2091 doesn't seem to have any termination jumpers on the PCB:

http://www.bigbookofamigahardware.com/bboah/product.aspx?id=1161

The 3 black pins between the internal scsi connector and the words "Internal SCSI Connector" are the termination and can be removed.

[Findlarn]

The 3 black pins between the internal scsi connector and the words "Internal SCSI Connector" are the termination and can be removed.

Do you mean those soldered resistor packs? But if those are there, that means termination is on, right? So no need to remove them... But does that also mean that you cannot have an external SCSI device installed at the same time?...

Anyway... I will play around with those jumpers as soon as I can, and will come back later to report my results...

[Oldsmobile_Mike]

It's been a while since I mucked around with it, but I think you need to have termination on the card, the last device of your internal chain, and the last device of your external chain. But SCSI can be finicky, lol. Still, I wouldn't remove them from the card unless you are really are sure what you're doing.

Edit: btw, what are your Mask and MaxTransfer values in HDtoolbox?

[Findlarn]

It's been a while since I mucked around with it, but I think you need to have termination on the card, the last device of your internal chain, and the last device of your external chain. But SCSI can be finicky, lol. Still, I wouldn't remove them from the card unless you are really are sure what you're doing.

Edit: btw, what are your Mask and MaxTransfer values in HDtoolbox?

Well, I didn't exactly plan to desolder them... When I said "playing around" I only meant the jumpers on the card reader... I would never attempt to remove those unless it turns out to be absolutely necessary.

And regarding the Mask and MaxTransfer values I will try to remember checking those as well...

[madgrizzle]

Found this thread:
http://www.amiga.org/forums/archive/index.php/t-61819.html

So it should be workable.. someone else has managed to get an A2091 to work with a mechware reader.

[Matt_H]

I'm using one of these card readers (I think it's the -50B) on an A2000 with a 2091 with no issues. Not really sure what the problem could be. I have LUNs disabled so only the PCMCIA slot works, which I use with a CF adapter. With LUNs enabled, the machine takes far, far longer to boot - longer than I have patience for - since it polls each LUN at each SCSI address. My 2091 has 2MB of RAM installed and the system is also using a 2630 accelerator with 4MB. I don't remember my jumper settings on the card reader, but presumably I have termination enabled since it is the only SCSI device in the machine. I have nothing connected to the external SCSI port.

It sounds like you are able to boot from floppy and insert the CF drive afterwards to work on it in HDToolbox? Are there any filesystems installed in the RDB? Maybe the system is getting hung up on something there. SCSI reselection may be another flag worth investigating.

Are the v7 ROMs installed correctly (i.e., not accidentally swapped)? What revision DMAC chip is in your 2091? What revision SCSI chip?

[wlemonds]

Do you mean those soldered resistor packs? But if those are there, that means termination is on, right? So no need to remove them... But does that also mean that you cannot have an external SCSI device installed at the same time?...

Anyway... I will play around with those jumpers as soon as I can, and will come back later to report my results...

Sorry, I screwed up. I've been working on different systems with 2091, Fastlane, and Rapidfire. The 2091 has them soldered.

[Findlarn]

I'm back folks!

And I think that I have finally solved it now! It was a ridiculously easy fix! All I needed to do was to add another jumper to the card reader, making it device number 1. Previously it was set to 0. I also remember now that when I originally installed it I did not know that the A2091 counts as a device itself, hence I set it to 0. In other words the A2091 is apparently by default set to 0 so therefore your added unit must be 1 or higher in order to work. At least that's what I can make of it.

Matt_H:
That's strange... mine isn't any slow when booting with LUN activated!? Or how inpatient are you? It was painfully slow however, before I changed the jumper settings. But now it boot's up pretty quickly. Even when the CF card is inserted in the CF slot. Although it boots slightly faster when it's through the PCMCIA slot... Actually I'm very surprised at this. So that was indeed a nice bonus feature! In fact I think I can live with this controller card a bit longer now before upgrading. Mine is rev. 4.0 btw...

wlemonds:
Well... That that took care of a lot of confusion for me. Thanks!


And now when all this is taken care of I have a couple of other small questions I would like to take care of in order to get me going with this

What do I need in order for the Amiga to be able to read FAT formatted devices? Where do I find a driver for this? And how do I install it? Do I just need a simple driver file to put in my "DosDrivers" drawer? (I remember having something like that for my 1200, unfortunately I don't remember where I got it or how I installed it) And also, are the cards (other than the HDD with the OS) hot-swap able? I ask this because I (obviously) want the simplest/fastest way possible to transfer files over to the Amiga...

And one more final question... Is there a driver or something for reading jpg/jpeg? (Good for desktop backgrounds etc.)

[Oldsmobile_Mike]

What do I need in order for the Amiga to be able to read FAT formatted devices? Where do I find a driver for this? And how do I install it? Do I just need a simple driver file to put in my "DosDrivers" drawer? (I remember having something like that for my 1200, unfortunately I don't remember where I got it or how I installed it) And also, are the cards (other than the HDD with the OS) hot-swap able? I ask this because I (obviously) want the simplest/fastest way possible to transfer files over to the Amiga...

You need this:

http://aminet.net/package/disk/misc/fat95

Read the instructions carefully, it can be kind of tricky to do the initial setup.  Otherwise, yes to all of your questions.  I use a FAT-formatted SD card in my A2000.  When I want to swap files I pop it out and pop it in the card reader on my PC and copy away.  Yes, I could also use USB or network (since my A2000 has both of those) but the SD card is almost too easy to need any other solution.  

And one more final question... Is there a driver or something for reading jpg/jpeg? (Good for desktop backgrounds etc.)

Plenty of applications on the Amiga can read .jpg files.  If you want to open them natively (i.e., with Multiview or the Workbench wallpaper prefs) you need a .jpg datatype.  These are the best:

http://www.warpdt.co.uk/

You don't have to register but it doesn't hurt to throw the author a few bones for his trouble.  

Also, while you're at it, you mention using 3.1.  If you're not ready to upgrade to 3.9 (or don't have the system specs to support it), check out this:

http://lilliput.amiga-projects.net/BetterWB.htm

Have fun!  

[Matt_H]

I believe the 2091 controller itself is ID 7, so your device should have worked at ID 0. There are a number of hidden RDB flags having to do with identifying the last device on the chain so that the controller stops looking for others. (Sometimes HDToolbox with start up with a message "Drives have been added or removed from the system" which is an indication that it wants to update that flag.) I wonder if one of those flags was choking with ID 0.

My controller starts to boot instantly with LUNs disabled, but enabling them added a 20-30 second delay. That delay wasn't worth it to me since I don't need to sneakernet files to the machine. It's on the network so I just send things over that way.

For transferring from Windows drives you need fat95 on Aminet. I think you'll need to create a DOSDriver, too. GiggleDisk (also Aminet) can pull the geometry and do that for you.

[Findlarn]

Oldsmobile_Mike:
Thanks for the links! And of course it was on Aminet! Why didn't I think of that!? But on the other hand I didn't remember the name of it.... I know now that I've used it before. But that time I think it was pre-installed and  used under that alternative, strange "clunky" WB version. What was the name of that monstrosity again? Anyway... I also upon further inspection noticed that "FAT95" was already included! But not installed. I've looked into it a bit, but it looks quite complicated... Have I gotten this part right?

compactflash.device in "DEVS"
fat95 in "L:"
CF0 in "DEVS/DOSDrivers"

Is that all I need to know? Or is there more to it? How about the startup sequence? (the part that looked most complicated)

I will eventually check out the jpeg thing as well... It's just that I prefer to focus on one thing at a time, and when that works 100% I can move on to the next. Makes most sense to me...

And yes, I know about "BetterWB" Maybe I should give that a go. Because with my current specs there's no way that 3.9 would work. Plain 68000 processor and 3mb of ram...


Matt_H:
So the 2091's ID is actually 7. Hm... that's interesting... Might be useful to know sometime in the future And pardon my ignorance, but what is "Sneakernet"...? Is that something you use with "X-Surf"...?

[Oldsmobile_Mike]

Sneakernet means to walk a disk from one machine to another. :roflmao:

[Matt_H]

Sneakernet is a joke networking term referring to transferring files by walking them from one machine (while wearing sneakers ) to another using removable media (floppy, CD, USB stick, etc.). No actual network hardware/software is involved.

(To explain my previous comment further, since my machine is on the network, I don't need to use any of the other card reader slots for transferring files back and forth and so I disabled LUNs.)

[PanterHZ]

Have I gotten this part right?

compactflash.device in "DEVS"
fat95 in "L:"
CF0 in "DEVS/DOSDrivers"

Is that all I need to know? Or is there more to it? How about the startup sequence? (the part that looked most complicated)

Forget about compactflash.device since this is for the A600/A1200 PCMCIA port only. Fat95 is correct, and you can use the CF0 file after modifying it a little. Just open CF0 in a text editor and change compactflash.device to scsi.device. Next you must change the Unit number, which must consist of the Unit number of your card reader followed by the LUN number of the slot you want to use. In your case it should be 10 for Unit 1 and the first slot (LUN 0) for example.

You shouldn't have to change anything in the Startup-Sequence.

[Findlarn]

Sneakernet is a joke networking term referring to transferring files by walking them from one machine (while wearing sneakers ) to another using removable media (floppy, CD, USB stick, etc.). No actual network hardware/software is involved.

Haha ok, you really got me there! :lol: I'm Swedish you know, and doesn't always know these terms :laugh1: And yes I understand what you meant now with the networking thing

Forget about compactflash.device since this is  for the A600/A1200 PCMCIA port only. Fat95 is correct, and you can use  the CF0 file after modifying it a little. Just open CF0 in a text editor  and change compactflash.device to scsi.device. Next you must change the  Unit number, which must consist of the Unit number of your card reader  followed by the LUN number of the slot you want to use. In your case it  should be 10 for Unit 1 and the first slot (LUN 0) for example.

You shouldn't have to change anything in the Startup-Sequence.

Sounds a lot easier then the included instructions... I think I can get it going now. I will try that out as soon as I can