AMOS HD Install problems

[Amiga600Driver]

I have a A600 with 2mb and a 4GB hard Card installed - I cannot get AMOS (1.2) HD installation to work from the Shell. AMOS Install.AMOS command is not valid. If I boot from the AMOS disk AMOS will start and I then ran the install.AMOS which starts (blue stripes across screen) and when I click the install button the screen clears to blue stripes and hangs. Any idea what may be happening here? Thanks

[Samurai_Crow]

If you have more than 2 GB free it won't install anyway. I suspect that the permissions are screwed up on one of your files so the executable bit isn't set but it uses a 32-bit signed integer to measure the amount of free disk space on your hard drive partition because it comes from an era when hard drives were never bigger than 100 MB.

Edit-- try this link:
http://amos-professional-aga.frederic-cordier.fr/

[Amiga600Driver]

Thanks

[Dradd]

I've just seen this thread, and have had the same problems on my A1200. So without wishing to sound stupid, are we saying there is no way to get AMOS installed on a CF/HD at all?
I accept that the installer for AMOS came from a day when HDs were tiny, but is there no workaround for this?

What about AMOS Pro?

Thanks in advance.

[Samurai_Crow]

@Dradd

AmosPro not only has the bug with the installer but has a copy-protection scheme. On the Amos Factory forum we were going to fix the bugs first and remove the copy protection before adding features. That didn't work out. Freddix started over from another person's attempt at fixing the bugs and has made much more headway. If there's a .hdf file at the link above, try to use it. AmosPro Unity supports AGA and is soon about to get SAGA support for the Vampire.

[Dradd]

Ah I see. Thanks for explaining that.

Originally Posted by Samurai_Crow

@Dradd

AmosPro not only has the bug with the installer but has a copy-protection scheme. On the Amos Factory forum we were going to fix the bugs first and remove the copy protection before adding features. That didn't work out. Freddix started over from another person's attempt at fixing the bugs and has made much more headway. If there's a .hdf file at the link above, try to use it. AmosPro Unity supports AGA and is soon about to get SAGA support for the Vampire.

[Psiq]

I installed AMOS Pro onto my CF card. I run the same HD image in WinUAE as I do on my A1200.

If you watch the following video, you can see me running AMOS from my HD. Its about 7 minutes into the video

[ Show youtube player ]

Matt

[Retro1234]

Originally Posted by Samurai_Crow

@Dradd

AmosPro not only has the bug with the installer but has a copy-protection scheme. On the Amos Factory forum we were going to fix the bugs first and remove the copy protection before adding features. That didn't work out. Freddix started over from another person's attempt at fixing the bugs and has made much more headway. If there's a .hdf file at the link above, try to use it. AmosPro Unity supports AGA and is soon about to get SAGA support for the Vampire.

What kind of copy-protection?
iirc I just copied the disk to a folder on the HD.

[Samurai_Crow]

The copy protection couldn't be written from an .ADF file. Original disks could be run from an Amiga but not an emulator, likewise freeware .ADF files couldn't be installed to a real Amiga without first being installed to a .HDF file.

[Retro1234]

I probably used a cracked copy later and originally coverdisks.

[Exodous]

For AMOS Pro to be considered "registered", the registration code and name need to be encoded and written into the application. Once this has happened, the files can be copied or moved anywhere, there is no "copy protection" as such.


The registration information is encrypted and is physically stored in the AMOSPro application file immediately following the null terminator character after the first instance of "dos.library". I'll refer to this as "REGSTART".

For the serial number, the first word at REGSTART is the length of the registration number and subsequent bytes (REGSTART+2 to REGSTART+2+length) are the encrypted data XOR'ed with 0x73. The default in hex is 00 00 21 36 34 3A 20 21 32 27 3A 3C 3D 53 50, which decodes to a length of 0 and "REGISTRATION #"

For the username, this is truncated to 32 characters. The first word at REGSTART+16 is the length of the username and subsequent bytes (REGSTART+18 to REGSTART+18+length) are the encrypted data XOR'ed with 0x5A. The default in hex is 00 00 EB CA D1 85 EC CB D6 D1 C4 C9 C9 C0 C1 84 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00, which decodes to a length of 0 and "Not Installed!"


A fresh AMOS Pro disk image that has never been registered will have:

• The word at REGSTART set to 0x0000
  
• The word at REGSTART+18 set to 0x0000
  
• The serial number (a number >10000) located as a long word (4 bytes) on track 0 offset 384 (ADF offset 384 = 0x182)
  
• The same serial number as a 12 byte null terminated string on track 80 offset 482, immediately after the disk name "AMOSPro_System" (ADF offset 451007 = 0x6E1BF)

  * Note, if the disk name is not "AMOSPro_System", this offset could be slightly different.

When you first run the AMOS Pro installer, if the registration code length in the executable at offset REGSTART is 0x0000, then the installer prompts you for the registration information. It reads the serial number from both disk locations and they must match. If not, it fails the registration process.

To make the registration number, it uses the first three letters of your surname, in upper case, followed by the text representation of the registration number from the disk, for example "JON12345", this is then encrypted, along with the username as detailed above and written into the main AMOSPro application file.