Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
cpmtools used with a floppy disk image of CP/M-86 does not work ?!
448 views
Skip to first unread message
Peter Dassow
Aug 11, 2012, 11:07:59 AM8/11/12
to
Hi,
I am not able to use cpmtools with a floppy disk image file, which can
be used for VMWare or even VirtualBox.
I was using this command for showing all directory entries:
cpmls -f cpm86-144feat imagefile
But it does not show any useful info (instead just junk).
Is the existing diskdefs entry cpm86-144feat incorrect ?
# CP/M 86 on 1.44MB floppies
diskdef cpm86-144feat
seclen 512
tracks 160
sectrk 18
blocksize 4096
maxdir 256
skew 1
boottrk 2
os 3
end
Or does the existing (and working) disk image files have a wrong
sector/track order ?
I am totally unsure, because I even wrote a small utility to split the
sector order to a different result:
I expected this sector order (C=Cylinder, H=Head) in VMWare/Virtualbox
disk images:
C0H0 C0H1 C1H0 C1H1 C2H0 C2H1 ... up to C79H0, C79H1
The new result was
C0H0 C1H0 C2H0 C3H0 C4H0 C5H0 ... up to C78H1, C79H1
But this doesn't help to get a correct cpmls result.
Am I wrong and a skew is existing for CP/M-86 floppy disks ???
Regards
Peter
I am not able to use cpmtools with a floppy disk image file, which can
be used for VMWare or even VirtualBox.
I was using this command for showing all directory entries:
cpmls -f cpm86-144feat imagefile
But it does not show any useful info (instead just junk).
Is the existing diskdefs entry cpm86-144feat incorrect ?
# CP/M 86 on 1.44MB floppies
diskdef cpm86-144feat
seclen 512
tracks 160
sectrk 18
blocksize 4096
maxdir 256
skew 1
boottrk 2
os 3
end
Or does the existing (and working) disk image files have a wrong
sector/track order ?
I am totally unsure, because I even wrote a small utility to split the
sector order to a different result:
I expected this sector order (C=Cylinder, H=Head) in VMWare/Virtualbox
disk images:
C0H0 C0H1 C1H0 C1H1 C2H0 C2H1 ... up to C79H0, C79H1
The new result was
C0H0 C1H0 C2H0 C3H0 C4H0 C5H0 ... up to C78H1, C79H1
But this doesn't help to get a correct cpmls result.
Am I wrong and a skew is existing for CP/M-86 floppy disks ???
Regards
Peter
Peter Dassow
Aug 12, 2012, 8:42:20 AM8/12/12
to
On 11.08.2012 17:07, Peter Dassow wrote:
> Hi,
>
> I am not able to use cpmtools with a floppy disk image file, which can
> be used for VMWare or even VirtualBox.
> I was using this command for showing all directory entries:
> cpmls -f cpm86-144feat imagefile
> But it does not show any useful info (instead just junk).
> [...]
> Hi,
>
> I am not able to use cpmtools with a floppy disk image file, which can
> be used for VMWare or even VirtualBox.
> I was using this command for showing all directory entries:
> cpmls -f cpm86-144feat imagefile
> But it does not show any useful info (instead just junk).
> I expected this sector order (C=Cylinder, H=Head) in VMWare/Virtualbox
> disk images:
> C0H0 C0H1 C1H0 C1H1 C2H0 C2H1 ... up to C79H0, C79H1
> The new result was
> C0H0 C1H0 C2H0 C3H0 C4H0 C5H0 ... up to C78H1, C79H1
>
> But this doesn't help to get a correct cpmls result.
I had made a mistake in my utility program I wrote. Now it works, track
> disk images:
> C0H0 C0H1 C1H0 C1H1 C2H0 C2H1 ... up to C79H0, C79H1
> The new result was
> C0H0 C1H0 C2H0 C3H0 C4H0 C5H0 ... up to C78H1, C79H1
>
> But this doesn't help to get a correct cpmls result.
order as expected above. I was able to use cpmls (cpmtools) now also for
my VMWare/Virtualbox floppy images.
Again, see my blog ( www.z80.eu/blog/ ) for the full story...
Regards
Peter
Uwe Nass
Aug 13, 2012, 5:38:16 AM8/13/12
to Peter Dassow
I have a similar problem. I can read a CP/M-86 3.5" floppy disk
directly with VmWare, accessing the floppy drive directly. I have,
of course, implemented the 1.44 MB feature by Freek Heite. But...
using "cpmtools" with:
cpmls -f cpm86-144feat /dev/fd0
gives only:
0:
cp/m-86.144
That's all. Is it really nesseccary to convert the disk via your tool,
or is something wrong with the diskdefs definition file?
Any help appreciated,
Uwe.
Peter Dassow
Aug 14, 2012, 9:56:26 AM8/14/12
to
Am 13.08.2012 11:38, schrieb Uwe Nass:
> Peter Dassow wrote:
>> On 11.08.2012 17:07, Peter Dassow wrote:
>>> I expected this sector order (C=Cylinder, H=Head) in VMWare/Virtualbox
>>> disk images:
>>> C0H0 C0H1 C1H0 C1H1 C2H0 C2H1 ... up to C79H0, C79H1
>>> The new result was
>>> C0H0 C1H0 C2H0 C3H0 C4H0 C5H0 ... up to C78H1, C79H1
>>>
> Peter Dassow wrote:
>> On 11.08.2012 17:07, Peter Dassow wrote:
>>> I expected this sector order (C=Cylinder, H=Head) in VMWare/Virtualbox
>>> disk images:
>>> C0H0 C0H1 C1H0 C1H1 C2H0 C2H1 ... up to C79H0, C79H1
>>> The new result was
>>> C0H0 C1H0 C2H0 C3H0 C4H0 C5H0 ... up to C78H1, C79H1
>>>
> I have a similar problem. I can read a CP/M-86 3.5" floppy disk
> directly with VmWare, accessing the floppy drive directly. I have,
> of course, implemented the 1.44 MB feature by Freek Heite. But...
> using "cpmtools" with:
>
> cpmls -f cpm86-144feat /dev/fd0
>
> gives only:
>
> 0:
> cp/m-86.144
>
> That's all. Is it really nesseccary to convert the disk via your tool,
> or is something wrong with the diskdefs definition file?
It's like I already expected - you just have to read my blog ;-)
> directly with VmWare, accessing the floppy drive directly. I have,
> of course, implemented the 1.44 MB feature by Freek Heite. But...
> using "cpmtools" with:
>
> cpmls -f cpm86-144feat /dev/fd0
>
> gives only:
>
> 0:
> cp/m-86.144
>
> That's all. Is it really nesseccary to convert the disk via your tool,
> or is something wrong with the diskdefs definition file?
Track order is different - cpmtools expects no alternating heads in the
given image file. So there are two possibilities... using my tools to
convert the image or modifying the source code of cpmtools.
I guess you can't change track/head order just by modifying a diskdefs
entry...
Regards
Peter
Uwe Nass
Aug 16, 2012, 5:31:59 AM8/16/12
to Peter Dassow
at least my problem is solved! I had to compile cpmtools
with libdsk. That's all.
Thanks again,
Uwe.
Peter Dassow
Aug 16, 2012, 2:20:04 PM8/16/12
to
On 16.08.2012 11:31, Uwe Nass wrote:
>> Track order is different - cpmtools expects no alternating heads in the
>> given image file. So there are two possibilities... using my tools to
>> convert the image or modifying the source code of cpmtools.
>> I guess you can't change track/head order just by modifying a diskdefs
>> entry...
>>
>> Track order is different - cpmtools expects no alternating heads in the
>> given image file. So there are two possibilities... using my tools to
>> convert the image or modifying the source code of cpmtools.
>> I guess you can't change track/head order just by modifying a diskdefs
>> entry...
>>
> Hi all,
>
> at least my problem is solved! I had to compile cpmtools
> with libdsk. That's all.
>
> Thanks again,
Uwe, I am a bit surprised now. I guessed you would like to work with
>
> at least my problem is solved! I had to compile cpmtools
> with libdsk. That's all.
>
> Thanks again,
VMWare/VirtualBox Floppy Disk Image files ... now you told here, you
have to compile cpmtools ? Is your last comment related with the
interpreting/reading problem of the disks ?
I took the ready compiled cpmtools version from
http://www.cpm8680.com/cpmtools/index.htm#windows ... I was NOT able to
read the image files directly ... ?!?
Regards
Peter
Uwe Nass
Aug 17, 2012, 3:47:56 AM8/17/12
to Peter Dassow
sorry, if I have surprised you! But, as I have written
in my first message to this thread, I always wanted to
read the floppy disk directly, i.e. via /dev/fd0. This
can be done without any problems with VmWare (NOT with
vbox (?)). In order to do the same with cpmtools, you
have to compile it with libdsk. How to do this is described
in the cpmtools package (use --with-libdsk option when
starting the ./configure process).
Regards,
Uwe.
Peter Dassow
Aug 17, 2012, 5:21:23 AM8/17/12
to
On 17.08.2012 09:47, Uwe Nass wrote:
>>
>> Uwe, I am a bit surprised now. I guessed you would like to work with
>> VMWare/VirtualBox Floppy Disk Image files ... now you told here, you
>> have to compile cpmtools ? Is your last comment related with the
>> interpreting/reading problem of the disks ?
>> I took the ready compiled cpmtools version from
>> http://www.cpm8680.com/cpmtools/index.htm#windows ... I was NOT able to
>> read the image files directly ... ?!?
>>
>>
>> Uwe, I am a bit surprised now. I guessed you would like to work with
>> VMWare/VirtualBox Floppy Disk Image files ... now you told here, you
>> have to compile cpmtools ? Is your last comment related with the
>> interpreting/reading problem of the disks ?
>> I took the ready compiled cpmtools version from
>> http://www.cpm8680.com/cpmtools/index.htm#windows ... I was NOT able to
>> read the image files directly ... ?!?
>>
> Hi Peter,
>
> sorry, if I have surprised you! But, as I have written
> in my first message to this thread, I always wanted to
> read the floppy disk directly, i.e. via /dev/fd0. This
> can be done without any problems with VmWare (NOT with
> vbox (?)). In order to do the same with cpmtools, you
> have to compile it with libdsk. How to do this is described
> in the cpmtools package (use --with-libdsk option when
> starting the ./configure process).
Ok, I understand. So you will NOT be faced with structural differences
>
> sorry, if I have surprised you! But, as I have written
> in my first message to this thread, I always wanted to
> read the floppy disk directly, i.e. via /dev/fd0. This
> can be done without any problems with VmWare (NOT with
> vbox (?)). In order to do the same with cpmtools, you
> have to compile it with libdsk. How to do this is described
> in the cpmtools package (use --with-libdsk option when
> starting the ./configure process).
between a VMWare *image* and a cpmtools *image*. AFAIK reading directly
floppy disks via cpmtools does work without track/head geometry
problems, because there is nothing to be "ordered" in a different way.
My problem was *only* related with the structural different *image* files.
Regards
Peter
s_dub...@yahoo.com
Aug 17, 2012, 3:37:22 PM8/17/12
to Peter Dassow
On Friday, August 17, 2012 2:47:56 AM UTC-5, Uwe Nass wrote:
> Peter Dassow wrote:
>
> > On 16.08.2012 11:31, Uwe Nass wrote:
>
[snipped]
> Peter Dassow wrote:
>
> > On 16.08.2012 11:31, Uwe Nass wrote:
>
>
> Hi Peter,
>
>
>
> sorry, if I have surprised you! But, as I have written
>
> in my first message to this thread, I always wanted to
>
> read the floppy disk directly, i.e. via /dev/fd0. This
>
> can be done without any problems with VmWare (NOT with
>
> vbox (?)). In order to do the same with cpmtools, you
>
> have to compile it with libdsk. How to do this is described
>
> in the cpmtools package (use --with-libdsk option when
>
> starting the ./configure process).
>
>
>
> Regards,
>
>
>
> Uwe.
Where is libdsk found?
> Hi Peter,
>
>
>
> sorry, if I have surprised you! But, as I have written
>
> in my first message to this thread, I always wanted to
>
> read the floppy disk directly, i.e. via /dev/fd0. This
>
> can be done without any problems with VmWare (NOT with
>
> vbox (?)). In order to do the same with cpmtools, you
>
> have to compile it with libdsk. How to do this is described
>
> in the cpmtools package (use --with-libdsk option when
>
> starting the ./configure process).
>
>
>
> Regards,
>
>
>
> Uwe.
Thxs,
Steve
s_dub...@yahoo.com
Aug 18, 2012, 8:26:54 PM8/18/12
to
On Friday, August 17, 2012 2:37:22 PM UTC-5, (unknown) wrote:
> On Friday, August 17, 2012 2:47:56 AM UTC-5, Uwe Nass wrote:
>
> > Peter Dassow wrote:
>
> >
>
> > > On 16.08.2012 11:31, Uwe Nass wrote:
>
[snip]
> On Friday, August 17, 2012 2:47:56 AM UTC-5, Uwe Nass wrote:
>
> > Peter Dassow wrote:
>
> >
>
> > > On 16.08.2012 11:31, Uwe Nass wrote:
>
>
>
> Where is libdsk found?
>
So it is here - http://www.seasip.demon.co.uk/Unix/LibDsk/
But the debian version has a broken link, and I've got trouble with the generic tar.gz --
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
-Steve
>
>
> Thxs,
>
>
>
> Steve
Ivan Shmakov
Aug 19, 2012, 1:02:38 AM8/19/12
to
>>>>> s dubrovich <s_dub...@yahoo.com> writes:
>>>>> On Friday, August 17, 2012 2:37:22 PM UTC-5, (unknown) wrote:
[...]
>>>>> On Friday, August 17, 2012 2:37:22 PM UTC-5, (unknown) wrote:
>> Where is libdsk found?
> So it is here - http://www.seasip.demon.co.uk/Unix/LibDsk/
> But the debian version has a broken link,
packages provided by a third party.)
> and I've got trouble with the generic tar.gz --
> gzip: stdin: not in gzip format
> tar: Child returned status 1
> tar: Error is not recoverable: exiting now
$ tar -ztv < seasip.info/Unix/LibDsk/libdsk-1.2.1.tar.gz
drwxrwxrwx 500/500 0 2008-01-24 01:29 libdsk-1.2.1/
-rw-r--r-- 500/500 13196 2008-01-24 01:29 libdsk-1.2.1/Makefile.in
drwxr--r-- 500/500 0 2008-01-24 01:29 libdsk-1.2.1/config/
-rwxr--r-- 500/500 39923 2004-12-20 07:44 libdsk-1.2.1/config/config.guess
-rwxr--r-- 500/500 29708 2004-12-20 07:44 libdsk-1.2.1/config/config.sub
-rwxr--r-- 500/500 5598 2001-06-23 23:50 libdsk-1.2.1/config/install-sh
-rwxr--r-- 500/500 94197 2002-04-20 07:19 libdsk-1.2.1/config/ltconfig
-rw-r--r-- 500/500 145396 2004-12-20 07:44 libdsk-1.2.1/config/ltmain.sh
-rwxr--r-- 500/500 6283 2001-06-23 23:50 libdsk-1.2.1/config/missing
-rwxr--r-- 500/500 722 2001-06-23 23:50 libdsk-1.2.1/config/mkinstalldirs
...
$ tar -ztv < seasip.info/Unix/LibDsk/libdsk-1.3.3.tar.gz
drwxr-xr-x 1000/1000 0 2010-09-19 20:55 libdsk-1.3.3/
drwxr-xr-x 1000/1000 0 2010-09-19 20:55 libdsk-1.3.3/win16bc5/
-rwxr--r-- 1000/1000 403 2006-01-22 03:23 libdsk-1.3.3/win16bc5/config.h
-rwxr--r-- 1000/1000 87882 2007-06-10 06:29 libdsk-1.3.3/win16bc5/libdsk.ide
-rw-r--r-- 1000/1000 477 2003-01-11 19:39 libdsk-1.3.3/win16bc5/libdsk.def
drwxr-xr-x 1000/1000 0 2010-09-19 20:55 libdsk-1.3.3/win32bc5/
-rwxr--r-- 1000/1000 328 2005-01-19 06:05 libdsk-1.3.3/win32bc5/config.h
-rwxr--r-- 1000/1000 124174 2007-06-10 06:49 libdsk-1.3.3/win32bc5/libdsk.ide
-rwxr--r-- 1000/1000 130 2002-12-04 05:04 libdsk-1.3.3/win32bc5/libdsk.def
-rw-r--r-- 1000/1000 24612 2010-06-29 02:46 libdsk-1.3.3/acinclude.m4
...
$ file -- \
seasip.info/Unix/LibDsk/libdsk-1.2.1.tar.gz \
seasip.info/Unix/LibDsk/libdsk-1.3.3.tar.gz
seasip.info/Unix/LibDsk/libdsk-1.2.1.tar.gz: gzip compressed data, from Unix, last modified: Thu Jan 24 01:30:02 2008, max compression
seasip.info/Unix/LibDsk/libdsk-1.3.3.tar.gz: gzip compressed data, from Unix, last modified: Sun Sep 19 20:55:18 2010, max compression
$ sha1sum -- \
seasip.info/Unix/LibDsk/libdsk-1.2.1.tar.gz \
seasip.info/Unix/LibDsk/libdsk-1.3.3.tar.gz
8d02a8ed0021a34a13c061858ca026c385c11c5b seasip.info/Unix/LibDsk/libdsk-1.2.1.tar.gz
5ec36eb90cc55ba74b68b1529a15c51d60d382fe seasip.info/Unix/LibDsk/libdsk-1.3.3.tar.gz
$
--
FSF associate member #7257 http://sf-day.org/
s_dub...@yahoo.com
Aug 20, 2012, 12:02:38 AM8/20/12
to
On Sunday, August 19, 2012 12:02:38 AM UTC-5, Ivan Shmakov wrote:
> >>>>> s dubrovich <s_dub...@yahoo.com> writes:
>
> >>>>> On Friday, August 17, 2012 2:37:22 PM UTC-5, (unknown) wrote:
>
>
>
> [...]
>
>
>
> >> Where is libdsk found?
>
>
>
> > So it is here - http://www.seasip.demon.co.uk/Unix/LibDsk/
>
>
>
> > But the debian version has a broken link,
>
>
>
> There's no libdsk in Debian. (Although I see there're .deb
>
> packages provided by a third party.)
>
Thanks for your help. Is that 3rd party link reachable by you? I can't reach it from here,
> >>>>> s dubrovich <s_dub...@yahoo.com> writes:
>
> >>>>> On Friday, August 17, 2012 2:37:22 PM UTC-5, (unknown) wrote:
>
>
>
> [...]
>
>
>
> >> Where is libdsk found?
>
>
>
> > So it is here - http://www.seasip.demon.co.uk/Unix/LibDsk/
>
>
>
> > But the debian version has a broken link,
>
>
>
> There's no libdsk in Debian. (Although I see there're .deb
>
> packages provided by a third party.)
>
"
Unable to load page
Problem occurred while loading the URL http://www.youmustbejoking.demon.co.uk/progs.packages.html
Cannot resolve hostname
"
Could be my ISP filtering it, drat.
>
>
> > and I've got trouble with the generic tar.gz --
>
>
>
> > gzip: stdin: not in gzip format
>
> > tar: Child returned status 1
>
> > tar: Error is not recoverable: exiting now
>
current version of gzip 1.3.12-9
and tar 1.23-3
hmm,
Steve
>
>
> No such problem here. E. g.:
>
[snip]
>
> No such problem here. E. g.:
>
Ivan Shmakov
Aug 21, 2012, 1:57:38 PM8/21/12
to
>>>>> s dubrovich <s_dub...@yahoo.com> writes:
>>>>> On Sunday, August 19, 2012 12:02:38 AM UTC-5, Ivan Shmakov wrote:
>>>>> s dubrovich <s_dub...@yahoo.com> writes:
[Cross-posting to news:comp.os.linux.misc and
>>>>> On Sunday, August 19, 2012 12:02:38 AM UTC-5, Ivan Shmakov wrote:
>>>>> s dubrovich <s_dub...@yahoo.com> writes:
news:alt.os.linux.debian, and setting Followup-To: there, for
possibly better suggestions.]
[...]
>>> But the debian version has a broken link,
>> There's no libdsk in Debian. (Although I see there're .deb packages
>> provided by a third party.)
> Thanks for your help. Is that 3rd party link reachable by you?
> I can't reach it from here,
> Could be my ISP filtering it, drat.
always check the target with, say, http://lg.he.net/.
[...]
>>> gzip: stdin: not in gzip format
>>> tar: Child returned status 1
>>> tar: Error is not recoverable: exiting now
>> $ sha1sum -- \
>> seasip.info/Unix/LibDsk/libdsk-1.2.1.tar.gz \
>> seasip.info/Unix/LibDsk/libdsk-1.3.3.tar.gz
>> 8d02a8ed0021a34a13c061858ca026c385c11c5b seasip.info/Unix/LibDsk/libdsk-1.2.1.tar.gz
>> 5ec36eb90cc55ba74b68b1529a15c51d60d382fe seasip.info/Unix/LibDsk/libdsk-1.3.3.tar.gz
>> $
>> seasip.info/Unix/LibDsk/libdsk-1.2.1.tar.gz \
>> seasip.info/Unix/LibDsk/libdsk-1.3.3.tar.gz
>> 8d02a8ed0021a34a13c061858ca026c385c11c5b seasip.info/Unix/LibDsk/libdsk-1.2.1.tar.gz
>> 5ec36eb90cc55ba74b68b1529a15c51d60d382fe seasip.info/Unix/LibDsk/libdsk-1.3.3.tar.gz
>> $
> Thanks, I'm able to unpack it on my other winxp box, but not under
> debian for some reason.
Did you check the file(1) and sha1sum(1) output against the one
> debian for some reason.
I've provided?
> current version of gzip 1.3.12-9 and tar 1.23-3.
These are up-to-date versions from Debian GNU/Linux Squeeze, and
I've experienced no issues with them.
s_dub...@yahoo.com
Aug 21, 2012, 10:10:40 PM8/21/12
to
On Tuesday, August 21, 2012 12:57:38 PM UTC-5, Ivan Shmakov wrote:
> >>>>> s dubrovich <s_dub...@yahoo.com> writes:
>
> >>>>> On Sunday, August 19, 2012 12:02:38 AM UTC-5, Ivan Shmakov wrote:
>
> >>>>> s dubrovich <s_dub...@yahoo.com> writes:
>
>
>
> [Cross-posting to news:comp.os.linux.misc and
>
> news:alt.os.linux.debian, and setting Followup-To: there, for
>
> possibly better suggestions.]
>
>
>
> [...]
>
>
>
> >>> But the debian version has a broken link,
>
>
>
> >> There's no libdsk in Debian. (Although I see there're .deb packages
>
> >> provided by a third party.)
>
>
>
> > Thanks for your help. Is that 3rd party link reachable by you?
>
>
>
> Unfortunately, no.
>
>
>
> > I can't reach it from here,
>
>
>
> [...]
>
>
>
> > Could be my ISP filtering it, drat.
>
>
>
> If any connectivity or filtering issues are suspected, one can
>
> always check the target with, say, http://lg.he.net/.
>
>
Thanks for that useful tool.
> >>>>> s dubrovich <s_dub...@yahoo.com> writes:
>
> >>>>> On Sunday, August 19, 2012 12:02:38 AM UTC-5, Ivan Shmakov wrote:
>
> >>>>> s dubrovich <s_dub...@yahoo.com> writes:
>
>
>
> [Cross-posting to news:comp.os.linux.misc and
>
> news:alt.os.linux.debian, and setting Followup-To: there, for
>
> possibly better suggestions.]
>
>
>
> [...]
>
>
>
> >>> But the debian version has a broken link,
>
>
>
> >> There's no libdsk in Debian. (Although I see there're .deb packages
>
> >> provided by a third party.)
>
>
>
> > Thanks for your help. Is that 3rd party link reachable by you?
>
>
>
> Unfortunately, no.
>
>
>
> > I can't reach it from here,
>
>
>
> [...]
>
>
>
> > Could be my ISP filtering it, drat.
>
>
>
> If any connectivity or filtering issues are suspected, one can
>
> always check the target with, say, http://lg.he.net/.
>
>
Apparently, for example, my ISP filters www.project-fbin.hostoi.com because the domain hostoi.com is entered into a Black List re: URIBL.COM, (I have yet to talk to my isp about what they are doing but by using a proxy server, proxy.org, does get me there). (a small-c project)
>
> [...]
>
>
>
> >>> gzip: stdin: not in gzip format
>
>
>
> >>> tar: Child returned status 1
>
>
>
> >>> tar: Error is not recoverable: exiting now
>
>
>
> >> $ sha1sum -- \
>
> >> seasip.info/Unix/LibDsk/libdsk-1.2.1.tar.gz \
>
> >> seasip.info/Unix/LibDsk/libdsk-1.3.3.tar.gz
>
> >> 8d02a8ed0021a34a13c061858ca026c385c11c5b seasip.info/Unix/LibDsk/libdsk-1.2.1.tar.gz
>
> >> 5ec36eb90cc55ba74b68b1529a15c51d60d382fe seasip.info/Unix/LibDsk/libdsk-1.3.3.tar.gz
>
> >> $
>
>
>
> > Thanks, I'm able to unpack it on my other winxp box, but not under
>
> > debian for some reason.
>
>
>
> Did you check the file(1) and sha1sum(1) output against the one
>
> I've provided?
>
$ file -- libdsk-1.2.1.tar.gz
libdsk-1.2.1.tar.gz: tar archive
$ sha1sum -- libdsk-1.2.1.tar.gz
bff5b7f52b0efde43babc1ad1f9ce4287e6226bd libdsk-1.2.1.tar.gz
$ file -- libdsk-1.3.3.tar.gz
libdsk-1.3.3.tar.gz: tar archive
$ sha1sum -- libdsk-1.3.3.tar.gz
8868a4c066ac6d16f442f8595fabbb7b85961339 libdsk-1.3.3.tar.gz
I'm not sure where to turn to next, so your advice is appreciated.
Steve
Ivan Shmakov
Aug 22, 2012, 7:59:38 AM8/22/12
to
>>>>> s dubrovich <s_dub...@yahoo.com> writes:
>>>>> On Tuesday, August 21, 2012 12:57:38 PM UTC-5, Ivan Shmakov wrote:
>>>>> s dubrovich <s_dub...@yahoo.com> writes:
[...]
>>>>> On Tuesday, August 21, 2012 12:57:38 PM UTC-5, Ivan Shmakov wrote:
>>>>> s dubrovich <s_dub...@yahoo.com> writes:
>>> Thanks, I'm able to unpack it on my other winxp box, but not under
>>> debian for some reason.
>> Did you check the file(1) and sha1sum(1) output against the one I've
>> provided?
> Just did, and they are different..
> $ file -- libdsk-1.2.1.tar.gz
> libdsk-1.2.1.tar.gz: tar archive
> I'm not sure where to turn to next, so your advice is appreciated.
news:comp.infosystems.www.misc. (AIUI, this discussion has
little to do with CP/M, right?)
Bill Marcum
Sep 1, 2012, 1:25:46 PM9/1/12
to
On 08/21/2012 10:10 PM, s_dub...@yahoo.com wrote:
> Just did, and they are different..
>
> $ file -- libdsk-1.2.1.tar.gz
> libdsk-1.2.1.tar.gz: tar archive
>
> $ sha1sum -- libdsk-1.2.1.tar.gz
> bff5b7f52b0efde43babc1ad1f9ce4287e6226bd libdsk-1.2.1.tar.gz
>
> $ file -- libdsk-1.3.3.tar.gz
> libdsk-1.3.3.tar.gz: tar archive
>
> $ sha1sum -- libdsk-1.3.3.tar.gz
> 8868a4c066ac6d16f442f8595fabbb7b85961339 libdsk-1.3.3.tar.gz
>
> I'm not sure where to turn to next, so your advice is appreciated.
>
'file' says they are tar archives, it doesn't say they are gzipped.
> Just did, and they are different..
>
> $ file -- libdsk-1.2.1.tar.gz
> libdsk-1.2.1.tar.gz: tar archive
>
> $ sha1sum -- libdsk-1.2.1.tar.gz
> bff5b7f52b0efde43babc1ad1f9ce4287e6226bd libdsk-1.2.1.tar.gz
>
> $ file -- libdsk-1.3.3.tar.gz
> libdsk-1.3.3.tar.gz: tar archive
>
> $ sha1sum -- libdsk-1.3.3.tar.gz
> 8868a4c066ac6d16f442f8595fabbb7b85961339 libdsk-1.3.3.tar.gz
>
> I'm not sure where to turn to next, so your advice is appreciated.
>
Maybe your ftp client unzipped them, or they were named wrong on the
server.
s_dub...@yahoo.com
Sep 1, 2012, 2:12:38 PM9/1/12
to
Steve
V1050
Sep 5, 2012, 6:30:08 AM9/5/12
to
Hi folks, can i jump in here with some situation related to cpmtools?
I can copy individual ASCII files from a .DSK image (V1050) to my host system (Windows 7) using a precompiled cpmtools binary helped by the cygwin DLL. However, when i turn around and try to copy the same files (or any ASCII files) back to the disk, they arrive empty. The files arrive, the names arrive, but they arrive empty, or with only about 8 bytes that don't show up on the screen. Cpmtools acts like there's nothing wrong. No error messages. Anybody know why?
TIA
~Still
I can copy individual ASCII files from a .DSK image (V1050) to my host system (Windows 7) using a precompiled cpmtools binary helped by the cygwin DLL. However, when i turn around and try to copy the same files (or any ASCII files) back to the disk, they arrive empty. The files arrive, the names arrive, but they arrive empty, or with only about 8 bytes that don't show up on the screen. Cpmtools acts like there's nothing wrong. No error messages. Anybody know why?
TIA
~Still
Wayne Warthen
Sep 5, 2012, 12:29:24 PM9/5/12
to
-Wayne
V1050
Sep 6, 2012, 5:32:30 AM9/6/12
to
cpmcp -f v1050 V1050B.DSK v1050files 0:SENT.BAS
But this is how the command line should look:
cpmcp -f v1050 V1050B.DSK v1050files\SENT.BAS 0:SENT.BAS
I was missing the actual file to send. So the first command was creating SENT.BAS on the .DSK disk, but it would be empty. Since cpmtools was not complaining, i thought my command line was constructed right. I think what happened was my first attempts were to send multiple files, like this:
cpmcp -f v1050 V1050B.DSK v1050files\*.BAS 0:
When that did not work, i was experimenting with all kinds of variations and struck upon the one that created the empty SENT.BAS file. So if it's true that it's not possible to upload multiple files then it appears i've both matched and exhausted the possibilities of the cpmtools command line. Theoretically, everything is ok...unless others (but not me) are able to upload multiple files at a time.
It's funny how somebody saying they CAN do something kind of helps others figure out how they can do it also!
Thanks very much!
(all files) coming out of a disk and into a subfolder.
cpmcp -f v1050 v1050dsk\V1050B.DSK 0:*.* v1050files\V1050BDSK
Going the other way looks like this:
cpmcp -f v1050 v1050dsk\V1050B.DSK v1050files\V1050BDSK 0:SAMPLE
Ole Christensen
Sep 6, 2012, 7:43:58 AM9/6/12
to
on 2012-09-06 11:32, V1050 wrote:
> So if it's true that it's not possible to upload multiple
> files then it appears i've both matched and exhausted the
> possibilities of the cpmtools command line.
> Theoretically, everything is ok...unless others
> (but not me) are able to upload multiple files at a time.
Don't know how to do this in a .BAT-file,
> So if it's true that it's not possible to upload multiple
> files then it appears i've both matched and exhausted the
> possibilities of the cpmtools command line.
> Theoretically, everything is ok...unless others
> (but not me) are able to upload multiple files at a time.
but with a *nix shell, (bash), one could do:
ws2rtf.sh:
#!/bin/bash
# ----------------------------------------------------------
if [ -z $1 ] # If no arg...
then
echo "$0" " file(s) to convert,... exmpl. *.doc"
exit 1
fi
# ----------------------------------------------------------
until [ -z "$1" ] # Until all parameters used up...
do
ws_converter "$1" "$1.rtf" "/R"
shift # next arg
done
# ----------------------------------------------------------
exit 0
and run it like:
ole@orion:~/test$ sh ws2rtf.sh *.WS
ws_converter 1.30 : File Converter from WS to TXT, HTML or RTF
2010-2011 by Ole Christensen.
converting ms-80.WS to ms-80.WS.rtf
from WS format to rtf document
WordStar file opened:
conversion summary
data read :4,740 bytes
data written:5,879 bytes
ws_converter 1.30 : File Converter from WS to TXT, HTML or RTF
2010-2011 by Ole Christensen.
converting Sl5.WS to Sl5.WS.rtf
from WS format to rtf document
WordStar file opened:
conversion summary
data read :168,041 bytes
data written:200,429 bytes
ws_converter 1.30 : File Converter from WS to TXT, HTML or RTF
2010-2011 by Ole Christensen.
converting WS_EXAMP.WS to WS_EXAMP.WS.rtf
from WS format to rtf document
WordStar file opened:
conversion summary
data read :12,449 bytes
data written:14,632 bytes
ole@orion:~/test$
good luck,...!
<ole>
Wayne Warthen
Sep 6, 2012, 10:38:03 AM9/6/12
to
Yeah, those command lines look better. I think you are on the right track now.
It is possible to copy all of the files in a Windows directory over to your CP/M disk image. The following command line should work:
cpmcp -f v1050 v1050dsk/V1050B.DSK v1050files/V1050BDSK/*.* 0:
Note the use of forward slashes instead of backslashes. Even though you are running this on Windows, it is a port from Unix and prefers the forward slashes.
-Wayne
It is possible to copy all of the files in a Windows directory over to your CP/M disk image. The following command line should work:
cpmcp -f v1050 v1050dsk/V1050B.DSK v1050files/V1050BDSK/*.* 0:
Note the use of forward slashes instead of backslashes. Even though you are running this on Windows, it is a port from Unix and prefers the forward slashes.
-Wayne
V1050
Sep 6, 2012, 2:12:19 PM9/6/12
to
@Wayne
Yes! This works!
cpmcp -f v1050 v1050dsk/V1050B.DSK v1050files/V1050BDSK/*.* 0:
I remember reading something about the reversibility of the slashes in the documentation but didn't catch how it would be necessary to upload multiple files like the above example.
I might point out though while we're here, that while the above example did work, this slight variation did not:
cpmcp -f v1050 v1050dsk/V1050B.DSK v1050files/V1050BDSK/*.BAS 0:
On the other hand, this variation will work when going the other way...when copying .BAS files down from the .DSK to the host. So unless i'm mistaken again, i'm happy to at least be able to copy to .DSK either single, or all files in a folder.
Thanks very much!
Yes! This works!
cpmcp -f v1050 v1050dsk/V1050B.DSK v1050files/V1050BDSK/*.* 0:
I might point out though while we're here, that while the above example did work, this slight variation did not:
cpmcp -f v1050 v1050dsk/V1050B.DSK v1050files/V1050BDSK/*.BAS 0:
On the other hand, this variation will work when going the other way...when copying .BAS files down from the .DSK to the host. So unless i'm mistaken again, i'm happy to at least be able to copy to .DSK either single, or all files in a folder.
Thanks very much!
V1050
Sep 6, 2012, 3:00:51 PM9/6/12
to
@everyone
More debugging has revealed that while the following example does not work...
cpmcp -f v1050 v1050dsk/V1050B.DSK v1050files/V1050BDSK/*.BAS 0:
...the following example does:
cpmcp -f v1050 v1050dsk/V1050B.DSK v1050files/V1050BDSK/*.bas 0:
So cpmtools *does not like CAPS in the extension. I apologize if this was in the documentation and i missed it. But i'm glad i got that straightened out. So here's a summary of what was learned here:
1.)use unix-style backslashes when copying multiple files like *.*
2.)use small letters in the extention when copying multiple files like *.bas
~Still
More debugging has revealed that while the following example does not work...
cpmcp -f v1050 v1050dsk/V1050B.DSK v1050files/V1050BDSK/*.BAS 0:
cpmcp -f v1050 v1050dsk/V1050B.DSK v1050files/V1050BDSK/*.bas 0:
So cpmtools *does not like CAPS in the extension. I apologize if this was in the documentation and i missed it. But i'm glad i got that straightened out. So here's a summary of what was learned here:
1.)use unix-style backslashes when copying multiple files like *.*
2.)use small letters in the extention when copying multiple files like *.bas
~Still
Wayne Warthen
Sep 6, 2012, 8:04:34 PM9/6/12
to
Interesting...
UNIX uses case sensitive file names and cpmtools is (under the covers) a unix application. I wonder if it is simply doing a case sensitive file name comparison.
-Wayne
UNIX uses case sensitive file names and cpmtools is (under the covers) a unix application. I wonder if it is simply doing a case sensitive file name comparison.
-Wayne
0 new messages