AMOSPro problem on real A1200
 

Hey,

put Amos Pro on my real A1200. Via WinUAE, same specs, A1200 sporting a
Blizzard 1230IV 030/50. Upon installation, it quits like "not enough space on work:" -- Guess that's because my partition got 3.5 GB and the installer thinks wtf?!
Whatever, copied the stuff by hand and ran it ok under UAE. On the real thing, however, it boots up, showing "AMOS Professional Version 2.00," blah,
and freezes. Pointer in the upper right corner, frozen, totally.
Yeah, will try to install it on DH0: (~500MB) and see if it likes that more. But will take some time, plugging the card back into the PC...Weekends are for the family...:: yawns ::
Any clues meanwhile?

By the way, how much HD partitions can the A1200 handle? Space is running out on my 4GB card. Thinking about a 16GB one.

The problems with the AmosPro installer include the fact that any destination partition with more than 2 gigs free is interpreted as having negative free space.

By the way, check if there is a file in S: in the source drive for the AmosPro configuration.

Yeah, compiler and interpreter config are in S:

But what puzzles me is that it runs on WinUAE and refuses to do on the real deal.

Condition is not simply >2G. if remainder is >=2G after size is divided by 4G: negative free size. (2G to 4G, 6G to 8G and so on)

Interesting. But what does it have to do with WinUAE and the real one?

That was only possible proper answer, the only other answer is "not enough information".

Understood, Master. Please enlighten me.

It's "as is."
The A1200 and the UAE conditions meet. Even have the ROM image of the Blizzard-card plugged in (although Scalos says "020" instead of "030").

As I mentioned, your explanation of the sizes is interesting, but not everyone is a coding crack like you :p If you ask for more info, well, which one do you need?

Would it help if I try by installing it regularly on DH0:? That's roughly 500MB.

Do that.

Okie.
Thanks.

I'll let you know. May need some time...

Do you use exact same drive? Attach config file. Do you have exact same memory setup? (not just same amount of ram, it is not same)

Sorry for the late reply.
RL doesn't fancy real Amigas sometimes... :p
In the meantime I have replaced the 4Gb card with a 16 GB SD. 500 MB on DH0: and DH1: got the rest. AMOS works flawlessly on DH0: now.
Thanks to you both!

But...what puzzles me - and this goes out to Toni - is that DH1: reports some 2.7GB. Nothing more, nothing less. I'm aware that it is dizzy, the whole thing. And there must be more space. Since I'm currently unpacking a WHDLoad-Games-Archive which exceeds the current shown space by far.
I'm sporting PS3 and scsi.device 44.2.

Unpacking on Amiga, not PC? Yeah, the difference between 3.4Ghz and 50Mhz is just illusionary... :)

It's an overflow error; the drive size is reported as a 32-bit longword, which can only represent as much as 4 GB. So the size goes to 4 GB, then 0 GB, then some more, until it reaches 4 GB again, rinse and repeat.

You can try this visually in HDToolbox by moving the partition size marker slowly from 0 MB to the end of the drive.