Notes |
|
(0011507)
|
Wepl
|
2022-06-29 21:44
|
|
Hello, kudos for your work!
I can probably adapt the install for the latest main binary. But how often will this change, because for every new version another update is going to be required.
Another issue I see is that all the changes to other files cannot be reflected in a good way. So it may only be useful for people who can build their own installation. |
|
|
|
At best the executables need no more changes. Of course there might be some code bugs but in general I rewrote the files so that most data is now external. There is still one bug I want to fix.
Maybe you can tell me what you have changed, so I can fix it by myself?
Someone said that you also fixed some issues that occur in the original on some systems.
Thanks for your work! |
|
|
(0011655)
|
Wepl
|
2022-08-04 23:27
|
|
Can you tell me which part of the github repo can be used to update an installed (whdload) ambermoon installation? |
|
|
|
|
|
|
|
|
(0011662)
|
Hexaae
|
2022-08-07 14:15
|
|
|
|
|
Thanks Pascal. Hi Hexaae. ;)
Version 1.16 (linked above by Pascal) should be very stable regarding changes to the executables. |
|
|
(0011664)
|
Hexaae
|
2022-08-07 17:35
|
|
I'm currently using Ambermoon WHDLoad with latest 1.16 fixes, after manually hex-editing the AM2_CPU file as described here: https://github.com/Pyrdacor/Ambermoon/issues/22
Why still using WHDLoad version? Because of weird mem allocations of this game that can give some strange errors (crashes or "Out of memory" warnings) on real or WinUAE. I remember I experienced these random problems even on my real A1200+Blizzard1260 and 128MB FAST...
Try for example with WinUAE using 060 and 8MB CHIPRAM, 256MB FAST, and you'll see the game will use chipmem only for the game (?). Yes it's not exactly "real world" situation with real HW, but it's annoying and having "Out of memory" errors is a nonsense on such a system.
That's why I prefer the WHDLoad version, where the whole system env is "emulated" as it should and never had memory issues.
So, a new WHDLoad installer finally also compatible with new AM2_CPU would be great IMHO. |
|
|
(0011668)
|
Wepl
|
2022-08-08 00:11
|
|
|
|
(0011669)
|
Hexaae
|
2022-08-08 01:26
|
|
Tested with my manually hex-edited (actually 1.14 manually upgraded to 1.16) files; base 1.07 Eng; current 1.16 with the new AM2_CPU exe, and the game always launched correctly. Didn't play enough but everything seems to work as expected with all versions! |
|
|
|
I am a bit confused. Why is it necessary to add the fix manually when 1.16 already contain it? Moreover this isn't the only code fix between 1.07 and 1.16. There are several of them. |
|
|
|
@Welp
Hi,
Your latest Slave works perfectly on my A500 ACA500PLUS.
It was tested with English version 1.16 (extracted Files).
Best regards,
Pascal. |
|
|
(0011673)
|
Wepl
|
2022-08-09 22:23
|
|
|
|
(0011678)
|
Hexaae
|
2022-08-10 00:04
|
|
Something is broken in public release version: game crashes calling eagle and/or black screen at launch using current 1.16 files from GitHub.
I usa an Italian Workbench (I've seen you fixed the keyboard layout...).
Latest beta was working fine. |
|
|
(0011679)
|
Hexaae
|
2022-08-10 00:13
|
|
Never mind: solved. It was a mismatching "Saves" file. Ignore last message. |
|
|
|
Great job! Thanks! Couldn't test this yet. Can you also update the project page please? |
|
|
(0011682)
|
Wepl
|
2022-08-10 11:58
|
|
Which project page do you mean? |
|
|
|
The WHDLoad Ambermoon page. For me it only shows the changelog up to install version 2.0 from 2018. And also states that the most recent version is from 2018. |
|
|
(0011689)
|
Wepl
|
2022-08-11 12:21
|
|
Please reload. It is updated. |
|
|
|
|
|
(0011692)
|
Hexaae
|
2022-08-11 14:27
|
|
@Wepl
Got this message playing a bit from a savegame: https://i.ibb.co/mBN8wtP/image.png
when I try to open the map in Godsbane castle :(
What I did:
- tested 25-30 mount/dismount from Giant Eagle
- then flyed to Castle Godbsane in the swamp
- entered and went through teleporter to the room with the bed/altar (can't remeber what it was)
- every time I try to open the local Map I get the error above or similar because of low memory. |
|
|
(0011693)
|
Hexaae
|
2022-08-11 14:29
|
|
|
|
(0011694)
|
Hexaae
|
2022-08-11 15:09
|
|
|
|
(0011697)
|
Hexaae
|
2022-08-11 15:28
|
|
@Pyrdacor
Running the game without WHDLoad won't cause low-mem warning on first launch.
But if you quit the game and RELAUNCH IT AGAIN (try more than once please), for some reasons the game will complain it has not enough free mem (chip has 150Kb left for a moment, after the game returns to WB) to load savegames... |
|
|
(0011700)
|
Hexaae
|
2022-08-11 15:54
|
|
@Pyrdacor
That's why I always preferred the WHDLoad version, as we discussed before...
I had the same mem problem on my real A1200 + B1260 66MHz + 128 RAM as far as I can remember.
YouTube video: https://www.youtube.com/watch?v=hJLu5WPdapM
(The WB requester on quit says "RamDisk is full") |
|
|
(0011703)
|
Wepl
|
2022-08-11 22:56
|
|
You used 1.16?
I have not deeply investigated the memory management of the game but it looks suboptimal to me. When running under WHDLoad any file caching of it should be disabled.
To reduce any switches on saving the used kickemu uses a large IOCACHE. Combined with memory fragmentation it could cause this I think.
But are 25-30 mount/dismount from Giant Eagle are valid use case? |
|
|
(0011704)
|
Hexaae
|
2022-08-12 03:59
|
|
Yep 1.16.
No ignore the Giant Eagle thing (it's been fixed): you can just download and use my savegame (above OneDrive link) inside Castle Godsbane for a quick check. When you try to open the map in the castle you should see a memory warning. |
|
|
(0011708)
|
Hexaae
|
2022-08-13 23:47
|
|
FYI, I just hacked the SLAVE with an hex-editor increasing chip-mem, and got no more complaints in the game. |
|
|
(0011712)
|
Wepl
|
2022-08-16 10:40
|
|
To which value do you have increased it? |
|
|
(0011713)
|
Hexaae
|
2022-08-16 12:14
|
|
If you want to add a beta with $100000 chipmem I'll test it now. |
|
|
(0011717)
|
Hexaae
|
2022-08-16 16:16
|
|
Or maybe just 250Kb more will be enough... If you compile different versions I'll test and see if the low-mem warning appear again. |
|
|
(0011719)
|
Hexaae
|
2022-08-16 23:08
|
|
This seems to be enough:
WHDInfo v1.31 (03.08.2008) by Codetapper, Wepl
Ambermoon (c) 1993 Thalion
adapted by Harry/Wepl
Version 2.1 (09.08.2022)
Slave name: Ambermoon_hack.slave
Slave size: 6716 bytes
WHDLoad Version: 18
Flags: $2406 (9222)
All errors quit WHDLoad
Traps are emulated like autovectors
Forward "privilege violation" exceptions to handler
Uses resload_Examine/ExNext
Base memory: $a0000 (640 KB)
Fake Exec installed: None
Game Loader: $34 ($54 bytes from start of file)
Subdir for files: 'data'
Caching: All files
Debug key: None
Exit key: F10
Expansion memory: $130000 (1216 KB)
Kickstart name: '34005.a500'
Kickstart size: $40000 (256 KB)
Kickstart crc: $f9e3
Information: Slave requires kickstart 1.3 image! |
|
|
(0011720)
|
Wepl
|
2022-08-16 23:41
|
|
The problem is, that then the game will not work with 512k chip only anymore.
Better would probably to fix the memory manangement and give more expmem. |
|
|
(0011721)
|
Hexaae
|
2022-08-17 10:16
|
|
Would be great, but sounds complicated (a lot of work and time required)...
In the meanwhile could please you quickly recompile a version of the slave with 640KB of CHIP ram, so I can test if it's just a matter of chipmem?
About the fact it won't work on 512KB of chip... I think it was a problem in the original game too if you had just 512KB CHIP: the game won't crash and just warns you it has to disable music to continue. |
|
|
(0011722)
|
Hexaae
|
2022-08-17 19:38
|
|
|
|
(0011730)
|
Hexaae
|
2022-08-30 00:25
|
|
@Wepl
REQUEST: make the SLAVE work even with uncompressed "Ambermoon" exe, in case. |
|
|
(0011954)
|
Hexaae
|
2022-11-11 02:25
|
|
@Wepl
current Slave 2.2 has not enough CHIPMEM. To avoid "chipmem not enough" error in castle Godsbane when you open local map the game requires 640KB (at least, this value works fine in my hacked slave). |
|