Re: HD-DOS+ Notes
- From: Maurice Randall <maurice@xxxxxxxxxxx>
- Date: Tue, 28 Feb 2006 14:41:33 GMT
You're very close. The only difference is the order of the bytes.
The F-P command expects high byte first and low byte last. I know
everyone will think this is odd, however, the block (B-x) commands
basically are high byte first as well. The track value in a B-x
command can be considered the high byte and the sector the low byte.
That is why I kept the same order for the F-P command.
So, the correct line 20 is:
I guess nothing will happen if I try to seek beyond the end of file,
except an error message and the pointer remains unchanged.
That's exactly right. The error is $50 - RECORD NOT PRESENT
Will be there any convient way to set the hidden flag not involving a
It's a toggle function. If it's already hidden, it will be made visible.
Isn't the 32 byte filename extension a major compatibility problem?
No, if there are more than 16 characters in the filename, the normal
@$ or LOAD"$",8 commands will only show the first 15 characters plus
an asterisk. This lets the user know the filename is longer than 16
characters. And any software that tries to load the file will work
due to the ending asterisk. The only time this will be a problem is
when there are more than one file with the first 15 characters being
the same. It's up to the individual user to be careful with the choice
of filenames. To show the directory with long filenames:
All the other syntaxes that can be used with @$ can also be used with
@$L such as:
@$L:G* to show all files beginning with G.
The formatting of the listing is done in a way to be neatly arranged
on both a 40 column screen and an 80 column screen. Sorry about the
VIC-20, but 22 columns is just tough to deal with sometimes. :)
@$L doesn't break in the other partitions. It works just as if the
L wasn't there.
The root partition dir is an interresting idea, but why does it differ
from a simple "chroot"? Why make a separate directory for top level
directories, if one could just change the virtual root directory?
Didn't you know there is also a directory for the partitions which is
yet another directory level up? The partition directory is stored in
the system partition and is arranged just like a directory on a disk
with 30 bytes for each directory entry. Each directory entry points
to a partition. It has always been this way with the CMD-HD.
4GB is a huge partition. I think a way to break it up will be handy
for some people. For those who don't like it, just use the one
default root directory. You'll never have to worry about the
Master directory, just pretend it doesn't exist.
It seems to me that this extended partition thing is meant mostly to
store disk image files, or for new software which can cope with the
situation. That's sad. But at least the way of handling those image
files is nice ;-)
No, you can copy files to it and then load and run them just like you
would any other partition. LOAD"FILENAME",8 and RUN works just like
you would expect.
FCOPY can copy files to/from an Extended Native partition just as well
as it can with a regular native partition.
The only problem you will have is with programs that do direct disk
access. But for them, as long as their support files are within the
first 16MB of the partition, they will work also because they will
always put a 0 byte where the high byte of the block address goes.
Programs that expect to find something on track 18 won't work, but
who cares. Those programs don't work in a 1581 or native partition
** Maurice Randall - Click Here Software Co.
** High-Performance for your Commodore
** email: maurice@xxxxxxxxxxx, support@xxxxxxxxxxx
** web: http://cmdrkey.com
- Prev by Date: Re: Yuck!
- Next by Date: Re: Yuck!
- Previous by thread: Re: HD-DOS+ Notes
- Next by thread: warp copy worked fine, now suddenly acting weird