Bootable Floppy error

[Robb Bates]

I'm trying to create a ZPM3 bootable floppy.  Following the instructions in the manual.

Here's what happens:

13:26 A0:SYSTEM>dir

Scanning Directory...

Sorting  Directory...

Directory For Drive A:  User  0

    Name     Bytes   Recs   Attributes      Name     Bytes   Recs   Attributes
------------ ------ ------ ------------ ------------ ------ ------ ------------
BNKBDOS3 SPR    16k    106 Dir RW       BNKBIOS3 SPR     8k     36 Dir RW
CPM3     SYS    32k    236 Dir RW       GENCPM   DAT     4k     19 Dir RW
HELP     HLP    64k    496 Dir RW       MAKEDOS  COM     4k     17 Dir RW
README   TXT     4k     20 Dir RW       RESBDOS3 SPR     4k     16 Dir RW
STARTZPM COM     4k      8 Dir RW       ZCCP     COM     4k     25 Dir RW
ZINSTAL  ZPM     4k     12 Dir RW       ZPMLDR   COM     4k     30 Dir RW
ZPMLDR   SYS     8k     41 Dir RW

Total Bytes     =    160k  Total Records =    1062  Files Found =   13
Total 1k Blocks =    139   Used/Max Dir Entries For Drive A:  228/1024

13:26 A0:SYSTEM>syscopy d:=a:zpmldr.sys

SYSCOPY v2.1 for RomWBW CP/M, 15-May-2020 (CP/M 3 Mode)
Copyright 2020, Wayne Warthen, GNU GPL v3

Transfer system image from A:ZPMLDR.SYS to D: (Y/N)? y
Reading image...
DOS error, return code=0x01

Not sure what that error even means.  The floppy is writable, as I am able to copy other files over to it.

Robb

[Robb Bates]

More research found this:

https://github.com/wwarthen/RomWBW/issues/529

But Wayne says ZPMLDR.SYS was fixed already...but maybe it got broken again...

Robb

[Robb Bates]

ZPMLDR.SYS shows records = 41, which as I recall are 128 byte records.  The bug report says it should be a multiple of 512 bytes, which means it should be 40 or 44 records.  Maybe padding it up to 44 records would fix it?  But I'm not sure how to do that.

Robb

[Mark Pruden]

Are you certain you have obtained the latest zpm disk image, noting the fix was quite recent.

[Wayne Warthen]

Odd.  This was supposed to have been fixed in 3.5.1.  However, I am still seeing something wrong.  Give me a little time to look at this.

-Wayne

--
You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/rc2014-z80/153f1f36-e2a4-449e-a74f-24de140841f5n%40googlegroups.com.

[Wayne Warthen]

OK, two problems.

First, my comment in Issue #529 was incorrect.  The file does not need to be an exact multiple of 512 bytes.  The core problem (in v3.5.0) was that the size of the file did not match the size specified in the header of the file.  This was corrected in v3.5.1 by making the size of the file 42 records (5,376 bytes).

@Robb, I suspect you somehow have a disk image with the v3.5 version of zpmldr.sys on it.  The erroneous file size is 41 records, which is what you reported.  I have confirmed that both zpmldr.sys and cpmldr.sys are 42 records long in v3.5.1.

Thanks, Wayne

[Robb Bates]

Derp.  You are indeed correct.  I'll have to upgrade I suppose.

Robb

[Wayne Warthen]

Just copy the one file over from the v3.5.1 distribution archive.

--

You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.

To view this discussion, visit https://groups.google.com/d/msgid/rc2014-z80/09ef17e0-6807-4a5b-a476-37896b66b044n%40googlegroups.com.

[Robb Bates]

Yep, that worked.  I didn't think to try that since I figured I would have some BIOS mismatch errors pop up or something.

Robb

[Wayne Warthen]

FYI, the version mismatch stuff will only apply to version changes at the top two levels.

[Robb Bates]

Ah, good to know!