similar to: MSDOS on my network

I have periodically been trying to get memdisk to boot images larger than your average 1.44Mb floppy and have always been unsuccessful. I cannot boot anything greater than 1.44Mb. The systems I'm attempting to do this with are not too old but they are not recent either. One is a Asus P5A and the other is a Intel SE440BX both with the most recent bios firmware patches available applied. If

Hi, All. I hope everyone's enjoying the nice weather. I am called the system admin here, but really I just fell into the job over the past 25 years. Is there a way to search the archives? My problem is that I've suddenly got 6 WinXP desktops that can access only 1 of my 5 smb servers, 4 of which run on Linux and 1 on SCO Unix. The 1 they can access runs Linux with Samba version

For several reasons (security, resources, and simplicity) is there a project underway to make Samba run without TCP/IP. The FAQ says that there is a desire to make this project work, and that it is stalled. I for one would like to hear from anyone working on this before I dive headlong myself into trying to get Samba to work without TCP/IP. --john

If 'msdos' filesystem is not compiled in Kernel (and I don't have the msdos.ko module neither), then syslinux refuses to work. Is it possible to fix syslinux to try more filesystems, not only msdos? Or is it possible to call the mount command somehow without filesystem option at all, so the kernel (or whatever) will decide itself what filesystem to use? Thank you for

Hi, How are you! I built a PXE server of MSDOS in Linux server, client can boot from network and login MSDOS, but by default, the output console is VGA, My target client has not VGA port, it can only output from serial port, so could you help to tell me how to boot a MSDOS client from network and keep the PXE client output console is serial port ? Below is the PXE configure file?s

Hi all, I try to boot an msdos system using pxelinux and memdisk on my PC engines Wrap-2.c card and I have problems with it This is what I see: PXELINUX 3.11 Debian-2006-03-16 Copyright (C) 1994-2005 H. Peter A boot: msdos Loading memdisk.... Loading images/msdos/msd622bd.dosim......................... Ready. dp83815: Setting full-duplex based on negotiated link capability. MEMDISK 3.11

I have many hp laptops that boot msdos with memdisk + pxelinux perfectly. However, I recently have the need to usb boot msdos with syslinux. And memdisk. When the dos Image loads I get "loading bootsector..." and then it halts. Sometimes I can get "starting ms-dos" but freezes as well. I'm trying to boot clean msdos floppy image created with winimage. I'm using

Hi! Windows Applications seem to run fine uder wine, but for any MSDOS-Application FILE, I get the following error: wine: can't exec 'FILE': invalid exe file Protocol error: process 0x806a100: partial recvmsg 0 for fd This happens regardless of winver/dosver (wine is called by 'wine --winver winxyz --dosver x.yz FILE'). What am I doing wrong? Do I need to start some kind of

Running samba 1.9.16p11 on Digital Unix 3.2c. We currently access unix shares from W95 without problems but now since we had our network overhauled, 2 MSDOS harddriveless PC's need to be able to access the unix system for it's hard drive. They have Intel Express cards . How do I setup the MSDOS computer to map a drive to SAMBA. One question is these computers do not have IP addresses, how

(I've already sent this message to Ted Ts'o directly. I should have sent it to this list first but I didn't know about it until today. My apologies to Ted.) Last Friday a system that I just inherited refused to mount a file system that had been working fine for about 6 months. This is on a Scientific Linux 4.3 system using a 2.6.9 kernel. This is another Linux distribution based on

I've been sitting in on this mailing list for a long while now, and I wanted to know, if there are any guide lines on getting a system to boot a DOS boot disk over the wire, ie, via PXE booting? I know this has been covered, and I am also googling for a site to help me out, but I thought I would ask anyway, so that I don't get lead astray. I have a thin client setup already up and

I am working on creating a program for some simulations I need to do and I want to execute a Perl script that I wrote using the system() command in R. I have spent a couple days trying to figure this out and it appears that my problem occurs when sending the perl script file path through R to MSDOS. I have tried using double backslashes, quotations, etc. Moving my files to the root directory with

Hi, I've been using rsync to create backup copies of all my data files on my Linux laptop to my Windows XP Home based desktop for about 6 months now. Been working as it should, copying only files that changed since the last backup. The first backup I ran after the time change to Daylight Saving Time it wanted to copy all of the files regardless of the timestamp. It copied old files

Hello Anytime I try to do anything with the root user (like join the domain) or run 'net user' or 'net group' with root, when I enter the correct password, I get NT_STATUS_UNSUCCESSFUL .... I've been trying more commands, and if I run tdbedit -e=tdbsam (to export the smbpasswd to tdbsam style), I get this error : tdb_update_sam: Failing to store a SAM_ACCOUNT for [root]

Does SYSLINUX have any idea which DOS driveletter would be assigned to the disk it is booting from? At www.veder.com someone is trying to build a USB flash drive. However, FreeDOS does not seem to boot correctly from it (bootsector trouble maybe, or kernel itself is confusing drives), thus we're thinking of using Syslinux + Memdisk + bootimage, but somehow we want to be able to also access the

Hello, Everything I've tested so far regarding my Samba 3.0.0 beta 1 installation works great, despite the following error: Error loading module '/usr/local/samba/lib/charset/CP850.so': Cannot open "/usr/local/samba/lib/charset/CP850.so" This error comes up when I run any of the Samba binaries, such as smbpasswd, pdbedit, etc... also it shows up in log.smbd, log.nmbd when

Hi, I've been searching through the list archives on marc.theaimsgroup.com, and haven't found many suggestions relating to this problem. What's happening, is that maybe 5 out of 100 network logons the logon script does not execute, and none of my drives are mapped. This happens on both NT 4.0 Workstations as well as Windows 2000. It's been happening as long as I can remember

HI all ! I've read in a doc, that Samba is talking only with the clients where Netbios over TCP/IP is running ! I guess it is true, but are there any solution maybe to connect with a client where only the NETBEUI is the only one installed protocol ? It would be from DOS, I have a DOS boot disk which is waking up the Netbeui, and it would be difficult to prepare it to wake up the TCP/IP !

Hi, Before Samba 3.0.0 RC4 I was running Samba 3.0.0 beta3, and when I upgraded to RC4, I began having problems with group mappings. I didn't notice at first, because on my laptop I don't normally log on to the domain. I just noticed when I tried to use my desktop and log on to the domain... I don't have Domain Admin privileges. So, I look at 'net groupmap list' ... and it

I'm trying to use this universal DOS TCP/IP boot disk available here: http://members.iinet.net.au/~bdriver/bootdisk/ It requires an MS-DOS formatted disk created by Windows XP. It works great as a floppy but doesn't boot at all with memdisk. The problem can be simplified down to just the XP boot disk. If you make an MS-DOS startup disk with XP on a floppy, dd the floppy to an image