bootblock

[mai]

I have found inside scene collection a lot of disks, where the disks dont start, when inserting in WinUAE.
I had a look with an hex editor and saw the reason.
Is there any logical reason for this:

[Galahad/FLT]

Originally Posted by mai

I have found inside scene collection a lot of disks, where the disks dont start, when inserting in WinUAE.
I had a look with an hex editor and saw the reason.
Is there any logical reason for this:

Try with an Kickstart 3.0+

[mai]

Originally Posted by Galahad/FLT

Try with an Kickstart 3.0+

Does not work.

[Galahad/FLT]

Upload a bootblock to the zone and i'll check it out or one of the disks.

[Leffmann]

Yes it's that $68 that causes the boot block checksum to not add up. Set it to 0 and you get the correct checksum.

AmigaOS will only attempt to boot a disk when the checksum is $FFFF FFFF and the first 4 bytes are $444F 5300. Most antivirus utilities should be able to calculate the checksum for you, it's a quick way to find out if this is the cause.

[mai]

Originally Posted by Leffmann

Yes it's that $68 that causes the boot block checksum to not add up. Set it to 0 and you get the correct checksum.

yes, i was aware, but how can this happens, where are many disks with the same $68 value.

[Leffmann]

Good question perhaps all these disks/disk images have been processed with the same buggy tool?

[redblade]

Perhaps the scene disks had a custom boot loader on it and the virus killer warned it was a possible virus and 'installed' the disk? (with a incorrect boot crc)