Overview Features Instructions Performance Forum Downloads Products Reseller Contact

Welcome to the Apollo Forum

This forum is for people interested in the APOLLO CPU.
Please read the forum usage manual.
VISIT APOLLO IRC CHANNEL



All TopicsNewsPerformanceGamesApolloVampireReleases
The team will post updates and news here

Sagasd.devicepage  1 2 

Sean Sk

Posts 59
13 Nov 2017 14:07


Ok Iíve just seen a couple of problems with the surfaces and blocks per track values. Will change them tomorrow. But if someone is able to tell me how I can get HDToolBox 45.6 and get it to work in WB 3.1 that would be great.


Martin Soerensen

Posts 143
13 Nov 2017 14:44


I think it may be the version included with WB 3.9? Not sure if it can run under 3.1. At least not without replacing all relevant libs to their 3.9 counterparts.


Thomas Blatt

Posts 72
13 Nov 2017 14:51


Now I am using my MicroSD card with FFS and have no more write errors. I copied one time all my WHDLoad games to the MicroSD card. For WHDLOAD games is FFS fast enough.
  I got everytime with SFS and PFS write errors.
 


Simo Koivukoski
(Apollo Team Member)
Posts 263
13 Nov 2017 16:58


sean sk wrote:
Total number of blocks reported by SDDiag is 61071360.
61071360 / 16 Heads / 63 Blocks per Track = 60586 Cylinders
 
60586 Cylinders
    16 Heads
    63 Blocks per Track
    1008 Blocks per Cylinder (16 Heads * 63 Blocks per Track)
-> park head 60586

I tested this with the same values:
 
SD0:
FileSystem       = l:pfs3_aio-handler
Device          = sagasd.device
Unit            = 0
BlockSize        = 512
Surfaces        = 16
SectorsPerBlock  = 1
BlocksPerTrack  = 63
Reserved        = 2
PreAlloc        = 0
Interleave      = 0
MaxTransfer      = 0x0001FE00
Mask            = 0xFFFFFFFE
LowCyl          = 2
HighCyl          = 30293
Buffers          = 300
BufMemType      = 0
StackSize        = 16384
Priority        = 0
GlobVec          = -1
DosType          = 0x50445303
Activate        = 1
Mount            = 1
/* Bootable      = FALSE */
SD1:
FileSystem       = l:pfs3_aio-handler
Device          = sagasd.device
Unit            = 0
BlockSize        = 512
Surfaces        = 16
SectorsPerBlock  = 1
BlocksPerTrack  = 63
Reserved        = 2
PreAlloc        = 0
Interleave      = 0
MaxTransfer      = 0x0001FE00
Mask            = 0xFFFFFFFE
LowCyl          = 30294
HighCyl          = 60585
Buffers          = 300
BufMemType      = 0
StackSize        = 16384
Priority        = 0
GlobVec          = -1
DosType          = 0x50445303
Activate        = 1
Mount            = 1
/* Bootable      = FALSE */
Here's video how I made it on OS31: EXTERNAL LINK 

Always remember to press enter after each field that you enter on HDToolBox!
 
 
 


Sean Sk

Posts 59
14 Nov 2017 02:29


Well I re-created the partitions and made sure the following were the correct values in the mountlist:
 
  Surfaces        = 16
  SectorsPerBlock  = 1
  BlocksPerTrack  = 63
 
(I don't know why they were different last time, I assumed I pressed enter when I changed the values.)
I also followed Simo's video to the letter.

  Anyway I'm still getting "Write Error 29" and "LRU Update" errors with PFS3. I tried using FFS and was getting "You MUST replace volume (name) in device SD0 !!" which leads me to believe the SD Card is being unmounted during the middle of a write/format.
 
  Is it possible the SD Card reader in my V600 2 is faulty?


Simo Koivukoski
(Apollo Team Member)
Posts 263
14 Nov 2017 05:43


Does it works OK with the default Gold 2 x11 core?


Sean Sk

Posts 59
14 Nov 2017 08:02


Simo Koivukoski wrote:

Does it works OK with the default Gold 2 x11 core?

No. It does the same thing on GOLD 2.

I'm using Cloanto's latest WB 3.1 which had an update in 2016.
When trying to follow the procedures I have noticed that when I type "SYS:Tools/HDToolBox device=sagasd.device" nothing shows up in "Hard Drives in System" box. So I checked the Tool Types of HDToolBox and noticed the following:

SCSI_DEVICE_NAME=scsi.device
SCSI_MAX_ADDRESS=6
SCSI_MAX_LUN=7
XT_NAME=  XT

I have been changing the first line to "SCSI_DEVICE_NAME=sagasd.device" so that the SD Card will show up.

I don't know if this will have any bearing on things.


Simo Koivukoski
(Apollo Team Member)
Posts 263
14 Nov 2017 08:38


Could you test with the FAT32? It is easiest to setup, because fat95 device has partition geometry autosense.

Format your SD card on PC to FAT32 fileformat in the normal way. Do not use any Amiga tools like HDToolBox, SDMount or Giggledisk.

Make sure you have:

DEVS:sagasd.device
L:fat95
DEVS:DOSDrivers/SD0
DEVS:DOSDrivers/SD0.info
Make sure that your DEVS:DOSDrivers/SD0 mountlist uses partition geometry autosense, its contents must be like this:
FileSystem     = l:fat95
Device        = sagasd.device
Unit          = 0
Flags          = 0
LowCyl        = 0
HighCyl        = 0
Surfaces      = 1
BlocksPerTrack = 1
BlockSize      = 512
Buffers        = 300
BufMemType    = 1
BootPri        = 0
Stacksize      = 4096
Priority      = 5
GlobVec        = -1
DosType        = 0x46415401

For the quick test, delete all SD related stuff from your DEVS:DOSDrivers -folder and extract this to the your SYS: EXTERNAL LINK


Sean Sk

Posts 59
14 Nov 2017 21:27


Thanks Simo.

I have tried the fat95 set up. But when I am copying files to the SD Card from my CF Hard Drive it once again gives me an error:

Please re-insert disk "name"!

If I press "Retry" it will continue but will throw the error up again a little later. Same with FFS. With PFS it just completely spits the dummy and won't let me continue.

There something not right. It's got to be the Vampire's card reader.

Could it also be a power issue? I am using an Amiga 500 power supply because they deliver more power than the A1200 or A600 PSU's. Could it still be a problem?


Simo Koivukoski
(Apollo Team Member)
Posts 263
15 Nov 2017 06:28


We use 30 years old hardware, so most important thing is that, both, your Amiga and PSU are recapped.
 
This "re-insert disk" is known issue. Some uSD brands gives a lot of CRC-errors and lowering speed is the only cure. We need help to repair this (also boot and hot swap would be a cool features).
 
You can test with the older driver, but I cannot promise that it works any better: EXTERNAL LINK


Sean Sk

Posts 59
15 Nov 2017 07:51


Ok its nice to know that its a known issue and im not the only one to have had it.
 
  Yeah both computer and PSU have brand new caps. PSU is in excellent shape but wasnt sure if power was an issue. But I dont think it is since the Amiga 600 and the Vampire have been completely stable and havent had any crashes whatsoever in the 6 months Iíve had the V600 2.
 
 
 
 

posts 31page  1 2