OS 3.9 installation issues

[SACC-guy]

Thanks again for your help!  I'm sorry I kept you as late as I did.  Thanks again!

Da nada, amigo

[paul1981]

What version of PFS are you using? There's a few different ones, cpu specific I believe. Can you shed any light on that? Might be worth while trying the whole install under good ol' FFS. Well, it's something else to try at least.

[Oldsmobile_Mike]

@olds-mike
I noticed two things I have no knowledge of...
He was using the PFS on sys:
and he was using two scsi controllers (scsi.device and warpscsi.device

If he's able to install the OS and run applications (I see Dopus and other things in his pics and vid) I'm assuming file system isn't an issue.  I'd make sure you're installing the latest version of PFS3-AIO from Aminet along with the C: (or at least PFSformat) tools from the 53 install.

I was pretty intimidated by PFS the first time I used it, as well, and found the lack of documentation daunting.  But it's a good FS especially for "more advanced" Amiga's (i.e., I'd use FFS if if I was just building something to play games).

Will try to load mine up later and post a few screenshots of the settings that work for me (disclaimer: your mileage may vary).  

Two controllers shouldn't be an issue, but same as we've already talked about, may be simpler to eliminate as many possible causes of issues here as possible.  Try them both on warpscsi.device.  Hummm, I wonder if maybe there is some MaxTransfer or Mask issue... it validates the CD based on the video files on there, maybe it's having a problem reading those big files off it because those settings are off?

Post a screenshot of your CD0: device settings (the text file)?

[matthey]

I was pretty intimidated by PFS the first time I used it, as well, and found the lack of documentation daunting.  But it's a good FS especially for "more advanced" Amiga's (i.e., I'd use FFS if if I was just building something to play games).

Actually, the documentation for PFS is good but it is technical and the installation process could be easier. I have had few problems with PFS but I have heard that it doesn't like a few hardware setups. I don't know if this has been improved with PFSAIO.

[Oldsmobile_Mike]

Documentation for PFS.  






Edit:  Actually, no, this is my copy of "Understanding Women".  :laughing:

[dschallock]

:laughing:

[matthey]

Documentation for PFS.  

What? They speak Chinese in the Netherlands now? I thought it was English .

Edit:  Actually, no, this is my copy of "Understanding Women".  :laughing:

Isn't that a chapter from "The Art of Love and War" by Shi Sun Tzu Mi? It takes a lot of Chinese characters just to write, "I know nothing ... nothing at all".

[dschallock]

Post a screenshot of your CD0: device settings (the text file)?

I had to work really late last night and couldn't get to my Miga, but I'll get this information tonight for sure.  Thanks again for putting brain power into this Mike!

[dschallock]

Post a screenshot of your CD0: device settings (the text file)?

Ok, here are the prefs Mike.

[Oldsmobile_Mike]

Hiya buddy!

I mean the text file, it should look something like the last screenshot of post # 9.

But on this one, why is yours CD1: instead of CD0:?

I'm still kind of grasping for straws here, but what I'm thinking is that maybe you have some kind of issue with the Mask or MaxTransfer value of your CD driver.  I've never heard of this being a problem with a CD before, especially not with SCSI, but am sure you've heard how having the wrong values can affect A1200/A4000's - file corruption, etc. when trying to read large files.  And I assume the video files on the CD that it's trying to validate against are pretty big...

Edit: any luck finding that adapter to put your CD drive on the warpscsi.device chain?

[dschallock]

Hiya buddy!

I mean the text file, it should look something like the last screenshot of post # 9.

But on this one, why is yours CD1: instead of CD0:?

I'm still kind of grasping for straws here, but what I'm thinking is that maybe you have some kind of issue with the Mask or MaxTransfer value of your CD driver.  I've never heard of this being a problem with a CD before, especially not with SCSI, but am sure you've heard how having the wrong values can affect A1200/A4000's - file corruption, etc. when trying to read large files.  And I assume the video files on the CD that it's trying to validate against are pretty big...

Edit: any luck finding that adapter to put your CD drive on the warpscsi.device chain?

When I installed 3.1  I used the CD0 device to get the CDROM working.  When I was installing 3.9 I installed the CDROM software off the 3.9 CD and it automatically created CD1 because CD0 was already mounted.  I just deleted CD0 after CD1 was installed.  I'm not sure how many places I would need to change in order to switch it to CD0.  Startup-sequence assign maybe and tooltype and rename the file?
Anyway, man I wish it was a max transfer thing.  That would be a sweet fix.
Here is the text file I think you were talking about.

[Oldsmobile_Mike]

This is an addendum  to the logic in the previous post:  You mentioned only  having 2MB chip on the A3000 motherboard.  The rest of your memory is on your accelerator.  Your CD drive is on the A3000 built-in SCSI.  Your hard drive is on your accelerator.  Depending on what type of memory and how much is allocated to the buffer on the CD drive...  I'm thinking it's trying to read these huge video files on the disc, and since it has to go through the motherboard to get from the CD to the accelerator memory, if it has to try to buffer through that meager 2MB of chip ram you've got on there...  Get what I'm saying?  Makes sense to my "it's 2am and I need to go the %#$# to sleep" brain, anyway.  LOL.  

[dschallock]

This is an addendum  to the logic in the previous post:  You mentioned only  having 2MB chip on the A3000 motherboard.  The rest of your memory is on your accelerator.  Your CD drive is on the A3000 built-in SCSI.  Your hard drive is on your accelerator.  Depending on what type of memory and how much is allocated to the buffer on the CD drive...  I'm thinking it's trying to read these huge video files on the disc, and since it has to go through the motherboard to get from the CD to the accelerator memory, if it has to try to buffer through that meager 2MB of chip ram you've got on there...  Get what I'm saying?  Makes sense to my "it's 2am and I need to go the %#$# to sleep" brain, anyway.  LOL.  

Actually that's pretty brilliant, or I'm equally tired.  I think the easiest fix try for that theory is to get the CDROM on the warpdevice as well.

[Oldsmobile_Mike]

Gah, I'm confused again.  So are you installing a fresh 3.9?  Or 3.9 on top of 3.1?

Also, from your screenshot, "BufMemType = 513".  I wish Thomas was here, but as far as I know there's only supposed to be a single digit there, 0 through 5:

Buffer Type: 0,1=Any, 2,3=Chip, 4,5=Fast RAM

Try changing that field to a 1 and see what happens.

Next try changing your MaxTransfer to 0x1fe00.

Try increasing the number of buffers from 50 to say, 200.

Make these changes one-at-a-time, and note if anything changes.  

[Rotzloeffel]

 I think the easiest fix try for that theory is to get the CDROM on the warpdevice as well.

Yes, but you need a little Hardware-Hack to get it working in the A3000 !

It is incompatible with the A3000's motherboard SCSI controller - replacing the A3000's SCSI chip to rev. 08 solves the problem.

And the device is called warpdrive.device

[dschallock]

Gah, I'm confused again.  So are you installing a fresh 3.9?  Or 3.9 on top of 3.1?

I did do a fresh install, it wasn't over 3.1... however the emergency disk I created was made on a fresh 3.1 install which meant the CD driver was the 3.1 CD0 driver in Devs/dosdrivers/.  That was necessary just to get the system to boot and recognize the CD to be able to install 3.9.  But the 3.1 CDROM driver has problems not the least of which is the truncated file names, so I installed the CDROM software from the 3.9 install which is improved. Does that make sense or am I explaining it wonky?

Also, from your screenshot, "BufMemType = 513".  I wish Thomas was here, but as far as I know there's only supposed to be a single digit there, 0 through 5:

Buffer Type: 0,1=Any, 2,3=Chip, 4,5=Fast RAM

Try changing that field to a 1 and see what happens.

Next try changing your MaxTransfer to 0x1fe00.

Try increasing the number of buffers from 50 to say, 200.

Make these changes one-at-a-time, and note if anything changes.  

Awesome tips, Thank you.  I will try these one at a time.  I guess the test after each change is to try and install boingbag1.