#Read/Write Errors
5 messages in this thread
Don:
By the time you got through that mess I called a "little problem", I
think I may have found it myself, and now need to know the cheapest way to
work around it.
I went to Dave Haynie's SetCpu program and altered the arguments so that
the instructions were CACHE and BURST but the data was rendered just the
opposite. This drags the speed of the A3001 board down from 10.96 times
the standard speed (per the Ronin test program) to where is is about 7.7
times. However, the 2090a at least operates without the read/write errors.
It looks like I am in need of a faster controller for my St-506 Rodime.
Do you agree, and do you have any suggestions?
Thanks
Regards Tom
If your useing setcpu 1.6, try the cardromlist. Moveing the drive to 32bit
ram may work,thats driver,. You can also use diskx to edit the boot track
mountlist to use fastram for buffers only.
John.
John:
Hit me again on how to use DiskX. I have no 16 bit fast ram. I have a
2000 with a 1 Meg Agnus and an A3001 with 4 Megs of 32 bit ram. I have the
ICD with an external Syquest and the 2090a with the ST506 Rodime. The only
other item in there is the MicroWay Flicker-Fixer. I *think* I would like
to map the 2090A ROM into Chip ram. I don't trust my Agnus chip fully
because I just saw a thread where someone returned his because it went
crazy when he typed GoPal. So does mine. 😎 Whoopeeee!
Regards Tom
One mount res0: two access res0: There go two block 0 Now the fun starts.
What you see is the mountlist used at boot up. The big hex number is
maxtranfer. The next is memorymask. The last is dostype 444F5301 if FFS or
300 if not. Now go to block 68. You will see the same thing. If you change
anything, you must do it to both blocks.
You may try changing dostype to FFS, so the hole disk is FFS. Also note
there is a fix ,or some what so, for overscan. You the program 2090fix and
change the maxtransfer numbers for it to work.
Diskdrives me crazy John ;-).
Tom,
I think you need to talk to GVP and see what they say.
Don