English Amiga Board - View Single Post - Boot problem after changing Kickstart to/from 1.2

mark_k · 18 November 2017, 18:02

Yes the issue only seems to happen with a (uaehf) HDF configured. You can use Crash_test_HD_4GB.bin to illustrate the problem. Shared folder isn't necessary. Config with no shared folder, 1.2 ROM:

Code:

https://www.media!fire.com/file/fiobjz970b5je3p/my_test_JIT_uaegfx_NoZ3RAM3.zip

Load config, start emulation. See 1.2 insert Workbench disk screen. Press Ctrl-A-A. Machine resets then "No disk present in unit 0" requester appears. This in log:
filesystem: diagentry 00202da0 configdev 00000000
Pre-KS 1.3 automount hack: DF0: boot block faked.

At that point you can press F12, change to 3.1 ROM and click Reset. Same requester appears. Press Ctrl-A-A, same requester appears. With 3.1 ROM there is this in the log:
filesystem: diagentry 00200098 configdev 00000c48
filesystem: diagentry 0020be68 configdev 00000000
Pre-KS 1.3 automount hack: DF0: boot block faked.
Pre-KS 1.3 automount hack: init drives.

18 November 2017, 18:02	#3
mark_k Registered User Join Date: Aug 2004 Location: Posts: 3,343	Yes the issue only seems to happen with a (uaehf) HDF configured. You can use Crash_test_HD_4GB.bin to illustrate the problem. Shared folder isn't necessary. Config with no shared folder, 1.2 ROM: Code: https://www.media!fire.com/file/fiobjz970b5je3p/my_test_JIT_uaegfx_NoZ3RAM3.zip Load config, start emulation. See 1.2 insert Workbench disk screen. Press Ctrl-A-A. Machine resets then "No disk present in unit 0" requester appears. This in log: filesystem: diagentry 00202da0 configdev 00000000 Pre-KS 1.3 automount hack: DF0: boot block faked. At that point you can press F12, change to 3.1 ROM and click Reset. Same requester appears. Press Ctrl-A-A, same requester appears. With 3.1 ROM there is this in the log: filesystem: diagentry 00200098 configdev 00000c48 filesystem: diagentry 0020be68 configdev 00000000 Pre-KS 1.3 automount hack: DF0: boot block faked. Pre-KS 1.3 automount hack: init drives.