Displaying 20 results from an estimated 1200 matches similar to: "chain.c32 "map" argument"
2010 Dec 30
0
chain.c32 map argument patch
The syntax is (in unix regexp form for lack of knowing BNF well):
each drvspec is (ignore whitespace): (fd[0-9]{1,3} | hd[0-9]{1,3} | boot
| 0x[0-9A-Fa-f]{1,2} | (0[1-9][0-9]{1,2}) | 0[0-9]{1,3})
where each branch represents: floppy disk 0 through 127, hard disk 0
through 127, boot drive, drive 0x0 through 0xFF in hex, drive 0 through
255 in decimal, drive 00 through 0377 in octal.
the full
2016 Jul 14
3
[PATCH] : Adding dlabel option to chain.c32
On 07/14/16 05:56, Ady Ady via Syslinux wrote:
>
> @Peter, Erwan, Gene, Michal, (and anyone else interested)...
>
> Although I haven't actually tested Erwan's patch, would it be
> acceptable by you (all) if I were to send a patch to this Syslinux
> Mailing List with the same code while changing the wording as I
> previously suggested in a prior email? Would it be
2016 Jul 15
0
[PATCH] : Add diskbypartname option to chain.c32
Looking at the UEFI specs, and _if_ I understand Erwan's patch correctly,
we are talking about searching for a "Partition Name". Avoiding the
"label" term for this new option should help in reducing some potential
confusions (e.g. BSD's "disklabel", fdisk's "partition label (type)",
filesystem's "volume label"...).
So, IMO,
2010 Jul 24
0
[PATCH] chain.c: allocation fixes
1) At the end of main, there's attempt to free cur_part->record, which
rarely comes from malloc. Only valid case is if gpt handover was performed
and chaining was not successful (cur_part->record is overwritten with gpt
specifc handover record). Freeing the handover area has been adjusted.
2) If our current iterator is ebr, parent wouldn't be freed at the end of
main. Added generic
2012 Nov 06
50
chain.c32 (and partiter) updates v2
This is a bit updated set of chain.c32 changes that simplifies a few things
(and in partiter part), fixes few minor issues and adds a few new features.
Details are in the following commits, below is the summary and pull details at
the end.
Shao - any chance to peek over them ? Most of those are relatively simple
changes and well tested, though of course something might have slipped my
attention.
2011 Nov 10
1
Help: sqlSave Error
I am using sqlSave to save my data into an existing table at MS SQL Server
database. Previously my code ran smoothly but all of a sudden it stopped
working. Here is my code:
sqlSave(con, highVol, "dbo.futuresHighVol", append=TRUE, rownames=FALSE)
Error: sqlSave(con, highVol, "jrgchis.dbo.futuresHighVol", append = TRUE, :
42S01 2714 [Microsoft][ODBC SQL Server Driver][SQL
2010 Aug 08
1
PATCH/RFC chain.c: update iterator code, yank from chain.c, move both to separate directory
1) code split and move
Iterator related functionality is yanked from chain.c and moved to
iterator.{c,h}. Both are moved to com32/chain and this way chain.c is ready
for further splitting.
Alternatively, partiter could be moved to com32/lib at any time in the future.
It's potentially useful for other modules (e.g. if someone wanted to code
partition dumper or editor).
2) Iterator updates
2008 Apr 24
1
[PATCH] chain.c32: fix booting from logical partitions
Booting from a logical partition failed with the "Requested logical
partition not found" error due to a wrong test for partition signature
in find_logical_partition().
Signed-off-by: Sergey Vlasov <vsu at altlinux.ru>
---
com32/modules/chain.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/com32/modules/chain.c b/com32/modules/chain.c
index
2008 May 31
1
Still blocked with chain.c32
Hi again,
I'm still blocked with chain.c32.
Does it allow drive swapping like Grub or not?
If not, how to boot a Windows system that is located on hd1 1 (instead of
regular hd0 1)?
Can't find any clue/doc on chain.c32.
Thanks
2010 Jul 27
1
chain.c32: Chainboot failed!
When you try to boot the FreeDOS kernel with 'fs' specified, chain.c32
won't boot the FreeDOS kernel.
boot: chain.c32 fs freedos=kernel.sys
Loading the boot file...
Booting...
Chainboot failed!
boot:
It would be nicer that chain.c32 will automatically correct 'fs' to 'boot'
behavior, so it won't fail.
msdos= will probably behave the same as freedos=.
- Gert
2010 Jun 28
0
[PATCH] chain.c32: pass partition number to stage2 of Grub Legacy
Grub Legacy stage2 will read the install_partition variable from
memory address 0x8208.
We only need to change the value at 0x820a to the correct partition
number:
-1: whole drive (default)
0-3: primary partitions
4-*: logical partitions
Signed-off-by: Gert Hulselmans <gerth at zytor.com>
---
com32/modules/chain.c | 13 ++++++++-----
1 files changed, 8 insertions(+), 5
2011 May 01
0
[patch X 2] chain.c32 ReactOS FreeLdr Support
Two commits available at:
http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/chain_freeldr
---
Author: Shao Miller <shao.miller at yrdsb.edu.on.ca>
Date: Sun May 1 13:49:43 2011 -0400
chain: Support loading ReactOS' FreeLdr
Use something like:
LABEL freeldr
COM32 chain.c32
APPEND freeldr=freeldr.sys
Signed-off-by: Shao
2006 Jun 30
0
chain.c32 booting windows off a second disk?
I was seeing if I could use chain.c32 to boot windows
off of a second drive. I'm pretty sure I'm using it
right. Could it be because these are sata drives?
I installed FC5 on a second sata drive I had in my
new machine. Of course Grub didn't work as I wanted so
I decided to try extlinux and if I can get it to work
I might switch to syslinux so that I can edit the boot
info in windows
2005 Oct 26
1
chain.c32 question
I am trying to use chain.c32 to boot windows xp from a hard disk. In my
pxelinux.cfg file I have the following:
Prompt 1
Default menu1
Timeout 2
Label menu1
Kernel chain.c32 hd0 1
When my system boots it gives me the following usage error
Usage: chain.c32 (hd|fd)# [partition]
Boot:
If I type chain.c32 hd0 1 at the boot prompt the system boots windows
ok. Any help would be
2010 Jun 25
1
chain.c32 GPT Support
Hello all.
Here[1] is a branch where chain.c32 can chain-boot a partition on a GPT
disk when given the partition index.
boot: chain hd1 84
(For example.)
- Shao Miller
[1]
http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/
chain_gpt
2005 Feb 04
0
PXELinux, chain.c32 and my 3com NIC
Hello!
I use the latest version (3.0.8pre5) of PXELinux, menu.c32 and chain.c32
Everything worked fine with my test-PC (when WinME was installed on the
hard disk): There is a working menu item for hard disk boot (chain.c32 hd0).
I have deleted the partition table and installed W2k (NTFS): now hard
disk boot no longer works if I use PXELinux. :-(
First I thought that there is something wrong
2010 Mar 02
2
chain.c32 "Chainboot failed!"
Hi,
I am using syslinux-4.00-pre24, -pre27 and -pre31. chain.c32 fails for pre27 and pre31 for particular configs ... shown below.
1) works on pre24, fails with error message "Chainboot failed!" for pre27 and pre31
LABEL local
MENU DEFAULT
MENU LABEL Local Boot ... (skip PXE boot)
KERNEL chain.c32
APPEND hd0 0
2) works on all three.
LABEL local
2010 Mar 11
1
Recovery console doesn't work in chain.c32 3.85 or 3.86-pre1
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
2005 Jan 10
1
chain.c32 does not work (for me?)
Hello!
I am trying to boot from the MBR of my hard disk using PXELinux.
here is the (relevant) part of my pxelinux.cfg/default
LABEL harddisk
KERNEL chain.c32
append hd0
All I get is a single dot and then the boot process stops.
What am I doing wrong?
Alex
2007 Aug 29
1
chain.c32 question
I'd like to use chain.c32 to allow the computer boot from HARDDISK if
needed.
If I use isolinux and boot from CD, the following works OK:
chain.c32 hd0
But if I boot from USB Flash Key, it sometimes work and sometimes it
doesn't and I have to use
chain.c32 hd1
(it seems BIOS assigns hd0 to the flash key sometimes, so the real
harddisk is hd1 in that case).
Is there any way to tell