I have a problem w SCSI controler on my CSPPC card use it with OS4. My harddisk is 36,4GB Ultra Wide SCSI. Works perfecly with OS3.9 + BB2 and MuTools.
Today I decide to install OS4 on this disc. By Media Toolbox I created partition 1GB with FFS with long names support. On this partition i set block size to 1024, 180 buffers, Max. transfer to FFFE00 and Mask to 7FFFFFFF and saved settings. I did reboot like Media Toolbox suggest. After reboot I run installation with OS4, quick format partition I created and install system. After reboot system loaded, on my screen comes requester with information like:
Wolumen OS4 has read error in block nr 687425
This requester comes very often and very diffrent moment when I use OS4. The block number is always diffrent. When I try use other partitions with data, I have the same requesters with errors on that partitions. I tryed to change Max. transfer value to smaller but nohing change. So my very fast SCSI disk is useless on OS4 :(
Weird is that on OS3.9 everythink is OK. I can play games, use programs and nothing bad happend. Są I think this is bug in cybppc.device ? Anyone have the same problems?
As soo as I return home will check the specs of my OS4 partition and re post here. You probably do something wrong with the specification you are giving to the OS4 partition.
I wonder if you're using the right dos code for the FFS system... If I remember rightly (can't remember which revision it affected) but even if you selected in toolbox you wanted to use FFS with longname support you had to alter it manually...
read your book and check this? Or I could be completely wrong ie without proper dos code it wouldn't work anyway...
check ya config file in your kickstart directly too... perhaps there is some options relating to the PPC that caters to the UW...
I run OS4 on my 233mhz PPC too but my UW HD died quite some time ago and I never replaced it...
I never boot the system anymore since I've gone SAMs way... adios!
~Yes I am a Kiwi, No, I did not appear as an extra in 'Lord of the Rings'~ 1x AmigaOne X5000 2.0GHz 2gM RadeonR9280X AOS4.x 3x AmigaOne X1000 1.8GHz 2gM RadeonHD7970 AOS4.x
As soo as I return home will check the specs of my OS4 partition and re post here.
Would be great. Thank You :)
Quote:
You probably do something wrong with the specification you are giving to the OS4 partition.
I did the same with IDE hard disc (partition, installation and others) and everything works perfectly. No error requesters. I think I did everything in right way.
I wonder if you're using the right dos code for the FFS system... If I remember rightly (can't remember which revision it affected) but even if you selected in toolbox you wanted to use FFS with longname support you had to alter it manually...
I did.
Quote:
check ya config file in your kickstart directly too... perhaps there is some options relating to the PPC that caters to the UW...
Good idea! I will.
Quote:
I run OS4 on my 233mhz PPC too but my UW HD died quite some time ago and I never replaced it...
Why not? Today this discs on ebay it's really cheap. I have second exactly the same disc for day when my current disk be bad.
Quote:
I never boot the system anymore since I've gone SAMs way... adios!
I did some tests and found some conclusion. I have two SCSI device.
1. Streamer HP SureStore DAT24 SCSI II 2. IBM UW Fast SCSI 36,4GB HDD
In CSPPC bios both are setup to: - 15 transfer offset - 10MHz sync period - Synchron - 8-Bit bus - No reselection
When I turned off (NO LUN) Streamer, reboot and OS4 come up. Guess what? No error requesters! So I turned on Streamer and changed "Synchron" to "Async/Synchron". Reboot and now is much better. I almost have no error requesters with read error.
It's really weird that on OS3.9 everythink is OK with or without this change.
Out of topic Did You know that if you start OS4 then You can't get in to csppc bios? Anyone have the same?
I think the CSPPC early-startup hooks into a vector that's bypassed by the OS 4 startup (which over-rides the original ROM startup in the same way as those old Kickstart 1.3 compatibility disks worked). If you hold down the C+A+A for long enough to remove that vector (a number of seconds) it'll go through the original bootstrap code and you can run the CS-PPC menu again by holding down Esc as normal.
I think the CSPPC early-startup hooks into a vector that's bypassed by the OS 4 startup (which over-rides the original ROM startup in the same way as those old Kickstart 1.3 compatibility disks worked). If you hold down the C+A+A for long enough to remove that vector (a number of seconds) it'll go through the original bootstrap code and you can run the CS-PPC menu again by holding down Esc as normal.
I think. :)
Yes it works and I knew about that. I wrote about CSPPC menu problem with hope that sombody found solution. Thank you for advice :)
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
