I have a pi running raspbian (debian 10) and samba 4.9 which serves files
to a set of DOS QEMU VMs using the MSCLIENT 3.0 for DOS network stack.
It's pretty cool to see DOS boxes running on an ARM.
Anyway, what follows isn't pretty but here are ALL of the pertinent details
I can think to share.
I normally don't use DOS < 3.3 myself, either. But I do have programs that
claim to work with DOS 3.0 or 3.1 so I want to make sure they actually work
where they claim to. I guess hardly anybody really uses DOS < 3.3 any more,
except maybe the few people who still have working PC/XT/Jr hardwar
> On Mar 1, 2022, at 3:29 PM, tom ehlert wrote:
> [..]
> I'm still surprised the
>
> ECHO Off | VGoToXY Up | VEcho /N /E
>
> line doesn't work, but as I don't care about MSDOS 3.x anyway I will
> be able to live with that
>
> Tom
+1
I don’t spend much time using MS-DOS 1 & 2 or any ot
> if I wrote
> anything I think it would be something that actually tries to
> manipulate the ECHO state (if that's even possible without a WHOLE lot of
> work).
1'st) you still get the output of your
ECHOSTATE OFF
program on screen, which started the whole discussion.
2'nd) there is no EC
> There is one other thing to try via v8power tools. Instead of using
> vgotoxy up | vecho /n /e, there is another combination to do it as
> well.
>
> echo off | vgotoxy up | vdelete
>
> Anyhow, vdelete is a far simpler program than vecho. You may even
> have better compatibility results.
I'll try
>> Multi-booting all those OSes off a single partition is very *VERY*
>> much a hard way of doing this.
> Actually, no it's not. It's fairly easy with System Commander.
+1
while I didn't use System Commander, *ALL* of us were booting multiple
systems from the same disk (and possibly also parti
> Multi-booting all those OSes off a single partition is very *VERY*
> much a hard way of doing this.
Actually, no it's not. It's fairly easy with System Commander. And AFAIK,
System Commander is the only multi-boot manager that works this way
(manipulating the boot files instead of manipulati
Hi,
> If I run either TEST1.BAT or TEST2.BAT with MS-DOS 3.0, 3.1, or 3.2, it
> crashes.
That is definitely possible. Since the earliest version of DOS I really only
every used was MS 3.3, I never have worried about pre-3.3 compatibility.
> If I run them with MS-DOS 3.3 or 4.01 the session l
Well, I've run some tests with V8 Power Tools and let's just say they are
inconsistent. In summary, the V8 Power Tools approach sometimes works and
sometimes doesn't, so it's not a universal solution. In fact, there doesn't
seem to be a good, universal solution and I just may need to live with
Thanks Liam,
If this app is copy-protected and needs a dongle, then I suspect it
won't run in a VM, because the dongle won't be connected to the VM.
How about just running Windows 7 32-bit in a VM, and trying that way?
You already have it, presumably licensed
If the dongle won't be recognized by
On Tue, 1 Mar 2022 at 02:41, Sean Warner wrote:
>
> Thanks Liam,
>
> Not sure if you saw my more recent post...
You changed the subject/title line. In Gmail, that broke the thread
and made your 2nd message into a new thread.
> I now have a version of FreeDOS 1.2 with the NIC and MS Client instal
Thanks Jerome.
I'll take a look at EtherDFS..
Regarding Win 10 being snobbish. Smbv1 is now disabled by default in Win
10. You can enable it and you might need to change the local security
policy in each win 10 client also to allow lanman auth.. not sure if you
can do that in Win10 home Ed.
At l
On Sat, 26 Feb 2022 at 02:57, Bret Johnson wrote:
>
> I have a large set of DOS environments I use for testing. Basically, I have
> a bunch of different versions of DOS that I can boot to (MS-DOS, PC-DOS,
> FreeDOS, DR-DOS, from versions 3.0 to the latest of each). DOS versions 1 &
> 2 were s
Hi,
I’m no expert on Samba shares. But from personal experience, your probably not
going to have much luck.
I have a Linux server on my home network. When I let it use a minimum of SMB2,
all but one ancient Mac will chat with it. No problem.
But to get that one Mac working, requires lowering
Bret,
> 3. Just let the problem happen and "fix" the screen afterwords
Jerome's approach is probably the only sensible solution,
like
>> echo off | vgotoxy up | vecho /n /e
> This to me seems like a solution that could actually do what I'm
> wanting to accomplish. I may experiment with that
Hi Dennis,
Thanks for the detailed response.
There is a bit of pressure from my IT dept to upgrade both the file server
that the network share resides on and the win 7 laptops that we use to run
the dos app in.
When they recently upgraded another file server the dos app had to be moved
to anothe
16 matches
Mail list logo
