similar to: SYSLINUX doing odd things since upgrade

Hi all Is it possible to boot an ISO image using syslinux - using something like memdisk? Thanks Chris ***Disclaimer**** This e-mail and any attachments are for the intended addressee(s) only and may contain confidential and/or privileged material. If you are not a named addressee, do not use, retain or disclose such information. This email is not guaranteed to be free from viruses and does

Hi all I checked the archive and it looks like this is a known problem, but no news since Dec 2006. So, I was wondering, is there any update on this problem, as I've tried it on a variety of Thinkpads with up to the latest version of syslinux/memdisk. Thanks Chris ***Disclaimer**** This e-mail and any attachments are for the intended addressee(s) only and may contain confidential

Have just upgraded from 3.0.14a to 3.0.25b. On starting winbindd it puts the following in /var/log/messages: initialize_winbindd_cache: clearing cache and re-creating with version number 1 All the winbind UID/GID mappings are lost and it starts again from scratch. Hence all file ownership / ACLs on this samba server become invalid. Anyone else seen this? Why does it see fit to destroy this

Good day again Daniel, So the first thing I did was to remove the >NUL for your XMSDSK line and put a PAUSE after it in AUTOEXEC.BAT. That way, I could see the error message: *** XMS RAMdisk v1.9I (FU - 08/98): XMS get free mem error. Then I noticed that if you run AUTOEXEC.BAT manually from the DOS CLI, XMSDSK actually succeeds! So that led to a new test: Duplicate the XMSDSK line. ...

Good day to you, too. No worries about the delay. I understand how busy everyone is with SYSLINUX. Gladly, the project continues to develop and improve. With that said, thanks for today's flurry of activity regarding my reported problem. Impressively, the debug version of MEMDISK that you had directed me to use appears to have done the trick. Results below. command line:

Hello all. Again I call upon the greats of this mailing list to help me with an issue related to MEMDISK - notably when paired with various Dell OptiPlex and Latitude systems. The issue presented itself sometime ago and I best dealt with it by remaining with version 3.83 of the SYSLINUX package. But valuing the improved changes fostered by newer versions, I would prefer to move forward with

Hello, =20 Something wrong happens when I use the seq (function). Here it is an exampl= e from my R console, I have the R version 2.7.2 (2008-08-25) running on Mic= rosoft windows XP Version 2002 Service Pack 3, and my machine is a Dell Opt= ilex GX280 with a processor Intel Pentium 4 CPU 2.80GHhz, 0.99 GB RAM: =20 =20 >r=3Dseq(0.150,0.180,0.001) =20 > r[16] =20 [1] 0.165 =20 >

A kind request for help please. MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below: MEMDISK 3.83: Ramdisk at 0x07eeaa00, length 0x007bc000 command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk MEMDISK: Image seems to have fractional end

Hello. We've been using a very old version of SYS-/PXELINUX, 3.36, going by the proven "if it works, don't break it" philosophy. We us it mostly to load floppy disk images to kick off OS installations. Unfortunately we've recently had some PXE menu problems (USB keyboard stopped working) for a certain Fujitsu PC model, and decided to upgrade to the latest version, i e 3.84.

Hello all. I am pretty new to this list but I have looked through the archives and did not see any reference to this problem. I have an MS-DOS boot floppy image that I am trying to load using MEMDISK. The disk is simply a boot floppy made using XPSP2. I have tried it on 4 different machines, all Dells. PowerEdge 2650 Server, Latitude D610 Notebook, Optiplex GX280 Desktop and Optiplex GX520

I've got echo problems. *** I'm looking for paid support. *** I'll accept free support, but don't mind paying if someone really knows what they are doing. I've read the wiki, etc. Played with the settings in zapata.conf Using V400P PSTN->_T1->_ASTERISK->_BROADVOICE->_PSTN ECHO ON CALLED PHONE PSTN->_T1->_ASTERISK->_T1->_PSTN NO ECHO

git://git.zytor.com/users/genec/syslinux.git Branch memdiskdbg-for-sha0 This starts with adding another check in two of the disk probes (by Shao; Thank you), expands the debug output, adds an additional check in the third probe and expands/reorders the debug output. At this time, it appears to resolve the MEMDISK issues that Jason Vasquez first noticed. The additional check in the third probe

Hi H. Peter Anvin, I wanted to thank you for sharing information about PXE, I have used this a lot and I wanted to share something that may be important for you and your readers. I have many different Dell model, they all worked well with PXE booting however not for E5510. I noticed that using "LocalBoot -1 or 0" doesn't work well. What I did use for Latitude E5510 (Bios A06)

Are there any differences with how both IDLE and "UID FETCH n:n+x (FLAGS UID...)" are handled when Dovecot is using a "mail" vs. a "Maildir" user? I have recently implemented support for IDLE (Push E-mail) in a client infrastructure that I'm building. I haven't in depth checked out what the problem might be, but when Dovecot was using the "mail" dir

Greetings I am nearing being prepared to get our corporate network from Active Directory to samba3 with ldap. The last hurdle is to get an administrative interface to the ldap repository containing the users and Groups. I,m hoping for some recommendations. I have attempted the following. Samba Console: http://imc.sourceforge.net/samba-console.html The difficulty I'm having is that it is

Hello. I've been testing pxelinux.0 (4.04-pre14) on some laptops: - HP EliteBook 6930P with BIOS F.18. - HP EliteBook 8440P with BIOS F.06. - Dell Latitude E4310 with BIOS A06. When booting pxelinux.0, the machines first display some random letters in different colors and then reboot. We've been using 4.02 for some time without problems. I've tested 4.03 too and it seems to work.

Hi A Optiplex GX270 with bios A06 (latest) freezes at the menu when I use 3.08pre5. Setup was simple menu (menu.c32) and pxe. When I tested with 3.07 everything worked as normal. I Have not had any problem with 3.08pre5 in other tests and machines. Also but not that important, I learned that for the hotkey highlight to work It must be uppercase for me. If lowercase the goto still works but

Hello, I'm seeing this warning and oops when trying to fuzz linus v4.4-rc1-290-g3ad5d7e with trinity. ------------[ cut here ]------------ WARNING: CPU: 1 PID: 4308 at drivers/gpu/drm/nouveau/nouveau_fence.c:198 nouveau_fence_context_new+0x22e/0x270() CPU: 1 PID: 4308 Comm: trinity-c19 Tainted: G B 4.4.0-rc1+ #1 Hardware name: Dell Inc. OptiPlex 990/0D6H9T, BIOS A06 07/25/2011

I've tried Samba 3.2.14, 3.3.7, and 3.4 (source3). In each instance, smbd was missing libtalloc.so.1 libtdb.so.1 libwbclient.so.0 as reported by ldd. It didn't work to well either :-) I've not been able to find RHEL 5 libtalloc package. I tried installing some from fedora core(6 and 11), however, they had considerable dependency trees... some of which conflicted with what was

Ah so... sure enough these libraries are found in their default locations /usr/local/samba/lib. ./configure LDFLAGS=Wl,-rpath,/usr/local/samba/lib SOLVED this problem on RHEL 5.3, x86_64 with gcc 4.1.2 Thanks, RW Hornbaker ________________________________________ From: John Drescher [drescherjm at gmail.com] Sent: Friday, August 21, 2009 3:22 PM To: Hornbaker, RW Cc: samba at lists.samba.org