Hi,
I've been running FreeDOS with MSCLIENT 3.0 for some time connecting to
Windows networks and being able to access files, install o/s etc.
Suddenly this week it does not work anymore:(
It appears the problem is related to our Domain Controllers being
upgraded to Windows Server 2003. As I
On Tue, 15 Nov 2005 13:11:36 +0200, you wrote:
Hi,
NwDisk is for Netware.
MS Client Solution
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.
I've successfully
Johnson Lam schreef:
On Tue, 15 Nov 2005 13:11:36 +0200, you wrote:
Hi,
NwDisk is for Netware.
MS Client Solution
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
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 working with you in order to fix the
bugs. NASM is
On Wed, 16 Nov 2005 04:44:08 +0100, you wrote:
Hi,
NwDsk can run MS Client (TCP/IP), see
http://www.veder.com/nwdsk/index.html#ms.img
Oh Gawd, my mistake. I didn't go through every paragraph ...
The big heading is IP/IPX ... I downloaded the Bart's boot disk only,
sorry to Erwin.
but that
On 11/16/05, Johnson Lam [EMAIL PROTECTED] wrote:
On Wed, 16 Nov 2005 04:44:08 +0100, you wrote:
Hi,
NwDsk can run MS Client (TCP/IP), see
http://www.veder.com/nwdsk/index.html#ms.img
Oh Gawd, my mistake. I didn't go through every paragraph ...
The big heading is IP/IPX ... I downloaded
