Hi!
The search engine says many things. Not sure about those:
- If host is Win10/Win11, you have to enable insecure
guest logons in the Lanman Workstation config (?)
- While the DOS VM is running, you can use the VirtualPC
menu to "install or update VM additions".
This might try to edit your config.sys or autoexec.bat
and you might be using fdconfig.sys and fdauto.bat
instead if you use FreeDOS! This just is a different
default, FreeDOS will also use config.sys if there is
no fdconfig.sys present :-p
- You may have to grant R/W access to everyone for
the directory folder you want to share with DOS.
- Your error message seems to be common for the case
that the guest additions for DOS are not installed or
configured properly (see my comment above)
- If your Windows is older than Win7, the VirtualPC 2004
guest addition fshare.exe for DOS might work better, but:
https://forums.virtualbox.org/viewtopic.php?t=25412
- You may have to enable the less secure SMB1 on Windows?
Given your results so far, it might be that Virtual PC 2007
FSHARE expects an "old enough" DOS. Which could be why it
does not work with FreeDOS 1.4 and MS DOS 7.1, which both
support FAT32 drives. With drivers, they also support long
file names. You could use a FreeDOS kernel without FAT32
support instead: It will report as DOS 5.0 instead of 7.1 :-)
For example, you can replace the default (fd-) kernel.sys
by a copy of our KERNL86N.sys file: That one is without
FAT32 support and it is old 8086 CPU compatible as well.
Of course you can also use CALLVER ("setver") or a command
like VERSION=6.22 in config.sys or fdconfig.sys to tell
FreeDOS to pretend being version 6.22. Not sure whether
it will have side-effects if FSHARE believes you use a
non-FAT32 DOS if you actually use a FAT32-aware kernel.
My first guess at the moment is that Virtual PC 2007
simply tried to update the wrong config sys / autoexec
and failed to tune the FreeDOS configuration properly.
Of course you can look at what it does to your MS DOS 6
configuration and manually configure FreeDOS like that.
Regards, Eric
Does this mean that you've tried it with MS-DOS, and it worked as you
expect it to work with MS-DOS; but when you do exactly the same thing
using FreeDOS it doesn't work?
Yes. Actually I have tried the following ways with the following results:
1) MSDOS 6.22 -> Successfull
2) MSDOS 7.1 -> Error Message
3) FreeDOS 1.4 -> Error Message
4) FreeDOS testing (multiple versions) -> Error Message
It's open source, but I think first you need to answer my question.
No.
Virtual PC 2007 is similiar to VirtualBox as It allow you to install
multiple guest operating systems originally created by Connectix as a paid
product before acquired by Microsoft and faded out after Windows 7 which
used it to run XP as a guest. fShare is added DOS software (there are
others DOS items included) that allows you to add folders from Windows to
the virtual machine so you can xfer files back and forth.
There are (of course) other ways to transfer files, but folder sharing is
the easiest way when it works as expected. I use both virual floppies and
.iso files when all else fails.
On Sat, May 9, 2026 at 13:32 G.W. Haywood via Freedos-user <
[email protected]> wrote:
Hi there,
On Sat, 9 May 2026, Norby Droid via Freedos-user wrote:
Is it possible to have FreeDOS report itself as MSDOS?
Not sure if this is possible or even how some programs may work.
Anything is possible but I think you might be barking up the wrong tree.
I work in FreeDOS in virtual PC 2007 and I am tryin to use fshare which
allows shared folders in VPC but it tells me that "folder sharing on this
host is not allowed" which makes me think it expects msdos but is gettin
freedos instead.
Does this mean that you've tried it with MS-DOS, and it worked as you
expect it to work with MS-DOS; but when you do exactly the same thing
using FreeDOS it doesn't work?
Is there a way to have the system temporarily report as msdos
instead of freedos, or a way to have programs see the system as
msdos and not freedos?
It's open source, but I think first you need to answer my question.
Could anyone enlighten me on this and their opinions?
Let's try not to put the cart before the horse.
--
73,
Ged.
_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Does this mean that you've tried it with MS-DOS, and it worked as you
expect it to work with MS-DOS; but when you do exactly the same thing
using FreeDOS it doesn't work?
Yes. Actually I have tried the following ways with the following results:
1) MSDOS 6.22 -> Successfull
2) MSDOS 7.1 -> Error Message
3) FreeDOS 1.4 -> Error Message
4) FreeDOS testing (multiple versions) -> Error Message
It's open source, but I think first you need to answer my question.
No.
Virtual PC 2007 is similiar to VirtualBox as It allow you to install
multiple guest operating systems originally created by Connectix as a
paid product before acquired by Microsoft and faded out after Windows
7 which used it to run XP as a guest. fShare is added DOS software
(there are others DOS items included) that allows you to add folders
from Windows to the virtual machine so you can xfer files back and forth.
There are (of course) other ways to transfer files, but folder sharing
is the easiest way when it works as expected. I use both virual
floppies and .iso files when all else fails.
On Sat, May 9, 2026 at 13:32 G.W. Haywood via Freedos-user
<[email protected]
<mailto:[email protected]>> wrote:
Hi there,
On Sat, 9 May 2026, Norby Droid via Freedos-user wrote:
> Is it possible to have FreeDOS report itself as MSDOS?
>
> Not sure if this is possible or even how some programs may work.
Anything is possible but I think you might be barking up the wrong
tree.
> I work in FreeDOS in virtual PC 2007 and I am tryin to use
fshare which
> allows shared folders in VPC but it tells me that "folder
sharing on this
> host is not allowed" which makes me think it expects msdos but
is gettin
> freedos instead.
Does this mean that you've tried it with MS-DOS, and it worked as you
expect it to work with MS-DOS; but when you do exactly the same thing
using FreeDOS it doesn't work?
> Is there a way to have the system temporarily report as msdos
> instead of freedos, or a way to have programs see the system as
> msdos and not freedos?
It's open source, but I think first you need to answer my question.
> Could anyone enlighten me on this and their opinions?
Let's try not to put the cart before the horse.
--
73,
Ged.
_______________________________________________
Freedos-user mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/freedos-user
<https://lists.sourceforge.net/lists/listinfo/freedos-user>
_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user
_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user