I own a Surf Squirrel for my Amiga 1200, my Amiga 1200 specs is as follows: 68060 @ 50 Mhz with 64 MB of RAM, OS 3.5. Everytime I use the Surf Squirrel it freezes my Amiga 1200 totally. If I am transfering files from the CD to the harddrive, the transfer continues but after a while no more than one minute or so, the entire system freezes over. It happens everytime, even if I do transfer, then stop it, then restart, then stop it, then restart, it freezes. Is this a software or hardware problem? Can anyone help me solve this problem? I have big files I want to transfer to my Amiga 1200 using the CD-ROM and I am unable to do that because it keeps freezing my system and cause validation problems on my harddrive. Thanks in advance.

@Foody

Can anyone help me please?

@Foody

I am sorry i cannot help but tell you i had the same problem.
The advice i was told was to check my termination on the scsi drives was set right.
I checked it made no difference.
At one point i bought a new cdrom drive and that one worked well for a while then it developed the same symptoms you describe.
I found if i stopped the transfer of files every now and then it would get through them all. Installing Heretic2 was murder.
Eventually i was using an ide drive instead.

_________________
A1/G4 1GHZ

OS4.1 latest update.
1ghz Radeon Club3d 9250
Usb/Dma fixed.

@Foody

What are the version numbers of devs:squirrelscsi.device and libs:surfsquirrel.library that you're using?

_________________
IBrowse, AmiSSL and Warp Datatype Developer

@Foody

Never used a surf squirrel...
But try this (if you can)
Set the SCSI devices to asyncronous transfer... Worked for the SCSI DVD drives on my Cyberstorm... (I had the freezing problem too)

_________________
Back to action!

@Foody

Your setup is similar to mine.

Since your system works for a while then freezes (rather than simply not working) it may be as was suggested above that you have some issues with the SCSI chain, or it could simply be a dodgy drive. However, some other possibilities are:

1) Have you changed anything in your CD0 mount-file since it was last working (Or has it never worked)? Is the stack space big enough, options for your drive correct etc?

2) Have you tried seting MaxTransfer to a lower value? - Try 0x7ffff.

3) I found that the "SquirrelSCSI" command in the startup-sequence needs to be before Setpatch else my system would freeze.

4) If you have a Phase5 Blizzard accelerator, use the "cpu060" command to see if it shows your 68060 to be a "rev 1". If so you need to run "cpu060 nostb" to disable the faulty bypass cache and avoid random crashes.

5) Make sure you have the latest library for your accelerator card. Alternatively consider installing Thor's MuLib package and use the 68060.library from it.

6) If you're using Executive, make sure the capture range isn't above priority 1.


Maybe something there could help!?

@Foody

My setup and problems were different from yours, but you could have a look at this anyway.
I had A1200 + Bz1230 IV with OS 3.9 and a SCSI burner attached to the Surf Squirrel II. At some point, the burner started destroying CDs when adding tracks 4 times out of 5. It took me a long while to figure out what the problem was. Eventually, I discovered that the DEVS:NSDPatch file had this line:

DEVICE squirrelscsi.device DEVICETYPE NSDEVTYPE_TRACKDISK COMMANDS 1-15,20-23,28 VERSION 37 REVISION 1765

but, indeed, I had newer drivers already! So, to fix the problem, all I had to do was commenting that line out.
I can't remember whether that line was introduced in OS 3.5 or OS 3.9 and, of course, your case is quite different from mine, but I guess that checking the version number of your drivers won't hurt

saimo

Last edited by saimo on 17-Sep-2006 at 04:01 PM.

_________________
RETREAM - retro dreams for Amiga, Commodore 64 and PC

All

@All

I am going to follow all your advices there and follow the steps and see what can be done about it. As for the versions of the specified libraries squirrelscsi.device and surfsquirrel.library as follows:

squirrelscsi.device (40.44)

@Foody

Quote:

As for the versions of the specified libraries squirrelscsi.device and surfsquirrel.library as follows: squirrelscsi.device (40.44)

I don't have those files at hand, so I can't compare. However, the version you report is likely to be greater than the one in the NSDPatch file, so I suggest you comment the relevant lines out.

saimo

_________________
RETREAM - retro dreams for Amiga, Commodore 64 and PC

@Foody

The 40.44 is for surfsquirrel.library, I guess. AFAIK, the latest versions are surfsquirrel.library 40.45 and squirrelscsi.device 37.1823. I remember the CD lockup problem well, but IIRC I only ever had it with the original Squirrel and not the Surf Squirrel - might be related to old driver files.

_________________
IBrowse, AmiSSL and Warp Datatype Developer

@Futaura & Foody

I can confirm the version numbers reported by Futaura. Besides that, there is also squirrelserial.device 37.565. AFAIK, those were the last drivers released.

saimo

_________________
RETREAM - retro dreams for Amiga, Commodore 64 and PC

@Laser

Quote:

Have you changed anything in your CD0 mount-file since it was last working (Or has it never worked)? Is the stack space big enough, options for your drive correct etc?

I have not touched a single configuration of the CD0 mount file at all. It was working ever since I installed the drivers for the Surf-Squirrel. Stack space? I never tried increasing the stack space before. I believe all the options and configurations are correct, at least the best of my ability I could be wrong.

Quote:

Have you tried seting MaxTransfer to a lower value? - Try 0x7ffff.

No, how do you do that? Could you show me step by step to lowering the MaxTransfer to that value? Thanks in advance.

Quote:

I found that the "SquirrelSCSI" command in the startup-sequence needs to be before Setpatch else my system would freeze.

There were no exact SquirrelSCSI command persay in my startup-sequence, just an if statement that executes the cd32 startup or something like that which of course have the other necessary command lines etc to mount and activate the cd burner. I did what you suggested, the CD ROM detected right away but as soon as the SetPatch command was executed it crashed right away. I had to return it back to it's normal setting in order for me to boot right away. I don't know if that means anything.

Quote:

f you have a Phase5 Blizzard accelerator, use the "cpu060" command to see if it shows your 68060 to be a "rev 1". If so you need to run "cpu060 nostb" to disable the faulty bypass cache and avoid random crashes.

I don't have the CPU060 oddly enough even though I own the blizzard 1260 card. So this I cannot do much about.

Quote:

Make sure you have the latest library for your accelerator card. Alternatively consider installing Thor's MuLib package and use the 68060.library from it.

I do have that! Don't worry about this part, thank God.

Quote:

If you're using Executive, make sure the capture range isn't above priority 1.

Executive? I don't know what Executive is! I don't think I am using Executive. However, how do I make sure the capture range isn't above priority 1?

@saimo

Quote:

DEVICE squirrelscsi.device DEVICETYPE NSDEVTYPE_TRACKDISK COMMANDS 1-15,20-23,28 VERSION 37 REVISION 1765

This perticular line was found in NSDPatch.config file and it is like this:

#DEVICE squirrelscsi.device DEVICETYPE NSDEVTYPE_TRACKDISK COMMANDS 1-15,20-23,28 VERSION 37 REVISION 1765

I assume that it is commented and thus not used at all. Am I correct in my assumption? I own OS 3.5 however.

@saimo

Quote:

I don't have those files at hand, so I can't compare. However, the version you report is likely to be greater than the one in the NSDPatch file, so I suggest you comment the relevant lines out.

I assume:
#Command line
is commented isn't it? if it is then it is already commented like that. I guess that is not the problem after all.

@All

I have tried some of the suggested requests and still face the problem...anyone here have another suggestion, thanks in advance?

@Foody

Yes, the dash comments the line out, so, if you have the newer drivers (see the version numbers reported above) the problem lies elsewhere. Unfortunately, I can't help.

saimo

_________________
RETREAM - retro dreams for Amiga, Commodore 64 and PC

@Foody

Quote:

Could you show me step by step to lowering the MaxTransfer to that value?

Edit your DEVS:DOSDrivers/CD0 file to include the line

MaxTransfer = 0x7ffff

It probably wont help, but its worth a try when things basically work but fail on larger files.


Quote:

There were no exact SquirrelSCSI command persay in my startup-sequence, just an if statement that executes the cd32 startup or something like that which of course have the other necessary command lines etc to mount and activate the cd burner. I did what you suggested, the CD ROM detected right away but as soon as the SetPatch command was executed it crashed right away.

Hmph! The exact opposite of what I find. Mind you, that CD32 startup is designed to allow easier booting of CD32 game disks, and can play about with your system in unexpected ways. It isn't needed (other than the SquirrelSCSI command) to actually use the CD-ROM drive.


Quote:

I don't have the CPU060 oddly enough even though I own the blizzard 1260 card.

Check your PM's. You say later you are using the MuLib 68060.library which ISTR automatically sets this. It doesn't hurt to check.


Quote:

Executive? I don't know what Executive is!

Then you needn't worry about it!
It's a very good system patch that makes multitasking much nicer.


Are you running one of CyberPatcher, OxyPatcher or MuRedox? It may not specifically help here, but it is generally useful to do so.