AMOSPro problem on real A1200

Torqual · 04 March 2017, 10:35

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.

Samurai_Crow · 04 March 2017, 10:40

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.

Torqual · 04 March 2017, 10:48

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.

Toni Wilen · 04 March 2017, 11:53

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)

Torqual · 04 March 2017, 12:16

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

Toni Wilen · 04 March 2017, 12:43

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

Torqual · 04 March 2017, 12:46

Understood, Master. Please enlighten me.

Torqual · 04 March 2017, 12:51

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

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.

idrougge · 04 March 2017, 14:00

Do that.

Torqual · 04 March 2017, 14:01

Okie.
Thanks.

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

Toni Wilen · 04 March 2017, 14:03

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)

Torqual · 28 April 2017, 22:32

Sorry for the late reply.
RL doesn't fancy real Amigas sometimes...

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...

idrougge · 07 May 2017, 04:36

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.

04 March 2017, 10:35	#1
Torqual Registered User Join Date: Feb 2017 Location: Germany Posts: 27	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.

04 March 2017, 10:48	#3
Torqual Registered User Join Date: Feb 2017 Location: Germany Posts: 27	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. Last edited by Torqual; 04 March 2017 at 11:07.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Forgotten extension in AmosPro	Goldrunner	support.Apps	2	04 September 2013 14:44
AMOSPro Source	Retro1234	Coders. AMOS	4	09 December 2012 02:28
AMOSpro install A4000	frl9lk	support.Apps	1	28 October 2008 15:48
Problem to installand run Micropoose games on my real A1200	retrogamer	support.Games	3	17 February 2007 17:43
Problem using .HDF files on real A1200	Magno Boots	support.Games	2	29 January 2007 22:04

04 March 2017, 10:40	#2
Samurai_Crow Total Chaos forever! Join Date: Aug 2007 Location: Waterville, MN, USA Age: 49 Posts: 2,186	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.

04 March 2017, 11:53	#4
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,502	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)

04 March 2017, 12:16	#5
Torqual Registered User Join Date: Feb 2017 Location: Germany Posts: 27	Interesting. But what does it have to do with WinUAE and the real one?

04 March 2017, 12:43	#6
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,502	That was only possible proper answer, the only other answer is "not enough information".

04 March 2017, 12:46	#7
Torqual Registered User Join Date: Feb 2017 Location: Germany Posts: 27	Understood, Master. Please enlighten me.

04 March 2017, 12:51	#8
Torqual Registered User Join Date: Feb 2017 Location: Germany Posts: 27	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 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.

04 March 2017, 14:00	#9
idrougge Registered User Join Date: Sep 2007 Location: Stockholm Posts: 4,332	Do that.

04 March 2017, 14:01	#10
Torqual Registered User Join Date: Feb 2017 Location: Germany Posts: 27	Okie. Thanks. I'll let you know. May need some time...

04 March 2017, 14:03	#11
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,502	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)

28 April 2017, 22:32	#12
Torqual Registered User Join Date: Feb 2017 Location: Germany Posts: 27	Sorry for the late reply. RL doesn't fancy real Amigas sometimes... 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...

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

07 May 2017, 04:36	#13
idrougge Registered User Join Date: Sep 2007 Location: Stockholm Posts: 4,332	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.