MultiDOS Help
14 messages in this thread
I'm having trouble with MultiDOS. I set it up as I understand the
directions, say PCMOUNTALL, and nothing much seems to happen, then PCFORMAT
Drive df0 Name Test, and my system goes to sleep and doesn't come back.
Can you help or put me into contact with someone who can?
Thanks in advance.
John
John,
I'm sorry, I don't know what MultiDOS is, thus don't know how to
use it or what might be wrong with it.
Was there a doc file with it, and if so, did you follow the
instructions exactly?
Don
Don,
Yes there is a doc file, and I _thought_ I followed it exactly. That's why
I was confused. I realize you can't be familiar with all shareware. I'll
see who jumps in to help.
John
John-
I have MultiDOS installed on my system. I don't use PCMOUNTALL,
since I don't want to lose my DF0: and DF1: functions. I have MC0: and
MC1: on my mountlist, and use a MOUNT command in my startup-sequence to
mount them. Do you have all the MultiDOS devices added to your MountList?
That might cause some trouble (if you don't)
I don't know why PCFORMAT wouldn't work – it works on my setup.
(^_^) Instead of specifying df0: as the drive, try using md0: or mc0:. I
just formatted a disk using PCFormat mc0: – and it worked fine. I tried it
using df0: and it told me 'Device MD0: not mounted' – which is what I
expected.
Len Lekx
[73300,723]
MultiDos works fine on my system… No mountlist entry either. MultiDos
will automatically switch between handlers when it detects that type of
disk. DF0: can be used for both PC and Amiga disks…… PCMOUNTALL is in
my WBSTARTUP drawer.. that's it! -Jonathan -exit
Johnathan-
> MultiDos will automatically switch between handlers when it detects
that
> type of disk. DF0: can be used for both PC and Amiga disks
I know that. When I first set MultiDos in my system, that's the way I used
it. I ran into trouble, however, when I tried to format an AmyDos disk
under Dos 2.04. It would go through the formatting procedure, but would
return an error on completion. 'Unable to Format Disk'. I don't know if
it's a bug in the way MultiDos handles filesystem switching, or something
inherent in 2.04 – either way, it wouldn't format right. I found I could
correct it by taking PCMountAll out of my Startup-Sequence and mounting
MC0: and MC1: the hard way (Mount MCx:) It works for me, it only adds a
second or two to my startup time, and I can format both Amy and PC disks.
Len Lekx
[73300,723]
Hmmmm… I am also running under 2.04. Never have had a problem.. It
might be having compatibility problems in something else you may have
installed. Kinda like Toolmanager doesn't get along with FMENU..
-Jonathan
Len,
Thanks for the help. I'll give your suggestions a try.
John
> I have MultiDOS installed on my system. I don't use PCMOUNTALL …
Although I can't claim to know what I'm doing WRT MultiDOS, I do use
PCMOUNTALL (Amiga 2000, DOS 2.04, internal DF0: only) and am always amazed
when I can insert and read both Amiga and MSDOS formatted disks in df0:
-MultiDOS seems to sense which format is on the inserted disk and react
appropriately — dunno how or why 🙂 WRT PCFormat — I only did one disk
and don't remember having any particular problems. I did have PCFormat.spc
in the s: directory but couldn't tell you now if that was really necessary.
BTW, I think that when MultiDOS creates a directory on a DOS formatted
disk — it doesn't fully initialize the directory — until the first file
is written into that directory. I had created some directories on a DOS
formatted disk with MultiDOS (but left them empty) and Norton Disk Doctor
objected when checking the disk on a PC. Directories that had at least one
file written did not seem to be a problem.
REC
——
You're right about the empty directories??? I had some problems a while
back, and now that you mention it, that is exactly what was happening.
– db —–> via Whap!
Another thing that I haven't yet completely pinned down —
When using MultiDOS to write files to a MSDOS formatted disk, sometimes
you can end up with files that have directory entrys that Norton Utilities
doesn't like … They are shown as "Not a valid directory entry" — or
something like that — when you look at the directory using Norton
Utilities.
These files show up just fine under a MSDOS 'dir' command and you can
copy, delete, etc. them without a problem (noted so far). In the cases
I've looked at so far, it seems to be some sort of a problem with the MSDOS
directory time stamp (maybe date/time stamp) field e.g. a file with a
creation time of 14:02am. Anyway, after using a 'touch' command to reset
the date/time stamp, Norton Utilities showed the directory entry for the
file just like the other normal entries. Go figure!!
REC
——
Hmmmm. Must be something I'm doing wrong. I think it might be the
mountlist.
Thanks.
John
Well, I'm still kinda mystified myself but I don't think that PCMountALL
gives a hoot about the mountlist 🙂 Not about:
>MountList.MultiDOS 5701 —-rwed 31-Dec-91 15:00:00
: MultiDos v1.12 ) 1990,1991 by Kjell H. Didriksen
anyway because I've done PCMountALL both with that file in devs: and with
the file NOT in devs: (i.e. deleted) and have not been able to see the
slightest difference in operations. Tonight, I'm reading both Amiga and
MSDOS disks in df0: after a PCMountALL WITHOUT Mountlist.MultiDOS in devs:
Go figure!!
REC
——