similar to: Re: DOS Networking [OT]

--------------------------------------------------------------------- Red Hat, Inc. Security Advisory Synopsis: Buffer overflow in mars_nwe Advisory ID: RHSA-1999:037-01 Issue date: 1999-09-13 Updated on: Keywords: mars_nwe buffer Cross references: --------------------------------------------------------------------- 1. Topic: There are several buffer overruns in the mars_nwe

Hi there, we've got the following problem, while Windows-Clients works with samba and a DOS-Client connects over Mars_NWE to the same Linux-Server: When the DOS-Client opens a file on the linux-server and the WinClient opens the same file, and when both clients want to write the same file, the windows-client gets an error and crashes. We tried it only with the windows-clients and there

Hi, I've successfully got DOS booting over PXE with Memdisk, but as RAM is severely limited in the PCs I'm using (only 32-64MB) I can't load a huge Memdisk image to run large DOS programs, Windows, etc. Are there any programs out there like Memdisk, but instead of storing the disk in RAM they read it over the network? (A "netdisk" program.) This would be a really useful

Greetings ... I have a quick question, which I hope will get a straight and quick answer. I am moving my system from flat files to LDAP. I have had my users in LDAP for a while, but then found that my computer accounts for Win2K in still in passwd. My question is, what are the bare minume LDAP attribs that I need for them to contiune to work? But I don't think I am going to get that

Subject: Wildcard '*.' matches inproper files (for SAMBA DOS clients) The problem does not appear when using W9x/NT clients. Testing environment: samba: 1.9.18p10i (compiled), 2.0.5a(binary distrib), 2.0.6(compiled) on Linux RedHat 6.0 and Solaris 2.5 smb.conf: | |[global] | workgroup = WORKG | server string = Samba %v | encrypt passwords = Yes | socket

Hi all, I'm trying to work out how to boot DOS on a diskless PC, and I've come to a bit of a stumbling block with loading IPX support (which is extremely important, since most DOS games use IPX for network play ;-)) So far thanks to PXELinux and Memdisk I've gotten a DOS floppy image booting successfully, but I'm stuck trying to get IPX support. Admittedly I don't have much

On 17 May 99, Axel Neumann <amn@cromemco.com> had questions about DOS to UNIX Conversion: > It seems that a lot of people hate Windoze in such a way that they only > accept solutions that are not coming from M$. Maybe that's because the M$ "solutions" are crap, and much better alternatives already exist. > If you want to view UNIX text files correctly on a W9x

Hi all, I'm still trying to figure out a good way of booting a DOS disk image via PXE and accessing files over a network share. Having some success with the Microsoft network DOS client, it seems that many programs have issues with its IPX support - so, now I'm trying to use Novell's IPX driver instead. Unfortunately it seems I need an ODI driver to do this, and there are no

> On Fri, May 23, 2014 at 8:29 AM, Ady <ady-sf at hotmail.com> wrote: > > Testing the DOS-based Syslinux installer, syslinux.com, with the "-m" > > parameter, I found that it works as expected under MS-DOS and its DOS > > variants, but it seems to fail under FreeDOS (please correct me if > > I'm wrong). > > This sounds like either a bug in

On Fri, May 23, 2014 at 8:29 AM, Ady <ady-sf at hotmail.com> wrote: > Testing the DOS-based Syslinux installer, syslinux.com, with the "-m" > parameter, I found that it works as expected under MS-DOS and its DOS > variants, but it seems to fail under FreeDOS (please correct me if > I'm wrong). This sounds like either a bug in FreeDOS or another undesirable negative

Hi, maybe I missed a recent "FDP" (Frequently described problem)in the list, but maybe somebody can point me to the right direction. There were several postings about not seeing Samba but none referred the the MS "File and Print Services" on W9x clients being the cause of the trouble (Hope this is the correct translation from German W9x). I've got a Samba 2.0.5a with Suse

I have Cent OS 5.1 I also have http://phpsysinfo.sourceforge.net/ I have asterisk running . Now when I look at System Information , I see that "Physical Memory" keep increasing and at one point it reaches 96%. Then my sever get hang and then I have to restart it. I have 4 GB RAM. Processors 2 Model Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz CPU Speed 2.53 GHz Cache Size 3.00 MB

I just tried to set up a tinc test installation, but I guess I did something wrong, because I can only ping one direction. Here's my setup (lan1,192.168.99.0)<-->firewall1<-vpn->firewall2<-->(lan2,192.168.100.0) firewall1 has tap0 on 192.168.88.2 firewall2 has tap0 on 192.168.88.3 i set up the following routes : on firewall1 : 192.168.100.0 gw firewall2(192.168.88.3) on

Greetings ... Please could someone confirm that Samba 2.2.x and Samba 3.0 ( Head ) does not support Trusts between domains. Thanks Mailed Lee

On 05/24/2014 01:58 PM, Ady wrote: > > My guess is that if this was a bug in FreeDOS (as in "something" that > has nothing to do with the syslinux.com command) then it would be > somehow triggered by other DOS programs trying to write to the MBR. > Considering that there are several (open source) DOS programs that > are capable of successfully writing to the MBR

On Sat, May 24, 2014 at 11:22 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 05/24/2014 01:58 PM, Ady wrote: > > > > My guess is that if this was a bug in FreeDOS (as in "something" that > > has nothing to do with the syslinux.com command) then it would be > > somehow triggered by other DOS programs trying to write to the MBR. > > Considering

Hello, In R 2.10, looking at: > `?` function (e1, e2) { if (missing(e2)) { type <- NULL topicExpr <- substitute(e1) } else { type <- substitute(e1) topicExpr <- substitute(e2) } if (is.call(topicExpr) && topicExpr[[1L]] == "?") { search <- TRUE topicExpr <- topicExpr[[2L]]

Sorry for the delay, I should not send email on an holiday week-end. I'll try to answer all the questions by explaining what does work for me right now, and what I'd like to do. I have a script to create the a USB stick or an ISO image. The boot media contains many DOS images, and I use versamenu to select one of them. If my DOS image is smaller than 8megs, everything is working fine as

Hi, I did found the problem, a combination of 2 factor. 1- I taught that I did install the latest syslinux, but in fact it was the 3.36 version. 2- Thank to kevin Connelly, he point me to a problem he got with mkdosfs command. The default FAT16 do not work, but the FAT12 do. By adding -F12 to the mkdosfs command fix the problem. The default F16 do seem to work for <8M floppy image. Thank you

To make say a BIOS flash tool available over PXE, my impression is that a typical procedure goes like this: modify a generic FreeDOS 1440K disk image to contain the EXE and change the AUTOEXEC.BAT to launch that EXE, then make the 1440K IMG available on the PXE server. But more recent BIOS flash EXE are too large and won't fit on the 1440K, not even 3840K, so now we have to look into