Hello Norbert,
But there are still some systems, where the machine completely stops
responding when initializing the network.
some network clients don't work if loaded into UMB memory; they also
don't work with MSDOS emm386
So, for your testing I applied for a fully functional test version
But there are still some systems, where the machine completely stops
responding when initializing the network.
some network clients don't work if loaded into UMB memory; they also
don't work with MSDOS emm386
The network client isn't loaded high at all.
And if you use umbpci everything works
This problem occurs when using SMARTDRV.EXE (with write caching
enabled) from MSDOS 6.22 with FreeDOS. Replacing either avoids the
problem.
I haven't pinned it down yet but the problem seems to occur with
more than just one pgm. I've seen it when installing UKA17X2 (i.e.
UKA_PPP),
Hello Norbert,
But there are still some systems, where the machine completely stops
responding when initializing the network.
some network clients don't work if loaded into UMB memory; they also
don't work with MSDOS emm386
The network client isn't loaded high at all.
And if you use umbpci
Hi!
19-Авг-2006 21:31 [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote to
freedos-user@lists.sourceforge.net:
sn h) Boot from first harddisk (0x80)
sn I fell into this because of the timeout. The next two lines on the
sn screen are:
sn Booting from local disk...
sn Virus!!!
This may be
Hi all,
But there are still some systems, where the machine completely stops
responding when initializing the network.
some network clients don't work if loaded into UMB memory; they also
don't work with MSDOS emm386
The network client isn't loaded high at all.
And if you use umbpci
Hi Eddie,
2006/8/21, [EMAIL PROTECTED] [EMAIL PROTECTED]:
This problem occurs when using SMARTDRV.EXE (with write caching
enabled) from MSDOS 6.22 with FreeDOS. Replacing either avoids the
problem.
Well, thanks indeed for the reports, perhaps you could tell us too if
you're using
Norbert Remmel schrieb:
You should also be prepared to send/sponsor this network card to
Michael
I really would like to do but my boss would cut my head off if I would
do so as you surely can imagine ;-)
That's just another way to solve the problem :D
SCNR ;)
Best regards,
Andre
Hi!
21-Авг-2006 18:08 [EMAIL PROTECTED] (Andre Tertling) wrote to
freedos-user@lists.sourceforge.net:
You should also be prepared to send/sponsor this network card to
I really would like to do but my boss would cut my head off if I would
AT That's just another way to solve the problem :D
AT
You should also be prepared to send/sponsor this network card to
I really would like to do but my boss would cut my head off if I would
AT That's just another way to solve the problem :D
AT SCNR ;)
What is SCNR?
Don't know either.
But he is right... Cutting my head off would really
At 06:50 PM 8/21/2006 +0200, Norbert Remmel wrote:
You should also be prepared to send/sponsor this network card to
I really would like to do but my boss would cut my head off if I would
AT That's just another way to solve the problem :D
AT SCNR ;)
What is SCNR?
Don't know
At 05:15 AM 8/21/2006 -0600, [EMAIL PROTECTED] wrote:
This problem occurs when using SMARTDRV.EXE (with write caching
enabled) from MSDOS 6.22 with FreeDOS. Replacing either avoids the
problem.
SMARTDRV is pretty particular on some machines. I just pulled the
following from the Microsoft
At 09:37 AM 8/21/2006 +0200, Norbert Remmel wrote:
During testing I discovered a bug concerning STR-ALT-DEL usage.
When pressing these keys, freedos crashes with invalid opcode outputting
some memory addresses and registers.
As I remember this wasn't like this using earlier versions of
hey - I hear this is the place I've installed FreeDOS on the first 250MB partition of my hard drive, it works in dosemu, and I can run Free COM in Windowsbut when I try to boot to it from LILO it passes over to the kernel (I think)
and tells me :Bad or non existant command interpreterenter full
Arkady V.Belousov wrote to freedos-user@lists.sourceforge.net:
sn h) Boot from first harddisk (0x80)
sn I fell into this because of the timeout. The next two lines on the
sn screen are:
sn Booting from local disk...
sn Virus!!!
This may be message from BIOS (if there is turned on
Hi!
21-Авг-2006 14:07 [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote to
freedos-user@lists.sourceforge.net:
sn Editorial comment:
snObviously, some of these results are not ideal.
What you want from FreeDOS in given case?
snWhat do *I* want? Nothing. I'm just testing the release CD
Hi!
21-Авг-2006 21:21 [EMAIL PROTECTED] (Chris Monahan) wrote to
freedos-user@lists.sourceforge.net:
CM I've installed FreeDOS on the first 250MB partition of my hard drive, it
CM works in dosemu,
CM and I can run Free COM in Windows
CM but when I try to boot to it from LILO it passes over to
At 09:37 AM 8/21/2006 +0200, Norbert Remmel wrote:
During testing I discovered a bug concerning STR-ALT-DEL usage.
When pressing these keys, freedos crashes with invalid opcode outputting
some memory addresses and registers.
Eric made a change suggestion which seems to clear up the problem with
At 02:50 PM 8/21/2006 -0600, Eddie wrote:
I was really hoping that this problem had been silently fixed by
all of the other work that has been done recently. I was disappointed
when the same problem cropped up again - because that means more work.
So far I haven't done the work to isolate
19 matches
Mail list logo
