Installing FreeDOS 1.0 on partition other than C:
Wolfi
1.0 supposedly can be installed on a partition other than C:, at least
with the bulk of its files.
However, when doing so (in my case on D:), FreeDOS won't be functional
after an apparently successful installation. Even though that all the
path settings in FDConfig.sys and Autoexec.bat correctly point to D:,
it looks like as if there is still some hardcoded stuff pointing to C:
in some essential system files.
Since Command.com was't found in the first place, I copied
FDConfig.sys to C: in order to improve my chances, but FreeDOS still
doesn't finish its boot-up.
So now my questions:
- can a _working_ FreeDOS 1.0 from fdfullcd.iso _really_ be installed
successfully on a partition _other_ than C:?
- if so, what additional post installation steps need to be taken, in
order to make it actually work?
- if so, how does one also get GEMAPPS off of C: and onto another
(programs/applications/whatever) partition?
I'm usung a multi-boot environment and therefore want to have as
little essential stuff, including FreeDOS and its apps, on C: as
possible.
Thanks
Wolfi
Richard Bonner
> Wolfi
*** What operating system is on the `C' drive? If it's Windows, perhaps
the problem is the NT file system.
Otherwise, FreeDOS may require its system files and its COMMAND.com be
placed on drive `C'. The SYS command can do that, but it will want to have
the system files occupy the first area on that drive. Doing this may
overwrite important files that are already there.
--
Richard Bonner
http://www.chebucto.ca/~ak621/DOS/
Bill Marcum
>
> *** What operating system is on the `C' drive? If it's Windows, perhaps
> the problem is the NT file system.
>
> Otherwise, FreeDOS may require its system files and its COMMAND.com be
> placed on drive `C'. The SYS command can do that, but it will want to have
> the system files occupy the first area on that drive. Doing this may
> overwrite important files that are already there.
If the first partition is NTFS, FreeDOS shouldn't see it as 'C'. The FreeDOS
partition should be marked as active.
Wolfi
No, C: i formatted with regular FAT16.
> Otherwise, FreeDOS may require its system files and its COMMAND.com be
> placed on drive `C'.
FreeDOS is engaged by a dedicated boot manager and starts up nicely,
but doesn't come through with its boot process.
At first it complained about missing command com, so I copied
FDConfig.sys from D: to C:, because of its Shell statement:
SHELLHIGH=D:\FDOS\bin\command.com D:\FDOS\bin /E:1024 /P=D:
\autoexec.bat
Now command.com seems to be found but I'm still stuck with only a
blinking 'underline' cursor, but not a completely booted FreeDOS.
At this point of course I have no idea about the exact sequence of
stuff needed to be located and still be loaded and why FreeDOS seems
to be glued to C: rather than continuing doing its stuff from D: where
all its files are located.
To me it just appears as if there are still some hard coded references
to C: in some of the initial boot files and those dependencies are not
taken care of by the installer.
>The SYS command can do that, but it will want to have
> the system files occupy the first area on that drive. Doing this may
> overwrite important files that are already there.
That shouldn't be relevant here, since FreeDOS starts to boot and
looking for command com, but still unable to continue and finish from
D:
Bill Marcum
>
> Now command.com seems to be found but I'm still stuck with only a
> blinking 'underline' cursor, but not a completely booted FreeDOS.
>
> At this point of course I have no idea about the exact sequence of
> stuff needed to be located and still be loaded and why FreeDOS seems
> to be glued to C: rather than continuing doing its stuff from D: where
> all its files are located.
>
> To me it just appears as if there are still some hard coded references
> to C: in some of the initial boot files and those dependencies are not
> taken care of by the installer.
>
https://lists.sourceforge.net/lists/listinfo/freedos-user or
freedos-user [at] lists.sourceforge.net
Richard Bonner
> > Wolfi (publicalfa...@yahoo.fr) wrote:
Richard Said:
> > *** =A0 What operating system is on the `C' drive? If it's Windows, perha=
> ps> > the problem is the NT file system.
> No, C: i formatted with regular FAT16.
*** OK. Did you set the active partition in FDISK or an equivalent?
> > =A0 =A0Otherwise, FreeDOS may require its system files and its COMMAND.co=
> m be> > placed on drive `C'.
> FreeDOS is engaged by a dedicated boot manager and starts up nicely,
> but doesn't come through with its boot process.
> At first it complained about missing command com, so I copied
> FDConfig.sys from D: to C:, because of its Shell statement:
> SHELLHIGH=3DD:\FDOS\bin\command.com D:\FDOS\bin /E:1024 /P=3DD:
> \autoexec.bat
*** Have you loaded a memory manager? Any "High" commands will require.
it be loaded first.
> Now command.com seems to be found but I'm still stuck with only a
> blinking 'underline' cursor, but not a completely booted FreeDOS.
*** It sounds as if it's waiting for something that is not present, or
it requires user input.
> At this point of course I have no idea about the exact sequence of
> stuff needed to be located and still be loaded and why FreeDOS seems
> to be glued to C: rather than continuing doing its stuff from D: where
> all its files are located.
*** Try loading all the files on `C' to see if it operates properly.
If so, there may be a file that is required on `C' that was not there
previously. If not, there is either a wrong reference in a start-up file,
or the drive is not set up to properly boot DOS.
> To me it just appears as if there are still some hard coded references
> to C: in some of the initial boot files and those dependencies are not
> taken care of by the installer.
*** Perhaps so; it's hard to diagnose without my watching the boot
process.
> > The SYS command can do that, but it will want to have
> > the system files occupy the first area on that drive. Doing this may
> > overwrite important files that are already there.
> That shouldn't be relevant here, since FreeDOS starts to boot and
> looking for command com, but still unable to continue and finish from
> D:
*** Load everything on to `C' and test.