English Amiga Board


Go Back   English Amiga Board > Support > support.Hardware

 
 
Thread Tools
Old 23 March 2017, 21:15   #341
demolition
Unregistered User
demolition's Avatar
 
Join Date: Sep 2012
Location: Copenhagen / DK
Age: 37
Posts: 3,342
Not sure what NT means but it is surely not related to SCSI termination since it is not relevant to the file system side.
demolition is offline  
AdSense AdSense  
Old 23 March 2017, 21:32   #342
ShK
Apollo Team
ShK's Avatar
 
Join Date: Mar 2013
Location: Lahti / Finland
Age: 46
Posts: 258
Quote:
Originally Posted by blatboy View Post
I'm assuming *NT means not terminated?
* means this partition is not ok
N means the device supports NSD, but the file system doesn't
S means the device supports SCSI, but the file system doesn't
T means the device supports TD64, but the file system doesn't
ShK is offline  
Old 23 March 2017, 21:35   #343
fgh
Registered User
 
Join Date: Dec 2010
Location: Norway
Posts: 585
But check4gb does not know pfs3aio and is therefore obsolete. Use hddreport instead.

Edit: Did you get a reply from the scsi2sd author?

Edit 2: Scsi.device lives in your kickstart rom. You talk about it as if it's a file you can just change. If you are using classicwb (which has such a mechanism in startup-seq) and there is a random scsi.device file in devs:, just delete it, so you're not patching a random version.

Last edited by fgh; 23 March 2017 at 21:45.
fgh is offline  
Old 23 March 2017, 21:54   #344
blatboy
"The Lurker"

blatboy's Avatar
 
Join Date: Mar 2017
Location: NYC/USA
Posts: 27
Great! I'll do that


Sent from my iPhone using Tapatalk
blatboy is offline  
Old 25 March 2017, 05:06   #345
blatboy
"The Lurker"

blatboy's Avatar
 
Join Date: Mar 2017
Location: NYC/USA
Posts: 27
More testing. I was in the studio today (where the 3000 resides) and I put the card in the real Amiga. Yeah... there's some issues. The computer boots up maybe 30% of the time. When it does, sometimes it's only the Workbench partition that mounts. That extra little partition that I added at the end of the 24GB "drive" never seems to mount. (It mounts ok on WinUAE.)

Here's the hddreport from WinUAE. Stupid me forgot to move the report from RAM: on the real Amiga (on one of the few times it booted up.) I'll see if I can get that tomorrow.

WinUAE:

Code:
--------------------------------------------------------------------------------
Report generated by HDDReport version 1.16 on Thursday, 23-Mar-17 at 20:46:12
--------------------------------------------------------------------------------

Overview:

  Drive      Volume         Capacity  Type  Boot  Device     Unit Loc.  Check
  JAZP                       1020 MB  PFS1     0  2nd.scsi    4         
  JAZPC                      1021 MB  MSD0   -20  2nd.scsi    5         
  JAZ2                       1911 MB  DOS3     0  2nd.scsi    5         
  JAZ0                       1021 MB  DOS1     0  dkbscsi     4         
  JMAC0                      1021 MB  MAC0     0  dkbscsi     4         
  JPC0                       1021 MB  MSH0     0  dkbscsi     4         
  NETPAR                     1478 GB  0000     0  netprinter  0   >128G 
  DH1        Workbench        500 MB  PFS3     0< scsi        0         
  DH1_1      Work            1547 MB  PFS3    no  scsi        0         
  DH2        Games             24 GB  PDS3    no  scsi        1   >4G   
  DH2.1                       258 MB  PDS3     0  scsi        1   >4G   
  DF0                         880 KB  DOS0     5  trackdisk   0         


System information:

  Kickstart 3.1         40.68             exec.library          40.10  
  dos.library           40.3              expansion.library     40.2   
  icon.library          46.4              graphics.library      40.24  
  intuition.library     40.85             utility.library       40.1   


Memory:

  Name                  Address      Size      Used      Free   Attributes
  expansion memory   0x07000020     16 MB   3245 KB     13 MB   PUBLIC, FAST, LOCAL, KICK
  chip memory        0x00001020   2044 KB    313 KB   1731 KB   PUBLIC, CHIP, LOCAL, 24BITDMA, KICK

--------------------------------------------------------------------------------
Report generated by HDDReport version 1.16 on Thursday, 23-Mar-17 at 20:46:12
--------------------------------------------------------------------------------

File Systems:

        DOS type    Name                           Version             Features
  MSH0  0x4D534800  CrossDOSFileSystem              42.5   (Resource)  
  MSD0  0x4D534400  CrossDOSFileSystem              42.5   (Resource)  
  PDS3  0x50445303  pfs3_aio.handler                18.5   (Resource)  TD64, NSD, SCSI
  PFS3  0x50465303  pfs3_aio.handler                18.5   (Resource)  TD64, NSD, SCSI
  DOS3  0x444F5303                                  40.1   (Resource)  
  DOS1  0x444F5301                                  40.1   (Resource)  
  MAC0  0x4D414300                                         (not found)  
  PFS1  0x50465301                                         (not found)  TD64
  0000  0x00000000                                         (not found)  
  DOS0  0x444F5300                                         (not found)  

--------------------------------------------------------------------------------
Report generated by HDDReport version 1.16 on Thursday, 23-Mar-17 at 20:46:12
--------------------------------------------------------------------------------

Exec Devices:

  adide_atapi.device              Version 120.3    (not a disk)
  ad_atapi.device                 Version 120.3    (not a disk)
  ahi.device                      Version   6.7    (not a disk)
  buddha_atapi.device             Version 120.3    (not a disk)
  clipboard.device                Version  38.8    (not a disk)
  console.device                  Version  40.2    (not a disk)
  gameport.device                 Version  40.1    (not a disk)
  input.device                    Version  40.1    (not a disk)
  keyboard.device                 Version  40.1    (not a disk)
  mfm.device                      Version  40.9    (not a disk)
  narrator.device                 Version  37.8    (not a disk)
  parallel.device                 Version  43.3    (not a disk)
  paulaaudio.device               Version   1.5    (not a disk)
  printer.device                  Version  44.39   (not a disk)
  printtofile.device              Version  44.4    (no units)
  ramdrive.device                 Version  39.35   (no units)
  serial.device                   Version  43.4    (not a disk)
  tandemat.device                 Version 120.3    (not a disk)
  tandemat_pcmcia.device          Version 120.3    (not a disk)
  tandemcd.device                 Version  41.6    (not a disk)
  tandemcd_come.device            Version  41.6    (not a disk)
  tandemcd_pcmcia.device          Version  41.6    (not a disk)
  telmexatapi.device              Version 120.3    (not a disk)
  timer.device                    Version  39.4    (not a disk)

  2nd.scsi.device       Unit   4  Error  -1  (device/unit failed to open)

  2nd.scsi.device       Unit   5  Error  -1  (device/unit failed to open)

  dkbscsi.device        Unit   4  Error  -1  (device/unit failed to open)

  netprinter.device     Unit   0  Error  -1  (device/unit failed to open)

  scsi.device           Unit   0  Version  40.12  NSD, SCSI

    TD_READ64        check failed with error -3 (command not supported by device)

    SCSI:
      Vendor       : Blatboy 
      Product      : BBHDSD2         
      Revision     : 1.0 
      BlockAddress : 4194303
      BlockLength  : 512
      Capacity     : 2048 MB

    RDSK:                                  Flags:
      Vendor       : Blatboy                 Last          = no
      Product      : BBHDSD2                 Last LUN      = yes
      Revision     : 1.0                     Last TID      = no
      Cylinders    : 4096                    Reselect      = yes
      Sectors      : 256                     Disk ID       = not valid
      Heads        : 4                       Controller ID = not valid
      CylBlocks    : 1024                    Synch         = no
      BlockBytes   : 512
      Capacity     : 2048 MB

    FSHD:
      PFS3  L:pfs3_aio-handler           Version  18.0   Size  69388 Bytes
      DOS3  L:FastFileSystem             Version  45.16  Size  26532 Bytes

  scsi.device           Unit   1  Version  40.12  NSD, SCSI

    TD_READ64        check failed with error -3 (command not supported by device)

    SCSI:
      Vendor       : Blatboy 
      Product      : BBHDSD2         
      Revision     : 1.0 
      BlockAddress : 50331647
      BlockLength  : 512
      Capacity     : 24 GB

    RDSK:                                  Flags:
      Vendor       : Blatboy                 Last          = yes
      Product      : BBHDSD2                 Last LUN      = yes
      Revision     : 1.0                     Last TID      = yes
      Cylinders    : 32768                   Reselect      = yes
      Sectors      : 256                     Disk ID       = not valid
      Heads        : 6                       Controller ID = not valid
      CylBlocks    : 1536                    Synch         = no
      BlockBytes   : 512
      Capacity     : 24 GB

    FSHD:
      PDS3  L:pfs3_aio-handler           Version  18.0   Size  69388 Bytes
      CFS0  L:pfs3_aio-handler           Version  18.0   Size  69388 Bytes
      DOS3  L:FastFileSystem             Version  45.16  Size  26532 Bytes

  trackdisk.device      Unit   0  Version  40.1   (none)

    Geometry:
      SectorSize   : 512
      TotalSectors : 1760
      Cylinders    : 80
      CylSectors   : 22
      Heads        : 2
      TrackSectors : 11
      BufMemType   : PUBLIC
      DeviceType   : Direct Access
      Flags        : REMOVABLE
      Capacity     : 880 KB

--------------------------------------------------------------------------------
Report generated by HDDReport version 1.16 on Thursday, 23-Mar-17 at 20:46:12
--------------------------------------------------------------------------------

Partitions:

  DH1:
    Device          = scsi.device          Flags:
    Unit            = 0                      Bootable = yes
    Flags           = 0                      Mount    = yes
    SectorSize      = 512
    Surfaces        = 4
    SectorsPerBlock = 2          /* 1024 bytes */
    SectorsPerTrack = 256
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 2
    HighCyl         = 1001
    Buffers         = 80
    BufMemType      = 0          /* ANY */
    MaxTransfer     = 0x0001FE00
    Mask            = 0x7FFFFFFE
    BootPri         = 0
    DosType         = 0x50465303 /* PFS3 */

  DH1_1:
    Device          = scsi.device          Flags:
    Unit            = 0                      Bootable = no
    Flags           = 0                      Mount    = yes
    SectorSize      = 512
    Surfaces        = 4
    SectorsPerBlock = 2          /* 1024 bytes */
    SectorsPerTrack = 256
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 1002
    HighCyl         = 4095
    Buffers         = 80
    BufMemType      = 0          /* ANY */
    MaxTransfer     = 0x0001FE00
    Mask            = 0x7FFFFFFE
    BootPri         = 0
    DosType         = 0x50465303 /* PFS3 */

  DH2:
    Device          = scsi.device          Flags:
    Unit            = 1                      Bootable = no
    Flags           = 0                      Mount    = yes
    SectorSize      = 512
    Surfaces        = 6
    SectorsPerBlock = 2          /* 1024 bytes */
    SectorsPerTrack = 256
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 2
    HighCyl         = 32423
    Buffers         = 80
    BufMemType      = 0          /* ANY */
    MaxTransfer     = 0x0001FE00
    Mask            = 0x7FFFFFFE
    BootPri         = 0
    DosType         = 0x50445303 /* PDS3 */

  DH2:
    Device          = scsi.device          Flags:
    Unit            = 1                      Bootable = no
    Flags           = 0                      Mount    = yes
    SectorSize      = 512
    Surfaces        = 6
    SectorsPerBlock = 2          /* 1024 bytes */
    SectorsPerTrack = 256
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 32424
    HighCyl         = 32767
    Buffers         = 80
    BufMemType      = 0          /* ANY */
    MaxTransfer     = 0x0001FE00
    Mask            = 0x7FFFFFFE
    BootPri         = 0
    DosType         = 0x50445303 /* PDS3 */

--------------------------------------------------------------------------------
Report generated by HDDReport version 1.16 on Thursday, 23-Mar-17 at 20:46:12
--------------------------------------------------------------------------------

DOS Devices:

  JAZP:
    Device          = 2nd.scsi.device
    Unit            = 4
    Flags           = 0
    SectorSize      = 512
    Surfaces        = 5
    SectorsPerBlock = 2          /* 1024 bytes */
    SectorsPerTrack = 130
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 2
    HighCyl         = 3216
    Buffers         = 512
    BufMemType      = 1          /* PUBLIC */
    MaxTransfer     = 0x7FFFFFFF
    Mask            = 0x7FFFFFFE
    BootPri         = 0
    DosType         = 0x50465301 /* PFS1 */
    Baud            = 1200
    Control         = 0

  JAZPC:
    Device          = 2nd.scsi.device
    Unit            = 5
    Flags           = 0
    SectorSize      = 512
    Surfaces        = 1
    SectorsPerBlock = 1          /* 512 bytes */
    SectorsPerTrack = 1
    Reserved        = 4
    PreAlloc        = 0
    Interleave      = 2091049
    LowCyl          = 0
    HighCyl         = 2091049
    Buffers         = 250
    BufMemType      = 1          /* PUBLIC */
    MaxTransfer     = 0x7FFFFFFF
    Mask            = 0x00FFFFFE
    BootPri         = -20
    DosType         = 0x4D534400 /* MSD0 */
    Baud            = 1200
    Control         = 0

  JAZ2:
    Device          = 2nd.scsi.device
    Unit            = 5
    Flags           = 0
    SectorSize      = 512
    Surfaces        = 1
    SectorsPerBlock = 4          /* 2048 bytes */
    SectorsPerTrack = 260
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 2
    HighCyl         = 15051
    Buffers         = 512
    BufMemType      = 1          /* PUBLIC */
    MaxTransfer     = 0x7FFFFFFF
    Mask            = 0x000FFE00
    BootPri         = 0
    DosType         = 0x444F5303 /* DOS3 */
    Baud            = 1200
    Control         = 0

  JAZ0:
    Device          = dkbscsi.device
    Unit            = 4
    Flags           = 0
    SectorSize      = 512
    Surfaces        = 2
    SectorsPerBlock = 1          /* 512 bytes */
    SectorsPerTrack = 65
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 0
    HighCyl         = 16084
    Buffers         = 512
    BufMemType      = 1          /* PUBLIC */
    MaxTransfer     = 0x7FFFFFFF
    Mask            = 0x7FFFFFFE
    BootPri         = 0
    DosType         = 0x444F5301 /* DOS1 */
    Baud            = 1200
    Control         = 0

  JMAC0:
    Device          = dkbscsi.device
    Unit            = 4
    Flags           = 0
    SectorSize      = 512
    Surfaces        = 2
    SectorsPerBlock = 1          /* 512 bytes */
    SectorsPerTrack = 65
    Reserved        = 0
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 0
    HighCyl         = 16084
    Buffers         = 5
    BufMemType      = 1          /* PUBLIC */
    MaxTransfer     = 0x00100000
    Mask            = 0x7FFFFFFE
    BootPri         = 0
    DosType         = 0x4D414300 /* MAC0 */
    Baud            = 1200
    Control         = 0

  JPC0:
    Device          = dkbscsi.device
    Unit            = 4
    Flags           = 0
    SectorSize      = 512
    Surfaces        = 2
    SectorsPerBlock = 1          /* 512 bytes */
    SectorsPerTrack = 65
    Reserved        = 1
    PreAlloc        = 0
    Interleave      = 2091049
    LowCyl          = 0
    HighCyl         = 16084
    Buffers         = 512
    BufMemType      = 1          /* PUBLIC */
    MaxTransfer     = 0x7FFFFFFF
    Mask            = 0x7FFFFFFE
    BootPri         = 0
    DosType         = 0x4D534800 /* MSH0 */
    Baud            = 1200
    Control         = 0

  NETPAR:
    Device          = netprinter.device
    Unit            = 0
    Flags           = 0
    SectorSize      = 512
    Surfaces        = 29480416
    SectorsPerBlock = 1          /* 512 bytes */
    SectorsPerTrack = 117921664
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 117628068
    HighCyl         = 0
    Buffers         = 5
    BufMemType      = 3          /* PUBLIC, CHIP */
    MaxTransfer     = 0x7FFFFFFF
    Mask            = 0xFFFFFFFE
    BootPri         = 0
    DosType         = 0x00000000 /* 0000 */
    Baud            = 0
    Control         = 0

  DH1: /* Workbench */
    Device          = scsi.device
    Unit            = 0
    Flags           = 0
    SectorSize      = 512
    Surfaces        = 4
    SectorsPerBlock = 2          /* 1024 bytes */
    SectorsPerTrack = 256
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 2
    HighCyl         = 1001
    Buffers         = 80
    BufMemType      = 0          /* ANY */
    MaxTransfer     = 0x0001FE00
    Mask            = 0x7FFFFFFE
    BootPri         = 0
    DosType         = 0x50465303 /* PFS3 */

  DH1_1: /* Work */
    Device          = scsi.device
    Unit            = 0
    Flags           = 0
    SectorSize      = 512
    Surfaces        = 4
    SectorsPerBlock = 2          /* 1024 bytes */
    SectorsPerTrack = 256
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 1002
    HighCyl         = 4095
    Buffers         = 80
    BufMemType      = 0          /* ANY */
    MaxTransfer     = 0x0001FE00
    Mask            = 0x7FFFFFFE
    BootPri         = 0
    DosType         = 0x50465303 /* PFS3 */

  DH2: /* Games */
    Device          = scsi.device
    Unit            = 1
    Flags           = 0
    SectorSize      = 512
    Surfaces        = 6
    SectorsPerBlock = 2          /* 1024 bytes */
    SectorsPerTrack = 256
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 2
    HighCyl         = 32423
    Buffers         = 600
    BufMemType      = 0          /* ANY */
    MaxTransfer     = 0x0001FE00
    Mask            = 0x7FFFFFFE
    BootPri         = 0
    DosType         = 0x50445303 /* PDS3 */

  DH2.1:
    Device          = scsi.device
    Unit            = 1
    Flags           = 0
    SectorSize      = 512
    Surfaces        = 6
    SectorsPerBlock = 2          /* 1024 bytes */
    SectorsPerTrack = 256
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 32424
    HighCyl         = 32767
    Buffers         = 80
    BufMemType      = 0          /* ANY */
    MaxTransfer     = 0x0001FE00
    Mask            = 0x7FFFFFFE
    BootPri         = 0
    DosType         = 0x50445303 /* PDS3 */

  DF0:
    Device          = trackdisk.device
    Unit            = 0
    Flags           = 0
    SectorSize      = 512
    Surfaces        = 2
    SectorsPerBlock = 1          /* 512 bytes */
    SectorsPerTrack = 11
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 0
    HighCyl         = 79
    Buffers         = 5
    BufMemType      = 1          /* PUBLIC */
    MaxTransfer     = 0x00200000
    Mask            = 0x7FFFFFFE
    BootPri         = 5
    DosType         = 0x444F5300 /* DOS0 */
    Baud            = 0
    Control         = 0

--------------------------------------------------------------------------------
End of report
--------------------------------------------------------------------------------
One thing that's interesting is that it reports that HD2.1, which is 258MB, is greater than 4GB... (that's the drive that won't boot on the real amiga, assuming the card boots up the computer at all)

I'll do more testing on WinUAE tonight. Might see if I can set up a V5 card and see how that goes. I have both... After I've exhausted that testing, I'll probably contact the creator of the card...

Last edited by blatboy; 25 March 2017 at 05:39.
blatboy is offline  
Old 28 March 2017, 21:49   #346
blatboy
"The Lurker"

blatboy's Avatar
 
Join Date: Mar 2017
Location: NYC/USA
Posts: 27
I decided to start from scratch on a new 8GB card.

DH1: 2GB
DH2: 5.5GB

Set everything up with PDS/03 etc. Everything seemed fine. Hddreport gave it an OK for >4GB. This time I didn't even get the message "PFS Doctor failed to access the disk above the 4G boundary... " when I checked the drive with pfsdoctor.

However, the error came up again when I was copying games...



Once I clicked on OK, I got a guru. Reboot... and DH2: is now "NDOS" Same thing that happened with the 32GB card.

This time the error occurred at the point DH2: was around 2.3GB full. That's not 4GB. Hmm. Of course HD1: is 2GB, so maybe it's treating it all as one big HD? Perhaps I'll try it again and just create drives less than 4GB. If I still get the error, it would seem to be some sort of issue with the SCSI2SD, and not some sort of issue with how I set up the Amiga.

Also note that the first time I tried to copy the games by just selecting all and moving the whole shebang over, it slowed to a crawl when got to the D games. This has happened a few times before, when I was trying to set this up in the last couple weeks. In the past, it worked better when I copied a smaller amount of files at a time. I stopped it (after letting it run all night) and deleted the D games. I set it to copy D-H. All good. Then rebooted and copied I-L. All good. Rebooted and copied M-Q. That's when the error occurred.

I have heard from the creator of SCSI2SD. He sent me new firmware to try. I'll give that a go too.

In the end, if I have to stick to drives that are <4GB, it won't be the end of the world. I just want a working setup so I can start using and enjoying my Amiga.
blatboy is offline  
Old 28 March 2017, 23:32   #347
thomas
Registered User
thomas's Avatar
 
Join Date: Jan 2002
Location: Germany
Posts: 5,543
Quote:
Originally Posted by blatboy View Post
maybe it's treating it all as one big HD?
Sure it does. The 4 GB limit applies to the whole harddrive, not to single partitions.
thomas is offline  
Old 28 March 2017, 23:37   #348
blatboy
"The Lurker"

blatboy's Avatar
 
Join Date: Mar 2017
Location: NYC/USA
Posts: 27
In theory, it shouldn't. The SCSI2SD allows you to set up multiple drives on one SD card, giving each of them an individual SCSI ID. I set up two drives... DH1: and DH2: with scsi IDs 0 and 1. I have two partitions on the 2GB DH1: (Workbench and Work). One partition on DH2: which is 5.5GB.

I'm trying one more time with the new firmware...

Last edited by blatboy; 28 March 2017 at 23:39. Reason: clarity
blatboy is offline  
Old 28 March 2017, 23:46   #349
blatboy
"The Lurker"

blatboy's Avatar
 
Join Date: Mar 2017
Location: NYC/USA
Posts: 27
Although, one thing I hadn't thought of trying was just to make it one big 8GB hard drive with multiple partitions. Maybe the Amiga will like that better? Worth a shot.
blatboy is offline  
Old 29 March 2017, 15:37   #350
blatboy
"The Lurker"

blatboy's Avatar
 
Join Date: Mar 2017
Location: NYC/USA
Posts: 27
Two more tests, and I get the same basic behavior.

I updated the firmware, and tried again with the same setup as last time. I got the error. This time it was at close to the 4GB mark within DH2:

I started over with the 8GB SD card. I set it up as one drive and three partitions. I got the error at almost the exact 4GB moment this time, on the third partition.

I think I'm just going to live with <4GB drives/partitions for now on the a3000, just so I can go on and use it. I don't like splitting up the games into multiple partitions, but it's not the end of the world.

I will be setting up my a1200 with a CF card. I'll probably use a win 3.1 ClassicWB setup as it's a pretty standard a1200. I know the setup will be different on that one (I will need to use a different scsi.device from the stock, for one thing...) If I run into a similar problem, I'll know it wasn't the SCSI2SD that was the issue, but perhaps a PEBKAC.

My gut feeling is that the issue isn't with the SCSI2SD. I could be way off base with this feeling. The issues I was having with the card mounting on the real machine makes sense to me that it's the SCSI2SD. These HD setup issues don't feel the same, mostly because they also happen on the emulator.

I will also further discuss the issue with the creator of the card.

Thanks for all your help. I'll keep updating you on the situation. (I'm sure you're thrilled hahah!)

Last edited by blatboy; 29 March 2017 at 15:46.
blatboy is offline  
Old 29 March 2017, 15:50   #351
blatboy
"The Lurker"

blatboy's Avatar
 
Join Date: Mar 2017
Location: NYC/USA
Posts: 27
Another thought:

I've just been using the stock format command (using the "format disk..." from the menu in WB) to format these drives. That's not a problem, right? I do get a window popping up that states it's PFS that's being used, so I've been assuming that was correct.

Thanks
blatboy is offline  
Old 30 March 2017, 08:33   #352
Jope
-
Jope's Avatar
 
Join Date: Jul 2003
Location: Helsinki / Finland
Age: 37
Posts: 6,319
Send a message via Skype™ to Jope
Always quick format! I hope you had selected that.
Jope is offline  
Old 05 April 2017, 13:17   #353
DaMi
Registered User
DaMi's Avatar
 
Join Date: Feb 2006
Location: Prague/The Czech Republic
Age: 43
Posts: 17
Send a message via Skype™ to DaMi
Hello, I would like to ask: if I intended to create a large drive in WinUAE using PFS\3 (or PDS\3) and uaehf.device (let's say 30 - 50 GB), I should not run in any troubles? The 4.3 or 7.87 limit is related only to scsi.device and FFS? Let's say, I would like to use this disk with OS3.5 or OS3.9 only for use in WinUAE.

Last edited by DaMi; 05 April 2017 at 15:46.
DaMi is offline  
Old 05 April 2017, 14:44   #354
Jope
-
Jope's Avatar
 
Join Date: Jul 2003
Location: Helsinki / Finland
Age: 37
Posts: 6,319
Send a message via Skype™ to Jope
If it is only uaehf.device, you will not run into troubles if you use a large disk capable FS such as SFS or PFS3.
Jope is offline  
Old 05 April 2017, 16:46   #355
blatboy
"The Lurker"

blatboy's Avatar
 
Join Date: Mar 2017
Location: NYC/USA
Posts: 27
Well, I finally have some good news to post. In my piles of junk, er, important gear, I forgot that I do indeed own an Addonics SCSI to IDE interface. Since I have an IDE to CF interface that I was saving for my 1200, this could be a viable option for the 3000 I'm trying to set up.

I couldn't find my 50 to 68 pin SCSI adapter, so I won't be able to test it on the real machine until I find it or until the new one I ordered comes in.

However, that didn't stop me from trying to set up a 32GB CF card in WinUAE. I set it up with PFS. And... all of the games copied over swimmingly onto a 20GB partition. Well... now I feel I know for sure that my issues with >4GB drives was a problem with the SCSI2SD card, and not my ability to set up a large HD in 3.9.

I don't want to jinx anything... and I hope I'm not speaking too soon... but I feel like I'm on the way to having a working, tricked out, fully loaded 3000/040 that I can enjoy. I'll keep you posted once I test this sucker in the real machine. Thanks again for all the help.

Last edited by blatboy; 05 April 2017 at 17:05.
blatboy is offline  
Old 05 April 2017, 16:59   #356
blatboy
"The Lurker"

blatboy's Avatar
 
Join Date: Mar 2017
Location: NYC/USA
Posts: 27
And murtherfore, now that I'm confident that I wasn't the problem haha, I will be bringing this up with the creator of the SCSI2SD card to be sure he knows about the issue(s). I still plan on trying one of them on one of my 68K Macintoshes. If this CF card works on the 3000, I'll probably get rid of the extra SCSI2SD cards I own... I've not run into a lot of people that seemed to have gotten a SCSI2SD working smoothly on an Amiga (esp the 3000). It seems like such a good option. Oh well. Sorry to drift OT. (Although I've been getting the feeling that perhaps I should have used a separate thread for my entire issue? Sorry if this wasn't the right place.)

Last edited by blatboy; 05 April 2017 at 17:11.
blatboy is offline  
Old 14 May 2017, 04:06   #357
AC/DC HACKER!
Registered User

 
Join Date: Aug 2016
Location: USA
Posts: 33
Quote:
Originally Posted by blatboy View Post
I decided to start from scratch on a new 8GB card.

DH1: 2GB
DH2: 5.5GB

Set everything up with PDS/03 etc. Everything seemed fine. Hddreport gave it an OK for >4GB. This time I didn't even get the message "PFS Doctor failed to access the disk above the 4G boundary... " when I checked the drive with pfsdoctor.

However, the error came up again when I was copying games...



Once I clicked on OK, I got a guru. Reboot... and DH2: is now "NDOS" Same thing that happened with the 32GB card.

This time the error occurred at the point DH2: was around 2.3GB full. That's not 4GB. Hmm. Of course HD1: is 2GB, so maybe it's treating it all as one big HD? Perhaps I'll try it again and just create drives less than 4GB. If I still get the error, it would seem to be some sort of issue with the SCSI2SD, and not some sort of issue with how I set up the Amiga.

Also note that the first time I tried to copy the games by just selecting all and moving the whole shebang over, it slowed to a crawl when got to the D games. This has happened a few times before, when I was trying to set this up in the last couple weeks. In the past, it worked better when I copied a smaller amount of files at a time. I stopped it (after letting it run all night) and deleted the D games. I set it to copy D-H. All good. Then rebooted and copied I-L. All good. Rebooted and copied M-Q. That's when the error occurred.

I have heard from the creator of SCSI2SD. He sent me new firmware to try. I'll give that a go too.

In the end, if I have to stick to drives that are <4GB, it won't be the end of the world. I just want a working setup so I can start using and enjoying my Amiga.
I use a 32GB SDCard with my SCSI2SD 5.0a and CompactFlash connected to IDE. So my Amiga is able to boot from CSPPC's SCSI or Amiga 4000's IDE. Here's the rub..

I use Amiga OS 3.5, and 3.9. To access larger partitions correctly SetPatch (currently 44.16) must be run. If it is not, then past 4GB won't be noticed and you'll be prompted by AmigaDOS to insert. I have 3 Partitions before the 4GB limit with FFS and several after. This way OS 3.5, 3.9 and Amiga OS 4.1 are accessible without SetPatch, once SetPatch is run I'm able to access a Partition for archives near the end of the 32GB, actually 29GB CompactFlash. With or AmigaDOS or Workbench. I also use SFS, but again, SetPatch has to be run AND 01FE00 for MaxTranfer must be set, or AmigaDOS will give transfer errors, especially with Directory Open 5.
Once SetPatch is run, my Amiga 4000 is also able to boot on a further partition OS 3.9 that I'm testing. It's around 15GB from the start of the CF and is 800MB. Anyway, hope that helps. :-)
AC/DC HACKER! is offline  
Old 14 May 2017, 15:57   #358
idrougge
Registered User
 
Join Date: Sep 2007
Location: Stockholm
Posts: 3,050
Quote:
Originally Posted by fgh View Post
But check4gb does not know pfs3aio and is therefore obsolete. Use hddreport instead.
Why would it need to know about the file system? No other program knows about your file system and files will have errors because they use the file system as intended.
idrougge is online now  
Old 19 May 2017, 13:09   #359
fgh
Registered User
 
Join Date: Dec 2010
Location: Norway
Posts: 585
Quote:
Originally Posted by idrougge View Post
Why would it need to know about the file system? No other program knows about your file system and files will have errors because they use the file system as intended.
The very purpose of the check4gb program is to check a system's drivers and file systems to help users confirm they have a >4GB proof setup.
I don't know its inner workings, but it did give incorrect reports for PFS3AiO, and it was Thomas himself who said Check4GB was obsolete and to use hddreport instead on EAB earlier.

I see a new version 1.6 of Check4GB is out, which according to the readme has fixed TD64 and HD_SCSICMD tests, so I suppose it might not be obsolete any more though
fgh is offline  
Old 19 May 2017, 17:24   #360
idrougge
Registered User
 
Join Date: Sep 2007
Location: Stockholm
Posts: 3,050
Sorry, I was confusing Check4GB with another of Thomas's programs which tests maxtransfer.
idrougge is online now  
AdSense AdSense  
 


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Similar Threads
Thread Thread Starter Forum Replies Last Post
Large Hard-Drives (over 4gb) keitha1200 support.Hardware 4 20 April 2012 09:09
GVP 4.15 Roms & Large Hard drives... Info-Seeker support.Hardware 21 09 August 2010 13:06
What sort of Filemaster to use with large drives? Ebster support.Apps 4 08 February 2009 18:53
replacing amiga floppy drives with hard drives Gordon support.Hardware 2 06 March 2007 01:44
Large hard drives and WB3.0... darkwave support.Hardware 3 05 July 2004 04:19

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 13:05.


Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.
Page generated in 0.38891 seconds with 15 queries