CD32 Quickstart fails to boot CD if..

[a4k-oerx]

WinUAE 1.5.3 and 1.5.4b1

Have observed a strange effect with CD32 Quickstart (and possibly also normal CD32 setup if configured "by hand") if I try to use a bootable CD32 disc as mounted ISO image (as drive Y: ) in Windows XP.

Have used WinUAE default settings, config-dir is empty, ROMs are available, default settings, see also attached winuae.ini

Quickstart appears to auto-scan available drives for bootable discs if I understand the logfiles. It identifies the mounted ISO correctly as CD32/CDTV but fails to boot it, if the Chipset Extra is set to CD32.

Have attached logfiles of 4 cases, with only the last one booting the mounted CD32 disc, with Chipset Extra set to Generic, so actually no real CD32 setup. Black screen is 0% to 3-4% CPU, have waited a few minutes in one testcase, Amiga/UAE does not crash but nothing happens.

Something wrong in CD32 routines?

The disc boots fine in several real CD32 machines...

Config always:
- winuae.ini
- Config dir/subdirs empty
- Normal and Extended ROM available for CD32
- CD32 Quickstart (with logging enabled)

log1:
Config extra:
- Y: is a mounted bootable CD32-ISO in WindowsXP
Effect:
- Y: is detected as CD32/CDTV, screen stays black, fail.

log2:
Config extra:
- Y: has mounted no ISO in WindowsXP, invalid drive
Effect:
- Y: can't read TOC, cd32 bootlogo with CD appears, "success".

log3:
Config extra:
- Y: is a mounted bootable CD32-ISO in WindowsXP
- Y: is added via "Add Directory" as read-only, bootable HD
Effect:
- Y: is detected as CD32/CDTV, screen stays black, fail.

log3:
Config extra:
- Y: is a mounted bootable CD32-ISO in WindowsXP
- Y: is added via "Add Directory" as read-only, bootable HD
- Chipset Extra set from CD32 to Generic
Effect:
- Y: is detected as FS=CDFS, boots fine, "success".

Note:
Y: is mounted ISO in XP with "Windows XP ISO Mount Utility":
http://download.microsoft.com/downlo...olpanel_21.exe

[Retro-Nerd]

Have you tried common mounting tools like Alcohol or DaemonTools too? Never heard of this WinXP mount utility.

[Toni Wilen]

Y: is mounted ISO in XP with "Windows XP ISO Mount Utility":

I don't think this is CD emulator but only drive letter mounter. CD32 emulation needs block level access, drive letter won't help.

[a4k-oerx]

It's a free tool from Microsoft, does (Edit: not)the same as Alcohol and DaemonTools (which both I do not have installed).

See eg.
http://myutilities.blogspot.com/2005...indows-xp.html

The problem is somewhere else, as WinUAE sees the files and also boots fine from the mounted ISO if Chiptset Extra is set to Generic.

[a4k-oerx]

Originally Posted by Toni Wilen

I don't think this is CD emulator but only drive letter mounter. CD32 emulation needs block level access, drive letter won't help.

That might be the solution.

Edit: But WinUAE should not hang if no block level access is there. It CAN identify the disc as "CD32/CDTV" obviously without block level access? See log1.

Edit 2: Note: It mounts a real ISO file, not only some sub-dir as drive-letter...

[Toni Wilen]

Originally Posted by a4k-oerx

It's a free tool from Microsoft, does the same as Alcohol and DaemonTools (which both I do not have installed).

I still don't think so. Does it appear as a drive in device manager/disk manager? Does it appear in CD burning software as a source drive?

The problem is somewhere else, as WinUAE sees the files and also boots fine from the mounted ISO if Chiptset Extra is set to Generic.

Of course it does if you add the drive letter as a harddrive but thats not emulating CD32.

[a4k-oerx]

It shows up in explorer, but not as source-drive in Nero. So that means, not block access I guess.

Nevertheless WinUAE identify the disc as "CD32/CDTV" obviously also without block level access? See log1. Why is that?

Edit, log: 58-875: Drive Y:: CD32 or CDTV

And another question: Can I switch off that auto-scanning/mounting? No "auto-mount" things are checked in WinUAE settings.

PS. Thanks for your quick help.

Edit 2: The only drive which shows up also in Nero as source-drive is the DAEMON Tools mount.

[Toni Wilen]

Originally Posted by a4k-oerx

It shows up in explorer, but not as source-drive in Nero. So that means, not block access I guess.

Nevertheless WinUAE identify the disc as "CD32/CDTV" obviously also without block level access? See log1. Why is that?

Edit, log: 58-875: Drive Y:: CD32 or CDTV

Perhaps it supports some features but not all.. Try burning the image to CD-R/RW and try booting using real drive. (You sure the image is real CD32 CD image and not some weird harddrive bootable only, it wouldn't be the first time..)

And another question: Can I switch off that auto-scanning/mounting? No "auto-mount" things are checked in WinUAE settings.

Not possible. Why? There is no manual cd configuration.

[a4k-oerx]

After further testing, it appears that two problems can be identified:

1. A valid from CD dumped CD32-ISO which has been edited with UltraISO (added one dir + some files, replaced some files) appears to be no valid ISO any more for WinUAE, see also below. But it mounts fine in all ISO mounting utilities below and all files are available from Windows.

Obviously UltraISO modifies something in the ISO which does not affect access to any files via Windows, but does affect WinUAE accessing the data. Edit: Seems UltraISO overwrote/stripped the CD32.TM data, so how does WinUAE detect the ISO as CD32 or CDTV?

2. Different ISO mounting utilities produce different results.

2.1. Windows XP ISO Mount Utility

35-609: IOCTL: FSCTL_ALLOW_EXTENDED_DASD_IO returned 1
35-609: IOCTL: device '\\.\W:' opened succesfully (unit number=2,media=1)
35-609: Drive W:: CD32 or CDTV
..
35-625: IOCTL: FSCTL_ALLOW_EXTENDED_DASD_IO returned 1
35-625: IOCTL: device '\\.\W:' opened succesfully (unit number=2,media=1)
35-625: using drive Drive W: (unit 2, media 1)

WinUAE can identify CD32 or CDTV but can not boot valid from CD dumped CD32-ISO, black screen appears.

2.2. UltraISO 9.3.1.2633

32-062: IOCTL: FSCTL_ALLOW_EXTENDED_DASD_IO returned 1
32-062: IOCTL: device '\\.\X:' opened succesfully (unit number=3,media=1)
32-062: Drive X:: CD32 or CDTV
...
32-062: IOCTL: FSCTL_ALLOW_EXTENDED_DASD_IO returned 1
32-062: IOCTL: device '\\.\X:' opened succesfully (unit number=3,media=1)
32-062: using drive Drive X: (unit 3, media 1)

WinUAE can identify CD32 or CDTV and can boot valid from CD dumped CD32-ISO, success.

02-218: IOCTL: FSCTL_ALLOW_EXTENDED_DASD_IO returned 1
02-218: IOCTL: device '\\.\X:' opened succesfully (unit number=3,media=1)
02-218: Drive X:: CD32 or CDTV
...
02-218: IOCTL: FSCTL_ALLOW_EXTENDED_DASD_IO returned 1
02-218: IOCTL: device '\\.\X:' opened succesfully (unit number=3,media=1)
02-218: using drive Drive X: (unit 3, media 1)

WinUAE 1.5.3 can identify CD32 or CDTV but can not boot with UltraISO edited CD32-ISO, CD-32 start-anim appears.

WinUAE 1.5.4b1 can identify CD32 or CDTV but can not boot with UltraISO edited CD32-ISO, CD-32 start-anim appears with delayed appearing graphics and double/overlayed sound-effects. This happens only with 1.5.4b1 and if DAEMON Tools (see below) is running at the same time with no own ISO mounted. If I capture a video, the graphics appears delayed but sound is not double/overlayed. Very strange effect.

2.3. DAEMON Tools Lite 3.47

48-875: IOCTL: FSCTL_ALLOW_EXTENDED_DASD_IO returned 1
48-875: IOCTL: device '\\.\Y:' opened succesfully (unit number=4,media=1)
48-875: Drive Y:: CD32 or CDTV
48-875: IOCTL: FSCTL_ALLOW_EXTENDED_DASD_IO returned 1
48-875: IOCTL: device '\\.\Y:' opened succesfully (unit number=4,media=1)
48-875: using drive Drive Y: (unit 4, media 1)

WinUAE can identify CD32 or CDTV and can boot valid from CD dumped CD32-ISO, success.

Both WinUAE 1.5.3 and 1.5.4b1 can identify CD32 or CDTV but can not boot with UltraISO edited CD32-ISO, CD-32 start-anim appears. No effects like above.

Conclusion: Using the Microsoft utility caused one problem, using a UltraISO modified ISO caused another problem. Both were difficult to identify as no errors are detected and/or logged.

[Toni Wilen]

Originally Posted by a4k-oerx

Obviously UltraISO modifies something in the ISO which does not affect access to any files via Windows, but does affect WinUAE accessing the data. Edit: Seems UltraISO overwrote/stripped the CD32.TM data, so how does WinUAE detect the ISO as CD32 or CDTV?

I guess it modifies "boot" sector partially but leaves the CDTV/CD32 identifier intact. CD32 boot rom ignores the CD if tm-data has been modified, even if one bit is wrong.

[a4k-oerx]

The tm-data was the indeed the problem.

After rebuilding the (by UltraISO modified) ISO with ISOCD V1.04 in WinUAE, the new mounted ISO boots fine in CD32 mode.

What I did:
- mount the above described modified "bad" ISO in Windows, all files can be seen.
- boot WinUAE with a Workbench 3.1 with the mounted "bad" ISO added as a directory (read only) and a temp folder added as another directory (r/w) for the new ISO
- use ISOCD V1.04 with CD32.TM to create the new ISO
- mount the new ISO in Windows
- Start WinUAE with CD32 quickstart, works.

Note to Toni: Maybe add a small note to logfile if a volume is detected as CD32/CDTV but then tm-data is not found/corrupt. Kiitos.

[Toni Wilen]

Originally Posted by a4k-oerx

Note to Toni: Maybe add a small note to logfile if a volume is detected as CD32/CDTV but then tm-data is not found/corrupt. Kiitos.

Consider it done (CD32.TM detection only, CDTV.TM requires filesystem parsing and I am not sure if I want to bother with it..)