similar to: Connecting to 1.9.18p10 from DOS boot diskette

I'm having a problem with Samba 2.0.6 on HP-UX 10.20, and I'd like to set up the debugging options so that I can only generate debug messages for my own connections. Can someone give me some help in how to do this? BTW, here's the problem I'm having... I'd appreciate it if anyone had any info about this issue as well <G> I'm connecting several Samba 2.0.6 shares

I have found something called: diskboot.img at: http://www.gtlib.gatech.edu/pub/centos/4/os/i386/images/ But it is 6Mb large (6411Kb) instead of 1411Kb And the rawreadwrirewin program gets an error on it when run on NT. On Win2000, it makes a diskette that fails to boot.. So really, HELP!!!! I 'just' discovered that my old bootable diskette is for Centos 3.0, and my other CDs are

Hi, I have HP DL 180 G6 2U Rack Server with HP Smart Array Controller Card B110i Onboard SATA Controller Chipset. This server has 4 * 500 GB SATA HDD have configured RAID 1+0 and it shows Single Logical Drive of 940 GB Hard Disk in the RAID BIOS. Have created driver diskette using dd command to enable this controller card to the CentOS 5.6 x86_64 arch and it shows HP LOGICAL VOLUME of size 940 GB

(New to CentOS and just joined the list.) Is there a boot diskette image for the install CD? I want to install CentOS in a classroom that does not have CD boot enabled. I couldn''t find one on the install CD, although it did have a USB flash drive boot image. I''m pretty sure that the machines in the classroom are too old to be able to boot from USB flash drives. (I will check on

OK. I am in an emergency crunch. I need that 4.0 install diskette. Like 2 hours ago! Where is it???????? I don't want to have to install 3.0 on this box.

On Friday, the IC3 (FBI/NW3C/BJA) put out a security advisory on their website that contained a fairly vaguely worded warning about Asterisk systems being compromised and then being used as "vishing" (voice phishing) platforms. They were non-specific on the threat other than to advocate upgrading to "newer versions" of Asterisk. This announcement was done on Friday

I have some hardware vendor diagnostic utilities that I'd like to use via PXE. One example is a three diskette test suite. How can I merge all these diskettes into a single PXE bootable image? I have been using pxelinux, memdisk, and isolinux successfully for other things, so I'm a little embarrased even asking. Is there a way to PXE boot ISO images? Can syslinux support larger than 2.8MB

Dear R community, I want to estimate coefficients in a (non-linear) system of equations using 'mle2' from the "bbmle" package. Right now the whole data is read in as just one long time series, when it's actually 9 cross sections with 30 observations each. I would like to be able to test and correct for autocorrelation but haven't found a way to do this in this package.

I downloaded the 'seatools for DOS' diskette creator on seagate website. it's a windows program that creates the diskette; so a floppy disk must be present in the drive. running the program is ok, but creating the diskette fails, it says "the current diskette format not valid". while the diskette is blank, vfat, mounted and linked to a: in wine; so everything seems to be ok.

I have been using the LEAF Bering firewall for a year or so. It boots with Syslinux 1.75. But Bering is too large for a 1440KB floppy, so it formats the diskette as 1680KB. Recently I found a small Compaq 2266 box to replace a larger Compaq 7170 to run the firewall. But when I try to boot the Bering diskette on the 2266 I get the following message: Loading Linux ............ Boot failed:

As I read in the article listet at the and of this email there is no sysvol replication while joining a domain as a dc. This means to me (if im right) that there are no group policies available on the samba dc. Is this right? On the other hand if I create a new domain n a samba dc and if I set up asamba as a new dc ... group policies are available. Is this correct?

We have about 50 CentOS servers with software RAID level 1 (mirroring). Each week, we swap out one of the drives (the one in the second of four hot-swap bays, only the first two of which contain drives) on each server and take them offsite for safekeeping. The problem is, the kernel seemingly randomly switches between /dev/sdb and /dev/sdc for these devices. This makes the process slower by

Hi, is there an easy way to circumvent the SYSLINUX novice protection thing? intended users don't know about CTRL key to circumvent it. I'm trying to make a generic bootdisk for systems of 8086 - Pentium4. however the bootdisk is slow, so I'd like to use Syslinux + Memdisk to load a diskette image. then the text displayed to user will be: 1) FreeDOS bootdisk (accelerated, 386

MEMDISK included in the freshly released Syslinux v3.10 is unfortunately broken. v3.09 works properly. Scenario: Isolinux --> MEMDISK --> FDBOOT.IMG (FreeDOS 360KB diskette image). Then try to access drive B: , which normally is your first diskette drive with driveletter A:. However, in this case MEMDISK occupies A:, and real diskdrive becomes B: Bug: when accessing B:, you're asked

I'm trying to move off of bpbatch and on to pxelinux (bpbatch doesn't boot the installation kernels for SuSE 8.1 and SLES 8--they appear to be too big). This has been a pretty easy transition, except for the fact that I'm using bpbatch to install Windows 2000 over the network as well as Linux. For Windows 2000 I use a DOS boot diskette with network drivers and run the 16-bit WINNT.EXE

Hi, Ady wrote: > This could be misinterpreted by some users as: "if > you want to build an isohybrid image, then you cannot use > 'syslinux.efi'". This would be incorrect. I don't know whether syslinux.efi can be used for booting from ISO 9660 via UEFI. Currently there is no example around which would succeed without GRUB or GRUB2. When describing the UEFI

Hi to all out there using HP DL380 G4 servers, i found a way to get the Digium TE410P with older firmware running on a HP-Compaq DL380 G4 Server! Here's the step-by-step description: 1. download the latest BIOS (in my case it was 4.04 from date: 06/02/2005) for the HP-Compaq DL380 G4 using the "Systems ROMPaq Firmware Upgrade Diskette for HP ProLiant DL480 G4 (P51) Servers" Link:

HPA, is it possible to add GZ support in syslinux itself? Some standalone software compresses very well, but is not compressed. Example is the Memtest86+ binary (90KB uncompressed --> 35KB gzip'd) and maybe Smart Boot Manager (gzip'd COM32 binary instead of normal COM32 binary?). I'm using both on a simple bootdisk, and all space savings are welcome. a workaround could ofcourse

(I *really* need to learn this list is configured for replying to sender instead of the list itself..) Dinesh P. schreef: > Hi there, > I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... > what is the problem can anybody tell me.. > please read Syslinux and Memdisk

We just upgraded our samba server from 3.0.14 to 3.0.21a and have discovered a subtle but very painful problem. Users of ESRI ArcMap (on fully patched Windows XP clients) are unable to read complex layered file data. Arcmap works fine with 3.0.14, it works fine with the data on a windows share, and it works fine when I set up a server to run the version of samba shipping with Solaris 9 (3.0.2! ).