Displaying 20 results from an estimated 90 matches similar to: "[elflink] diskstart.inc:420: error: Sector 1 overflow by 5 bytes"
2018 Jan 03
2
Structure of VBR in FAT32?
Gene, thanks for doing "Reply-All". I only get digest, so this keeps me in
the loop. Appreciated.
> which appears to be included in diskstart.inc. I will have to dig in and
> see
> > how this all gets compiled (pointers always appreciated :-) ).
>
> Yes.
>
Is the build process documented? Or am I just going to have to plod through
the makefiles?
> As Ady said,
2018 Jan 06
2
Structure of VBR in FAT32?
>
> > Is the build process documented? Or am I just going to have to plod
> through
> > the makefiles?
>
> I don't think so.
>
Oh well...
> > 1. Run installer
> > 2. Installer loads ldlinux.sys onto the filesystem (and copies
> ldlinux.c32,
> > but irrelevant for now).
> > 3. Installer calculates which blocks in the filesystem contain
2018 Jan 06
0
Structure of VBR in FAT32?
On Sat, Jan 6, 2018 at 12:34 PM, Avi Deitcher <avi at deitcher.net> wrote:
>> > Is the build process documented? Or am I just going to have to plod
>> > through
>> > the makefiles?
>>
>> I don't think so.
> Oh well...
>> > 1. Run installer
>> > 2. Installer loads ldlinux.sys onto the filesystem (and copies
>> >
2018 Jan 05
0
Structure of VBR in FAT32?
On Wed, Jan 3, 2018 at 2:38 AM, Avi Deitcher <avi at deitcher.net> wrote:
> Gene, thanks for doing "Reply-All". I only get digest, so this keeps me in
> the loop. Appreciated.
>
>> > which appears to be included in diskstart.inc. I will have to dig in and
>> > see
>> > how this all gets compiled (pointers always appreciated :-) ).
>>
2010 Dec 18
1
diskstart.inc: PartInfo sub-constants seen as local labels
I'm working on a debugging/diagnostic image in order to debug/diagnose
an issue with very recent machines using a UFD (USB Flash Drive) which
really _should_ be partitioned but someone decides to be a little too
quick and uses it raw. (FAT* file system on /dev/sdb rather than
/dev/sdb1).
Anyways, I've got a successful first iteration that'll say what the
BIOS thinks about geometry and
2010 Dec 21
2
[PATCH][git-pull] core/diskstart.inc
git://git.zytor.com/users/genec/syslinux.git
Branch core-diskstart-boot-for-hpa.
I found that INT 13h AH 08h in BOCHS used ES, DI, at least when using
a partitionless HDD, causing "Boot error" from the magic check as it
was loaded to the wrong location. HPA suggested wrapping INT 13h with
the push/pop for ES's safety. This then lead to checking over for all
int 13h calls in
2010 Dec 31
0
[PATCH][git-pull] core/diskstart.inc: Fix DS in verify_checksum
git://git.zytor.com/users/genec/syslinux.git
Branch core-diskstart-chkerr-for-hpa
verify_checksum is built to allow for segment wrap (ldlinux.sys larger
than 33280 bytes if my math is right). If the wrap occurs, DS is no
longer 0. If there's a checksum error after DS is no longer 0, it
won't be able print checksumerr_msg properly.
2 commits: 1 to make the fix in verify_checksum; the
2012 Aug 14
1
[GIT PULL] elflink fixes
Hi Peter,
The main part of this pull request includes commits that try to replace
as many __intcall() invocations as possible. Some remain, but not many
(and eventually they'll be gone too). There's also a patch to make
better use of ld's --as-needed option and various other bug
fixes/cleanups.
The following changes since commit ff7334a2ce536b7f4b1f6d6f93ff4e285a3bd45a:
Only
2006 Apr 01
0
CESA-2005:420 None CentOS 4 ia64 kernel - Updated kernel package
CentOS Errata and Security Advisory 2005:420
https://rhn.redhat.com/errata/RHSA-2005-420.html
The following updated files have been uploaded and are currently
syncing to the mirrors:
files:
updates/ia64/RPMS/kernel-2.6.9-11.EL.ia64.rpm
updates/ia64/RPMS/kernel-devel-2.6.9-11.EL.ia64.rpm
updates/ia64/RPMS/kernel-doc-2.6.9-11.EL.noarch.rpm
2006 Apr 01
0
CESA-2005:420 None CentOS 4 x86_64 kernel - Updated kernel package
CentOS Errata and Security Advisory 2005:420
https://rhn.redhat.com/errata/RHSA-2005-420.html
The following updated files have been uploaded and are currently
syncing to the mirrors:
x86_64:
kernel-2.6.9-11.EL.x86_64.rpm
kernel-devel-2.6.9-11.EL.x86_64.rpm
kernel-smp-2.6.9-11.EL.x86_64.rpm
kernel-smp-devel-2.6.9-11.EL.x86_64.rpm
kernel-doc-2.6.9-11.EL.noarch.rpm:
2006 Apr 01
0
CESA-2005:420 None CentOS 4 i386 kernel - Updated kernel package
CentOS Errata and Security Advisory 2005:420
https://rhn.redhat.com/errata/RHSA-2005-420.html
The following updated files have been uploaded and are currently
syncing to the mirrors:
i386:
kernel-2.6.9-11.EL.i586.rpm
kernel-2.6.9-11.EL.i686.rpm
kernel-devel-2.6.9-11.EL.i586.rpm
kernel-devel-2.6.9-11.EL.i686.rpm
kernel-doc-2.6.9-11.EL.noarch.rpm
kernel-hugemem-2.6.9-11.EL.i686.rpm
2009 Jul 13
0
Go t SIP response 420 "Bad Extension" back from
hi all
i have a following setup,
Xlite --------> Asterisk --------------> Outbound provider
(Dialout)------------> Client (mobile,landline phone)
Xlite registered on kamailio,
and Outbound call goes via outbound provider phone can ring properly but
when i picked up phone then it suddently hangup call giving
SIP response 420 "Bad Extension" back from ${provider IP address}
2013 Aug 30
0
Quadro NVS 420/450 regression
Hi Ben,
Someone came in to the channel to report that the outputs on the
second gpu of the NVS 420 were not being detected properly. Emil
tracked it down to the pclass == PCI_CLASS_DISPLAY_VGA check in
nouveau_display that you added in e412e95a in order to avoid
modesetting on Tesla cards. This can be worked around by specifying
nouveau.modeset=1.
I think it's a little ridiculous to require
2009 Nov 23
0
Got SIP response 420 "Bad Extension" back from inphonex.com
Hello:
New to asterisk and hoping to use for http://summitcamp.org research
station.
While trying to use with Inphonex I find that incoming calls drop after
about one minute--
-- Got SIP response 420 "Bad Extension" back from 208.239.76.169
== Spawn extension (incoming-inphonex, 210, 1) exited non-zero on
'SIP/inphonex-095bf208'
Found that I can use `*CLI> sip
2014 Nov 25
2
[PATCH] Re: [flac:bugs] #420 flac make check fails on os x
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 2014-11-24 9:49 PM, mark4o wrote:
> $ make check ... Original file size 441044 bytes. Compression
> level 0, file size 421389 bytes. ./test_compression.sh: line 42:
> let: last_size=: syntax error: operand expected (error token is
> "=")
I can reproduce on MacOS X 10.8.5. It doesn't seem to like the
assignment
2000 Feb 08
0
extra flags for cc and f77 on alpha (PR#420)
Full_Name: Albrecht Gebhardt
Version: 0.99.0
OS: alpha, osf4.0
Submission from: (NULL) (143.205.180.40)
Im not sure if this is really correct, but it has proven to work.
1. It is always a good idea to add -std1 to DEC cc's flags to force
strict ANSI language mode. It was neccessary for 0.90.x to compile,
so I used it for 0.99.0 too
2. I'm not sure if -fpe3 is neccessary for DEC f77,
2010 Dec 20
2
SIP 420
Hi;
I am running asterisk 1.6 from Fonality (Trixbox PRO).
I am trying to initiate a call FROM a softphone client to asterisk (either
an internal 4 digit extension call) or an outside line via a SIP trunk.
In both cases, asterisk rejects the call with a 420.
In this case, it?s a call from x3992 to x4415
Does this require a change on the softphone for x-call-detail?
<--- SIP read
2011 Apr 02
2
[patch] ~420 seconds in cpu_detect
playing with hdt on a soekris 4801,
Im getting HUGE delays in cpu_detect.
I added some timing code, heres what Im seeing
ACPI: Detecting
0 mS in detect_acpi
MEMORY: Detecting
0 mS in detect_memory
DMI: Detecting Table
DMI: ERROR ! Table not found !
DMI: Many hardware components will not be detected !
55 mS in detect_dmi
CPU: Detecting
0 mS in get_cpu_vendor
0 mS in "intel cpu
2011 Apr 02
2
[patch] ~420 seconds in cpu_detect
playing with hdt on a soekris 4801,
Im getting HUGE delays in cpu_detect.
I added some timing code, heres what Im seeing
ACPI: Detecting
0 mS in detect_acpi
MEMORY: Detecting
0 mS in detect_memory
DMI: Detecting Table
DMI: ERROR ! Table not found !
DMI: Many hardware components will not be detected !
55 mS in detect_dmi
CPU: Detecting
0 mS in get_cpu_vendor
0 mS in "intel cpu
2010 Mar 17
9
[Bug 27136] New: blank screen with G98 [Quadro NVS 420] (NV98) dual GPU, 4-head
http://bugs.freedesktop.org/show_bug.cgi?id=27136
Summary: blank screen with G98 [Quadro NVS 420] (NV98) dual GPU,
4-head
Product: xorg
Version: 7.5
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau