similar to: enhanced config.c32 module

Greetings: I have two systems, HP model 9000/800/R380. They are identical systems running 64-bit HP-UX 11.0 with 1GB RAM. I have downloaded and installed the HP rsync binaries, version 2.4.6 on both the source and target systems. The directory tree on the source system contains over 58GB of data in 1.3 million objects (including directories, links and files), 1.2 million normal files. The

Below, attached, and available at the 'ifmemdsk' branch at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=a975c12919bbd48739fede4ebfe099d98b87192e Review welcome! - Shao Miller ----- From a975c12919bbd48739fede4ebfe099d98b87192e Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sat, 6 Aug 2011 05:24:46 -0400 Subject: [PATCH]

I would like to see that it is possible to specify which config file should be loaded. I would like to have an extension of the CONFIG command. Normally CONFIG loads the file that is specified after it. It should be nice if syslinux/isolinux/pxelinux/extlinux can choose which config file to load, based on the bootloader from which the current config is runned. If I will explain it with an

Problems With wireless keyboard and form Dell and a Dell domensioen 5150 computer I have obtained a DVD UBCD on it and also a Linux distributions. By booting this DVD the main menu is displayed but the wireless usb board does not react. I made A working USB stick with a working UBCD (with working usb keyboard) with instuctions given in under mentioned forum about this matter. QUESTIONS: 1.

In message <BLU0-SMTP46982596DE9C2639CEB6B078BA40 at phx.gbl>, Ady wrote: >I am going to repeat what Genec requested at some point. Please post >the result of (replace 'sdX' with the adequate device): > > 'fdisk -l -c=dos -u=cylinders/dev/sdX' >and > 'fdisk -l -u=sectors /dev/sdX' > >where 'sdX' is (are) the problematic device. I

> > I have successfully created bootable USB flash drives containing the > following bootable products: > > 1) Clonezilla (recent version) > 2) Ultimate Boot CD (recent version) > 3) OpenELEC (recent version) > > All of these apparently use SYSLINUX as part of the boot process. > > All three boot up just fine and with no problems at all on

What I'm trying to get at is this -- I'd like to analyze and understand what softwares that was used to build a library of softwares that made it as UBCD 4.x. This way, I would be able to use UBCD as a model to build customized ITS apps to be used for campus tech work. Is there some kind of step-by-step or user guide that explains how to build everything from scratch and what softwares

Hello! Below is an excerpt from the thread in October. I have the same problem, but my laptop (which is a Brand new HP Compaq NC6230) does not have options in the BIOS to enable or disable floppy support. It just doesn't have one. I assume it leaves it enabled for USB Floppy support, but does not come with the drive. My ISOLinux setup is a UBCD. I tried to make my own, but the lack of

I and some other people have problems with running the freedos image included in Ultimate Boot CD (UBCD), when using memdisk for floppy emulation. Memdisk starts booting the image and freedos shows the following menu: 0 Boot Clean 1 Boot UMBPCI (silent) 2 Boot UMBPCI (optimal) 3 Boot UMBPCI (semi-defensive) 4 Boot EMM386 (optimal) 5 Boot EMM386 (semi-defensive) 6 Boot no UMB (defensive) 7 Boot

How do you do? I am a deaf and I am working at Gallaudet University as IT technician. For troubleshooting computer problem, I fixed over 4000 computers with different CDs such as Windows XP SP2, Dell 32bit Diagnostic Tools, Windows Memory Tester, Acronis True Image, ERD 2005, and others. Everyday, I brought many different CDs to different building for services. Really, I wanted to develop

> > In message <BLU0-SMTP1383C5798F6C577E5FFF368BA40 at phx.gbl>, > Ady <ady-sf at hotmail.com> wrote: > > >> With respect to all of the actually important stuff however, I may have > >> missed it all, but I don't recall having read or seen an explanation of > >> what Ady & everybody else finally figured out about all this... > >

> Both sticks show very unusual factors for heads and sectors > which are hardly intentional. If BIOS gets confused like fdisk, > then the failure to find files is quite plausible. > > ------------------------------------------------------------- > > Could you please exercise what is described for Linux in > http://www.syslinux.org/doc/usbkey.txt > and check whether

In message <BLU0-SMTP557B92590B4CC34F8318088BB30 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >Since in all cases you get to see at least the Syslinux copyright >message, the problem doesn't seem to be related to whether your BIOS >can identify the USB disk and boot from it. I can only agree. >Some GA motherboards might identify some USB drives as

In message <BLU0-SMTP48EE10402F4B5AE9EC1E078BBB0 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >Not all USB ports are the same. For instance, in some mainboards the >USB ports at the front of the computer case might be not recommended >for booting purposes. At least for these tests, I would suggest to >use always the same USB port where you have already seen success.

> > Anyway, in the F12 boot menu there is no clear indication of what thing > (or things) the BIOS thinks are or not present. (What made you think > that there would be?) > In some systems, in the BIOS F12 boot menu, when I have one internal SATA drive and one USB flashdrive connected, I could see them *both* under HDD, while under USB-HDD there is no device listed for the

How do you do? I am a deaf and I am working at Gallaudet University as IT technician. For troubleshooting computer problem, I fixed over 4000 computers with different CDs such as Windows XP SP2, Dell 32bit Diagnostic Tools, Windows Memory Tester, Acronis True Image, ERD 2005, and others. Everyday, I brought many different CDs to different building for services. Really, I wanted to develop

In message <BLU0-SMTP1383C5798F6C577E5FFF368BA40 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >> With respect to all of the actually important stuff however, I may have >> missed it all, but I don't recall having read or seen an explanation of >> what Ady & everybody else finally figured out about all this... > >There was at least one email that

> Hi, > > Ady wrote: > > I personally don't like this "hiding" [of CHS], but I understand > > their reasons to do so. > > > > I think that the "USB-Geometry" section in the wiki should try to > > point to the same kind of users. > > But it is in wiki page Hardware_Compatibility. > Check out the neighborhood. > If there

> > >This particular mainboard might be using different BIOS values than > >others, and there are several other alternative explanations for all > >these issues. Your last few tests suggest that we are on a good track > >now. > > I have just a couple of questions. First, who exactly is Mr. Syslinux? > Who is the primary developer/maintainer? Second, may I

The Windows recovery console doesn't work with chain.c32 3.85 or 3.86-pre1. COM32 chain.c32 APPEND cmldr=/cmldr Initially reported by cdob at: http://www.boot-land.net/forums/index.php?showtopic=10487#entry94001 It did work fine with the: "chain.c32: Handle nonlinear logical partitions" patch. The following patch broke the recovery console hack: chain.c32: add option to set hidden