search for: 33xx

If the ldlinux being processed is garbage, the search for LDLINUX_MAGIC will overflow its buffer - fix that. I did encounter this issue in Rufus as, due to notorious incompatibilities between different versions of ldlinux.sys and the com32's residing on an ISO, we download a version specific ldlinux.sys from our server... which may get trashed if the user sits behind one of these

...aviour. Maybe boot_image memory always will be a multiple of 4; I don't know. With the proposed patch's uintptr_t stuff, if the magic isn't found: * <------- boot_image_len dictates the final byte * <-------- wp is less than boot_image_len 00001111222233XXYYYY <- XX are out-of-bound bytes * <---- Where wp is when the loop breaks * <------ As far as any kind of pointer should point * <-------- When the loop should break, as 33XX can't contain the magic Fingers crossed that my math is worki...

...now what happend when i dial 4 digit number my asterisk wait for few digit why when i press # key it is dialing fast but without # wait for few number is there any configuration for dialplan I have setup asterisk with avaya system i have 5 avaya system on 5 location i use 16XX,22XX,33XX,44XX,20XX to reach avaya extentions but when i press 1627 then it is wait for 5 second and then rining start alternative press '#' what is the method to break this space of waiting after dialing my extention.conf ;North Delhi NOC Extention exten => _16XX,1,Dial(SIP/mediant/${EXTEN},60)...

...ork something better here, that could eliminate this cast. > With the proposed patch's uintptr_t stuff, if the magic isn't found: > > * <------- boot_image_len dictates the final byte > * <-------- wp is less than boot_image_len > 00001111222233XXYYYY <- XX are out-of-bound bytes > * <---- Where wp is when the loop breaks > * <------ As far as any kind of pointer should point > * <-------- When the loop should break, as 33XX can't > contain the magic You're right....