In WinUAE I set up an A4000 emulation ClassicWB - WB3.1 - with SFS filesystem on an 8GB Transcend 600x CF card to use on a real A4000 3.0 ROMs with a WarpEngine 4040 and IDE to CF adapter that has worked great with numerous CF cards of all sizes, including the same 8 gigger with a different setup.

I partitioned the CF card with a 400 meg WB partition and a 7245 meg partition loaded with 3,000 WHDLoad games. Both partitions are using SFS 1.279 as the filesystem. It all works great in WinUAE, but on the real A4000 the Games partition never mounts even though it is visible in both HDToolbox and HDInstTools. I also tried it WarpKicking 3.1 roms with the same results.

Does anyone have any ideas on what I could be missing?

Henry

Last edited by JHenry on 16-Aug-2021 at 07:17 AM.

@JHenry

Is this partition set to automount?


If you don´t find right answer here, you may also try eab.abime.net, where many experienced classic users are regulars.

Quote:

Does anyone have any ideas on what I could be missing?

Drivers for >4GB on the IDE bus. SFS only works if either TD64 or NSD64 is supported by the harddrive driver.

_________________
Email: thomas-rapp@web.de
Home: thomas-rapp.homepage.t-online.de

@pavlor @thomas

Yes, the partition is set to automount.

I created a mountlist for it in UAE and set it to not automount and was able to manually mount it and it performed normally. Boy it's been literally decades since I created a mountlist entry!

I moved the 8 gig CF to the real A4000 and it doesn't show up (of course) and I am unable to use t after mounting it manually in a shell. I get: "DH1:: not enough memory available" when I try to CD to it. It has 2 meg of chip and 64 meg of WarpEngine fast. It doesn't use up any of that memory. If I try to mount DH1 a second time it says it is already mounted. I could raid my Cyberstorm II 060 board for its 128 megs, but I'm pretty sure it will still say "not enough memory". SysInfo shows and will test DH0 (400MB also SFS), but DH1 doesn't show up. The command "info dh2:" just returns with no data or error.

Workbench thinks it is mounted, but won't allow access to it so I may be able to coax it out somehow. I'll have to keep beating on it.

Oh yeah, I was able to warpkick a 32 GB CF of a 3.2 install with "BestClassicWB" 2.0 set up with a 400MB WB partition, an 8GB FastFilesystem partition (with the WHDLoad games) and a 10 GB SFS partition. So the mobo IDE controller can be used for >4GB partitions.

@thomas what specifically do you mean by "the harddrive driver"?

Henry

I loadmodule'd scsi.device 44.2 before setpatch and 3.1 sees the 7.4GB partition and mounts it fine now.

I was under the impression that I didn't need a patched scsi.device if the disk/partition was 8GB or less. This appears to not be the case, at least with WB 3.1.

Now for some extended Amiga gaming, er testing time! It's been years since I played Amiga games other Populous for more than a few minutes.

It's nice having a well running A4000 with a flicker fixer that I haven't even recapped yet. I did replace C200, 4.7uF, 2nd closest to the Vartabarf battery (replaced with a 2032 coin cell), but C192 right next to it is ok for now. I do have a full recap kit and will get to it in the near future.

Now if I could just find my darned CV64 3D vid card. I can't believe I didn't keep it with my A4000s. I'm still missing that card and the CyberSCSI module that goes on the CS MkII. I have the external port board and cable for it and even the box for it, but not the board itself.

Thanks for the suggestions,

Henry

Quote:

I was under the impression that I didn't need a patched scsi.device if the disk/partition was 8GB or less. This appears to not be the case, at least with WB 3.1.

In your case not WB is the limiting factor but SFS. If you'd use PFS3 for example, you could access up to 8063 MB without a patch for scsi.device. That's still a little less than 8 GB (8192 MB), though.

_________________
Email: thomas-rapp@web.de
Home: thomas-rapp.homepage.t-online.de