CP/M-86 floppy image

[Henk Siewert]

Hallo,
I have a 3,5 inch 1,4mb floppy that I use to boot my PC into CP/M-86 for the
IBM PC and IBM PC XT Version 1.1
It uses the brilliant drivers made by Freek Heite.
I like to put an image of this disk on my website.
Until now I have not found a program that is able to make an image of this
floppy.
Help is greatly appreciated.
Henk Siewert

[Tonton Th]

On 11/08/2011 11:46 AM, Henk Siewert wrote:
> Hallo,
> I have a 3,5 inch 1,4mb floppy that I use to boot my PC into CP/M-86 for the
> IBM PC and IBM PC XT Version 1.1
> It uses the brilliant drivers made by Freek Heite.
> I like to put an image of this disk on my website.
> Until now I have not found a program that is able to make an image of this
> floppy.

rawrite under messydos, dd under unices ?

--

Nous vivons dans un monde étrange/
http://foo.bar.quux.over-blog.com/

[Henk Siewert]

> rawrite under messydos, dd under unices ?

Hallo,

I am very sorry but I do not understand a word you are sying.

Henk Siewert

"Tonton Th" <t...@la.bas.invalid> schreef in bericht
news:4eb91ddd$0$8439$426a...@news.free.fr...

> On 11/08/2011 11:46 AM, Henk Siewert wrote:
>> Hallo,
>> I have a 3,5 inch 1,4mb floppy that I use to boot my PC into CP/M-86 for
>> the
>> IBM PC and IBM PC XT Version 1.1
>> It uses the brilliant drivers made by Freek Heite.
>> I like to put an image of this disk on my website.
>> Until now I have not found a program that is able to make an image of
>> this
>> floppy.
>
>

[Henk Siewert]

Hallo,

From the post the French gentleman Tonton send us I recognized Rawrite.
After some googleling I found RawWrite for Windows 0.7.
After installing I made a .img of my CP/M-86 disk.
But this image is having the same problem as all the other images made by
other programs.
After writing the image to a new disk and booting my IBM NetVista from this
disk I get the error:
A>SUBMIT AUTOEXEC
MEMORY NOT AVAILABLE
AUTOEXEC?

This machine is equipped with 1.5 Gigabyte RAM!
So what can be the problem.
Booting from the original floppy, where the image was made of, is going
perfectly.

Henk Siewert

"Tonton Th" <t...@la.bas.invalid> schreef in bericht
news:4eb91ddd$0$8439$426a...@news.free.fr...

[Ivan Shmakov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> Henk Siewert <s...@tiscali.nl> writes:

>>> I have a 3,5 inch 1,4mb floppy that I use to boot my PC into
>>> CP/M-86 for the

[…]

> A> SUBMIT AUTOEXEC
> MEMORY NOT AVAILABLE
> AUTOEXEC?

> This machine is equipped with 1.5 Gigabyte RAM!

Which, to the best of my knowledge, no system of the CP/M family
could be made to recognize.

> So what can be the problem.

> Booting from the original floppy, where the image was made of, is
> going perfectly.

Could it be that the original floppy uses some special format?
(i. e., other than the PC's standard 80 tracks, 2 sides, and 18
sectors per track.)

- --
FSF associate member #7257
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBAgAGBQJOuVcRAAoJEOhSCjIbp0KhX7YP/0Eg1yYTavqzwPPPkFDOgB0L
LppuUPsvzcnn/HOUPmc4z0CTs1IR1apS1tdadse9VEVCSAQBGGHIJj/v+wVGyb5v
oX/t7rmJ6P7s+2f05fDD4uk1qBP81Wm9C1vL/LWVk2jbgTany1GwrahpY2VVjTBV
bRzFVNj4pXWFQ8rNysKM8WyEoFJNT/LDTLrUoT+HAoXBCZoj4bwcyZFbQv5cxyna
S1sLj09GWcbszvLQil1jZQxZRgZiYbZYf72p9iuPAqT2Zvft5xYWjZef7Vysp91Q
SdtTn3XVpu9nqn7DntI6YW75VZo/5MI4d2LSlMLDyy6xXrluh2kzvycbAim+pzmI
9rIbEsTgMdFwDwe9G8RC2d6zIZZHeoJDNZGcdhhqtai9uv/G4u1p88dad6KyDppI
PpWofoLFq2vw3iSacvHqOf6e8sjG6isCdgnd1qlAmLV1vLyJr8Yjqd6plX7TPl5P
rzrqQmrYRzhR+8JFOn60u8i8f+Ss9bhw6rMX3XrcYYCoChMeizvwkuYuM0/8jpa0
h5tW8UKRAlsmdZT930r7ouScHoc5+uHFd6g6xOyQms0TPBkIl0n+ddyNmrU3BEY1
YB90VqFKBpIP03IlMiPlVH110l32aeB5wtvUOhriW36FbvPKUyUL7Vg1MvUOtn7E
U5IGlHhg9i4AQ1Mb1xlC
=mIum
-----END PGP SIGNATURE-----

[Lawrence Sonderling]

I have the same "MEMORY NOT AVAILABLE" problem when installing CP/M-86
to a hard drive image under VirtualBox. VirtualBox boots fine from a
floppy image but gives the above error message when trying to boot from
the hard drive image.

Larry Sonderling

[s_dub...@yahoo.com]

There is an image, and pcdos batch file to install it to floppy, here:

http://www.cpm.z80.de/download/144cpm86.zip

If you have 720k 3 1/2 in floppies, and a floppy drive that can use
those (some of the modern floppy drives don't recognize these anymore)
the version for the Eagle can be made to work also..

http://www.cpm.z80.de/download/eaglecpm.zip

Both use CopyQM to restore disk image.

see Gaby's unofficial CP/M website.. http://www.cpm.z80.de/binary.html

Steve

[Roger Ivie]

On 2011-11-08, Ivan Shmakov <onei...@gmail.com> wrote:

>>>>>> Henk Siewert <s...@tiscali.nl> writes:
> > This machine is equipped with 1.5 Gigabyte RAM!
>
> Which, to the best of my knowledge, no system of the CP/M family
> could be made to recognize.

CP/M-68K could.
--
roger ivie
ri...@ridgenet.net

[roger]

Hello Henk!

besides that the image is found in the net the problem is the
following:

Freek has marked the disk as a 160 kb disk. This information is stored
in the boot sector.
(Like all other disks) Nearly all programs use this information to
read the disk and create the image!
So in this case you get a 160 kb image.....

Maybe a chance if you take pure MSDOS....

Rüdiger

[Henk Siewert]

Hallo,

Thank you all very much.
Now that I have the image from http://www.cpm.z80.de/download/144cpm86.zip
all problems are solved.

Henk Siewert

"Henk Siewert" <s...@tiscali.nl> schreef in bericht
news:4eb90885$0$14709$5fc...@news.tiscali.nl...

[Archer]

On Tue, 8 Nov 2011 11:46:22 +0100, "Henk Siewert" <s...@tiscali.nl>
wrote:

>Hallo,
>I have a 3,5 inch 1,4mb floppy that I use to boot my PC into CP/M-86 for the
>IBM PC and IBM PC XT Version 1.1
>It uses the brilliant drivers made by Freek Heite.
>I like to put an image of this disk on my website.
>Until now I have not found a program that is able to make an image of this
>floppy.

Why bother. Heite's floppy image is already available in the web.
Check Gaby's site.

--
Sandy

[Henk Siewert]

Thank you for your very positive reaction...

"Archer" <i...@here.com> schreef in bericht
news:b22lb7h3kahj5qcjn...@4ax.com...

[Bill Marcum]

yOn 2011-11-09, Roger Ivie <ri...@ridgenet.net> wrote:
> On 2011-11-08, Ivan Shmakov <onei...@gmail.com> wrote:
>>>>>>> Henk Siewert <s...@tiscali.nl> writes:
>> > This machine is equipped with 1.5 Gigabyte RAM!
>>
>> Which, to the best of my knowledge, no system of the CP/M family
>> could be made to recognize.
>
> CP/M-68K could.

The 68K cpu doesn't have segmented addressing like the 8086.
Perhaps one should say no CP/M-86 system could be made to recognize it.
In addition, as I recall the original CP/M-86 required a patch to work
with 80286 or later CPUs, and patched disk images are available on
Gaby's unofficial CP/M website.


--
Welcome to Borger King. Your way will be assimilated.

[dott.Piergiorgio]

Il 09/11/2011 07:22, roger ha scritto:

> besides that the image is found in the net the problem is the
> following:
>
> Freek has marked the disk as a 160 kb disk. This information is stored
> in the boot sector.
> (Like all other disks) Nearly all programs use this information to
> read the disk and create the image!
> So in this case you get a 160 kb image.....

mmmh.... I don't know if this disk is/was commercial, and if was
released when disk images was already in use, but seems to look like a
somewhat clever protection mechanism, but anyway the same tools used in
past for removal of these things (namely, track editors) perhaps can be
applied, but if is actually a protection scheme, surely in the boot
and/or booting code will be some checks of that marking...

Best regards from Italy,
dott. Piergiorgio.

[roger]

> somewhat clever protection mechanism, but anyway the same tools used in
> past for removal of these things (namely, track editors) perhaps can be
> applied, but if is actually a protection scheme, surely in the boot
> and/or booting code will be some checks of that marking...

Hello!

Its NOT a copy protection.....
It only signals MSDOS: hands off CP/M-86 !!!!

and there are 2 things that are not compatible:

the boot sector didn't contain the marks for a valid boot sector!: (AA
and 55)
and exact here has CP/M-86 the byte for the disk type....

Rüdiger

[Archer]

On Tue, 8 Nov 2011 22:22:12 -0800 (PST), roger <wil...@gmail.com>
wrote:

>besides that the image is found in the net the problem is the
>following:
>
>Freek has marked the disk as a 160 kb disk. This information is stored
>in the boot sector.
>(Like all other disks) Nearly all programs use this information to
>read the disk and create the image!
>So in this case you get a 160 kb image.....

IIRC Heite's CPM disc was available for both 720 and 1440 floppies, I
do have the 1440 here with me that works pretty well.

--
Sandy

[Freek]

"roger" <wil...@gmail.com> wrote

>> Its NOT a copy protection.....
>> It only signals MSDOS: hands off CP/M-86 !!!!

Correct, it has nothing to do with copy protection. I implemented it this
way to prevent both MS-DOS and CP/M-86-without-the-144FEAT-driver from
messing up with the CP/M-86 directory and files.
IIRC, I copied this "trick" from John Elliott.

Quoting from the documentation for 144FEAT about the layout of a 144FEAT
diskette:

In the DOS FAT's, all clusters are marked as "bad clusters. This prevents
DOS
from writing to the diskette's data area (not to the DOS directory - but
that wouldn't harm the CP/M-86 data).

The DOS directory is empty, except for a volume label "CPM-86-DISK" with
date and time stamps that indicate when the diskette was prepared.

In the directory as seen by standard CP/M-86, is a single file called
"CP/M-86.144" c.q. "CP/M-86.720" c.q. "CP/M-86.12M" that uses all available
(i.e. 160 KB) diskette space. This prevents standard CP/M-86 from writing
to the diskette, which it is seeing as a 160 KB, 40 tracks, single sided
diskette.

CP/M-86 1.1 when enhanced with the 1.44 MB feature, has its 8 KB directory
on track 2 and (for 720 KB and 1.2 MB) on the first sectors of track 3.
It ignores tracks 0 and 1 on the diskette. This prevents the 1.44 MB feature
from writing to the track 0 and 1 information that is used to "cheat" DOS
and
standard CP/M-86 1.1.

>> and there are 2 things that are not compatible:
>> the boot sector didn't contain the marks for a valid boot sector!: (AA
>> and 55)
>> and exact here has CP/M-86 the byte for the disk type....

Even on the 160 KB and 320 KB diskette formats supported natively by "CP/M86
for the IBM PC and XT", the original CP/M diskette formatting program
doesn't put hex AA and 55 in the last two bytes of the boot sector. CP/M-86
uses the last byte of the boot sector to indicate the diskette type. Quoting
again from my documentation for 144FEAT:

The very last byte on the very first sector of a diskette, defines the type
of diskette.

In standard CP/M-86, only two values are recognized:
1 = double-sided 40 tracks diskette, 8 sectors per track (320 KB)
any other value = single-sided 40 tracks diskette, 8 sectors per track
(160 KB)

Version 2 of the "1.44 MB feature" defines three additional specific,
decimal values:

144 = double-sided 80 tracks diskette, 18 sectors per track (1.44 MB)
72 = double-sided 80 tracks diskette, 9 sectors per track (720 KB)
12 = double-sided 80 tracks diskette, 15 sectors per track (1.2 MB)

Finally. version 2 of the 1.44 MB feature supports this media byte:

17 = double-sided 80 tracks diskette, 9 sectors per track (720 KB)
as used by "Personal CP/M Plus 2.0". Note that the ordering of
data on the diskette for this format differs from the ordering
on 720 Kb diskettes with media byte value 72.

Have fun,
Freek.