| Solved: Re: [hatari-users] ICD hard drive image |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-users Archives
]
- To: hatari-users@xxxxxxxxxxxxxxxxxxx
- Subject: Solved: Re: [hatari-users] ICD hard drive image
- From: Charles Curley <charlescurley@xxxxxxxxxxxxxxxxx>
- Date: Mon, 20 May 2019 11:47:08 -0600
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=charlescurley.com; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Subject:To:From:Date:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=92pTrvrhaJ8vE3Wy4eac35tgK5GW11AKg2YtBbGV0+0=; b=K/po82Ta/Spw+vDNcrvqhXDp1h oWDsbyDy95j9Yv0BoTfH3Vr6AvRw6J7kqL0AiJrn8WXA7t5Z+D4Dhcxz68BiR/TP+bnw7bKXKITqQ vgxRzMA2Enb9BOmGfv1doAU7jHnuWBdVbNbxkUTLa1FXv3aQNdjF/LUdCD7eU4v+RmyptQYKzrTaF tuswVPHwWWNESjMqe5b2qh7PgdtWC2qn4TYpIPjOGU28EF2aIIkac4YEI16ViCTQWDOqn2ikA8/U/ uBo69XCJi2BNm2KBRg9/eikdN6Zpv7GHVykA6VmTZvF+12EDPhZOiTDF7B8JZD4P/4XCouU9uS2Ly DoVKhsug==;
- Organization: occasionally
On Mon, 20 May 2019 18:07:58 +0200
Thomas Huth <th.huth@xxxxxxxxx> wrote:
> And Charles, could you please post an ASCII-dump of the first sector
> of your failing hard disk image? Something like:
>
> dd if=disk.img bs=512 count=1 status=none | xxd
charles@hawk:~/projects/hatari$ dd if=test.img bs=512 count=1 status=none | xxd
00000000: 2f0b 3f3c ffff 3f3c 000b 4e4d 588f c07c /.?<..?<..NMX..|
00000010: 000f b07c 000e 6700 005a 41fa 01a6 4a98 ...|..g..ZA...J.
00000020: 6700 0050 7203 0210 0081 0c10 0081 6600 g..Pr.........f.
00000030: 003a 49fa 01cc 7601 2c28 0004 2006 6100 .:I...v.,(.. .a.
00000040: 004a 6600 0026 343c 00ff 224c 4240 d059 .Jf..&4<.."LB@.Y
00000050: 51ca fffc b07c 1234 6600 0010 4bfa 002c Q....|.4f...K..,
00000060: 4e94 1e3c 00e0 6000 000a d0fc 000c 51c9 N..<..`.......Q.
00000070: ffb6 303c fde8 5340 66fc 265f 4e75 0800 ..0<..S@f.&_Nu..
00000080: 0000 0100 8a8a 8a8a 8a00 48e7 40f0 41f8 ..........H.@.A.
00000090: 8604 43e8 0002 50f8 043e 2238 04ba 5881 ..C...P..>"8..X.
000000a0: b2b8 04ba 64fa 2f0c 11ef 0003 860d 11ef ....d./.........
000000b0: 0002 860b 11ef 0001 8609 588f 45fa ffc0 ..........X.E...
000000c0: 2480 7008 8007 1480 32bc 0190 32bc 0090 $.p.....2...2...
000000d0: 3083 1543 0004 32bc 0088 7205 47ea 0006 0..C..2...r.G...
000000e0: 4280 101a 4840 101b 2080 4a41 6700 000e B...H@.. .JAg...
000000f0: 6100 0036 6b00 001e 51c9 ffe6 203c 0006 a..6k...Q... <..
00000100: ddd0 6100 002a 6b00 000c 32bc 008a 3010 ..a..*k...2...0.
00000110: c07c 00ff 32bc 0080 4e71 4a50 4278 043e .|..2...NqJPBx.>
00000120: 4cdf 0f02 4a40 4e75 203c 0000 3a98 0838 L...J@Nu <..:..8
00000130: 0005 fa01 6700 0006 5380 6af2 4e75 0000 ....g...S.j.Nu..
00000140: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000150: 0000 0000 0000 0147 454d 0003 ae6d 0000 .......GEM...m..
00000160: eb9b 0147 454d 0004 9a08 0000 eb9b 0147 ...GEM.........G
00000170: 454d 0005 85a3 0000 eb9b 0147 454d 0006 EM.........GEM..
00000180: 713e 0000 eb9b 0147 454d 0007 5cd9 0000 q>.....GEM..\...
00000190: eb9b 0147 454d 0008 4874 0000 eb9b 0147 ...GEM..Ht.....G
000001a0: 454d 0009 340f 0000 eba5 0000 0000 0000 EM..4...........
000001b0: 0000 0000 0000 06f4 07ff 06f4 06f4 0102 ................
000001c0: 0136 000a 1fb4 8147 454d 0000 0001 0000 .6.....GEM......
000001d0: eb9b 0147 454d 0000 eb9c 0000 eb9b 0147 ...GEM.........G
000001e0: 454d 0001 d737 0000 eb9b 0147 454d 0002 EM...7.....GEM..
000001f0: c2d2 0000 eb9b 0000 0000 0000 0000 4565 ..............Ee
charles@hawk:~/projects/hatari$
>
> And please also post the log output of Hatari that you get when
> running it with "--log-level debug" ?
charles@hawk:~/projects/hatari$ hatari --log-level debug
DEBUG: STMemory_RAM_SetBankSize total=2048 KB bank0=2048 KB bank1=0 KB MMU=8
DEBUG: Video_SetSystemTimings 1 3 -> 2 (WS3) 503 503 64
INFO : Hatari v2.1.0, compiled on: Dec 18 2018, 14:26:22
DEBUG: Video_SetSystemTimings 1 3 -> 2 (WS3) 503 503 64
DEBUG: Configured max Hatari resolution = 832x588, optimal for ST = 832x588
DEBUG: STMemory_RAM_SetBankSize total=2048 KB bank0=2048 KB bank1=0 KB MMU=8
INFO : Inserted disk '/home/charles/projects/hatari/ff.scr.disk.st' to drive A:.
DEBUG: update cyc speed 0 throttle 0.000000 clock_mult 512
DEBUG: CPU cycleunit: 256 (0.500)
DEBUG: CPU cycleunit: 256 (0.500)
DEBUG: 1870 CPU functions
DEBUG: Sound: Disabled
INFO : Mounting hard drive image '/home/charles/projects/hatari/fast.forth.img'
INFO : Mounting hard drive image '/home/charles/projects/hatari/drived.img'
INFO : Mounting hard drive image '/home/charles/projects/hatari/atari.micropolis.img'
ERROR: Cannot open HD file read/write!
DEBUG: Checking GEMDOS E: HDD: /home/charles/projects/hatari/cdrive
INFO : GEMDOS HDD emulation, E: <-> /home/charles/projects/hatari/cdrive.
DEBUG: memory_map_Standard_RAM total=2097152 ram0=2097152 ram1=0 mmu0=131072 mmu1=131072
DEBUG: memory_map_Standard_RAM - enable MMU 2097152 131072 131072
DEBUG: Loaded TOS version 2.06, starting at $e00000, country code = 0, NTSC
DEBUG: Skipped TOS patches.
DEBUG: Video_SetSystemTimings 1 3 -> 2 (WS3) 503 503 64
DEBUG: Video_SetSystemTimings 1 3 -> 2 (WS3) 503 503 64
DEBUG: Host system has accurate delays. (1)
DEBUG: update cyc speed 0 throttle 0.000000 clock_mult 512
DEBUG: CPU cycleunit: 256 (0.500)
DEBUG: CPU cycleunit: 256 (0.500)
DEBUG: Building CPU, 44274 opcodes (0 -2 1)
DEBUG: CPU=68000, FPU=0, MMU=0, JIT=0.
DEBUG: prefetch and cycle-exact
DEBUG: 24-bit
DEBUG:
DEBUG: hardreset, memory cleared
DEBUG: m68k_run_1_ce
DEBUG: Illegal instruction: 4e7b at 00E0005E -> 00E00062
DEBUG: CPU reset PC=e0006e (ROM memory)..
DEBUG: Illegal instruction: 4e7b at 00E0009C -> 00E000A0
DEBUG: Illegal instruction: 4e7b at 00E000D4 -> 00E000E8
WARN : Bus Error reading at address $ffff8282, PC=$e00156 addr_e3=e0015a op_e3=4a38
WARN : Bus Error reading at address $ffff8400, PC=$e00170 addr_e3=e00174 op_e3=4a38
DEBUG: memory_map_Standard_RAM total=2097152 ram0=2097152 ram1=0 mmu0=2097152 mmu1=2097152
DEBUG: memory_map_Standard_RAM total=2097152 ram0=2097152 ram1=0 mmu0=2097152 mmu1=131072
DEBUG: Illegal instruction: 7300 at 00E093BA -> 00E093C2
DEBUG: Illegal instruction: 42c0 at 00E00472 -> 00E004C6
WARN : Bus Error reading at address $fffffa40, PC=$e00556 addr_e3=e0055a op_e3=4a78
WARN : Bus Error reading at address $ffff860f, PC=$e00c28 addr_e3=e00c2a op_e3=4a10
WARN : Bus Error reading at address $ffff8400, PC=$e00c28 addr_e3=e00c2a op_e3=4a10
WARN : Bus Error reading at address $ffff8282, PC=$e00c28 addr_e3=e00c2a op_e3=4a10
WARN : Bus Error reading at address $fffffa81, PC=$e00c28 addr_e3=e00c2a op_e3=4a10
WARN : Bus Error reading at address $ffff8c80, PC=$e00c28 addr_e3=e00c2a op_e3=4a10
WARN : Bus Error reading at address $ffff8e09, PC=$e00c28 addr_e3=e00c2a op_e3=4a10
WARN : Bus Error reading at address $ffff8961, PC=$e00c28 addr_e3=e00c2a op_e3=4a10
WARN : Bus Error reading at address $ffff8901, PC=$e00c28 addr_e3=e00c2a op_e3=4a10
WARN : Bus Error reading at address $ffff9201, PC=$e00c28 addr_e3=e00c2a op_e3=4a10
WARN : Bus Error reading at address $fff0001d, PC=$e00c28 addr_e3=e00c2a op_e3=4a10
WARN : Bus Error reading at address $fff0005d, PC=$e00c28 addr_e3=e00c2a op_e3=4a10
WARN : Bus Error reading at address $fff0009d, PC=$e00c28 addr_e3=e00c2a op_e3=4a10
WARN : Bus Error reading at address $fff000dd, PC=$e00c28 addr_e3=e00c2a op_e3=4a10
WARN : Bus Error reading at address $fffffe00, PC=$e00c28 addr_e3=e00c2a op_e3=4a10
DEBUG: Bus error bget at 00cc03c3
WARN : Bus Error reading at address $cc03c3, PC=$e00c28 addr_e3=e00c2a op_e3=4a10
DEBUG: exit m68k_run
INFO : Floppy A: has been removed from drive.
charles@hawk:~/projects/hatari$
This line was a clue:
ERROR: Cannot open HD file read/write!
Bingo!
I had set the image to read only. Allowing writes to it let the desktop
import several of the partitions. So read-only images are not allowed.
Bug? Or if that's a feature, please document it.
So here's what I see: I have two other disk images, one partition each.
They show up as C: and D:. Then four partitions from the new image, E:
through H:. I: is my GEMDOS mounted directory. J: to O: are further
partitions from the new image. Is that the drive ordering you want, or
should the GEMDOS drive show up as O:? I was expecting it at O:.
Relevant portions of debug output from a running instance:
DEBUG: Sound: Disabled
INFO : Mounting hard drive image '/home/charles/projects/hatari/fast.forth.img'
INFO : Mounting hard drive image '/home/charles/projects/hatari/drived.img'
INFO : Mounting hard drive image '/home/charles/projects/hatari/atari.micropolis.img'
DEBUG: Checking GEMDOS I: HDD: /home/charles/projects/hatari/cdrive
INFO : GEMDOS HDD emulation, I: <-> /home/charles/projects/hatari/cdrive.
DEBUG: memory_map_Standard_RAM total=2097152 ram0=2097152 ram1=0 mmu0=131072 mmu1=131072
DEBUG: memory_map_Standard_RAM - enable MMU 2097152 131072 131072
--
"When we talk of civilization, we are too apt to limit the meaning of
the word to its mere embellishments, such as arts and sciences; but
the true distinction between it and barbarism is, that the one
presents a state of society under the protection of just and
well-administered law, and the other is left to the chance government
of brute force."
- The Rev. James White, Eighteen Christian Centuries, 1889
Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
https://charlescurley.com