On Wed, 16 Nov 2005 21:11:56 +, you wrote:
Hi,
>As far as I know all the big name adapters will work with NDIS and MS
>Client. I've tried a range of 3com, Intel, Broadcom, PICO PCMCIA plus
>whatever Toshiba use in their older laptops. Do you know of any specific
>NICs that don't work?
I'v
Hello,
XDMA v2.6 and is available for download at:
http://johnson.tmfc.net/freedos (click XDMA driver)
XDMA/XDMAJR now have a /N switch to request NO local-stack. With /N,
each driver now uses 656 bytes if XMS is available and 592 bytes for
"DMA only" mode!
XDMA.ASM now has "common" code and as
Michael Devore wrote:
I know the basics of how open source development works. Or how it
frequently doesn't work. I am not lacking in suggestions on how to
apportion my time for open source issues and I have invested many days
dedicated to open source support -- not just for FreeDOS. Frankly
Hi Johnson,
You should try MS Client with NDIS driver only, NDIS is not a packet
driver, I've failed a number of times to bind a NDIS driver to MS
Client, some of the NIC's driver have problem.
As far as I know all the big name adapters will work with NDIS and MS
Client. I've tried a range of
Hi Robert,
MSCLIENT does not support SMB signing.
Go to the Default Domain Controllers Policy and turn off "Microsoft
network server: Digitally sign communications (always)".
But as I said in my original post, the Domain Controller admins and IT
policy makers are NOT going to agree to have
Hi there,
thanks for all the suggestions. It turned out that NTFS4DOS
(www.datapol.de) is the culprit. Even with the latest version from the
web site I get a fancy error message. With latest kernel and ntfs4dos,
the crashes seem to be gone away, but the misbehaviour is still there:
NTFS4DOS l
At 10:29 PM 11/15/2005 -0800, Brolin Empey wrote:
Michael Devore wrote:
And another warning: NASM done got it some bugs. Even with the
relatively modest source of HIMEM, I hit a couple.
Have you told the NASM maintainers about these issues? I think they would
probably be interested in wor
On 11/16/05, Johnson Lam <[EMAIL PROTECTED]> wrote:
> On Wed, 16 Nov 2005 09:18:22 +0200, you wrote:
>
> Hi,
>
> Yeah. I love the boot disk, it did everything automatically.
> But I fail to migrate the floppy into hard disk, copy the files to
> hard disk but they still try to read the floppy (it's
Gerry Hickman wrote:
> anyway. The other setting is something called "SMB signing" which is
> related to not being able to hijack open sessions with a packet sniffer.
> MSCLIENT does not support SMB signing.
Go to the Default Domain Controllers Policy and turn off "Microsoft
network server: Digit
On Wed, 16 Nov 2005 09:18:22 +0200, you wrote:
Hi,
> Try the last floppy image, works like a charm for me, PCI NIC autodetected
>and configured, MS Client works also (tested in vmware and a notebook
>with a Pentium M). It uses the NDIS driver but automagically adds a
>wattcp.cfg
>and the environm
10 matches
Mail list logo
