Harald_Jensas at Dell.com
2006-Feb-09 06:58 UTC
[syslinux] menu.c32 error "Windows is bypassing your startupfiles"
Franga . wrote:> > Now i moved to my next step of trying to get Simple Menu's working. My> problem occurs after selecting a menu option. The image loads and > gives me this output: > > command line: initrd=images/c201.img BOOT_IMAGE=memdisk Disk is > floppy, 1440 K, C/H/S = 80/2/18 Total size needed = 1491 bytes, > allocating 2K Old dos memory at 0x9f000 (map says 0x9f400), loading at> 0x9e800 > 1588: 0xffff 15E801: 0x3c00 0x3e66 > INT 13 08: Success, count = 1, BPT = f000:98a9 > old: init13 = f0008590 init15 = f000f859 > new: init13 = 9e800008 init15 = 9e80027c Loading boot sector... > booting... > Starting Windows 98... >My guess: Someone, or something is pressing F5 right here. This is why MS-DOS/Win98 is bypassing the startup files.> > Windows is bypassing your startup files. > > Microsoft(R) Windows 98 > (C)Copyright Microsoft Corp 1981-1999 > > A:\> >// Harald
Sam Clements
2006-Feb-09 08:48 UTC
[syslinux] menu.c32 error "Windows is bypassing your startupfiles"
> > Starting Windows 98... > > > > My guess: > Someone, or something is pressing F5 right here. This is why > MS-DOS/Win98 is bypassing the startup files. >As I recall, pressing shift will do this too... -Sam
Nazo
2006-Feb-09 12:20 UTC
[syslinux] menu.c32 error "Windows is bypassing your startupfiles"
On 2/9/06, Harald_Jensas at dell.com <Harald_Jensas at dell.com> wrote:> > Franga . wrote: > > > > Now i moved to my next step of trying to get Simple Menu's working. My > > > problem occurs after selecting a menu option. The image loads and > > gives me this output: > > > > command line: initrd=images/c201.img BOOT_IMAGE=memdisk Disk is > > floppy, 1440 K, C/H/S = 80/2/18 Total size needed = 1491 bytes, > > allocating 2K Old dos memory at 0x9f000 (map says 0x9f400), loading at > > > 0x9e800 > > 1588: 0xffff 15E801: 0x3c00 0x3e66 > > INT 13 08: Success, count = 1, BPT = f000:98a9 > > old: init13 = f0008590 init15 = f000f859 > > new: init13 = 9e800008 init15 = 9e80027c Loading boot sector... > > booting... > > Starting Windows 98... > > > > My guess: > Someone, or something is pressing F5 right here. This is why > MS-DOS/Win98 is bypassing the startup files. > > > > > Windows is bypassing your startup files. > > > > Microsoft(R) Windows 98 > > (C)Copyright Microsoft Corp 1981-1999 > > > > A:\> > > > > > // > Harald > > _______________________________________________ > SYSLINUX mailing list > Submissions to SYSLINUX at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux > Please do not send private replies to mailing list traffic. > >Hmm, if you hold the CTRL key it forces the menu to appear. I'm thinking maybe if ALT or something like that were stuck, maybe that forces a bypass? Well, the only alternative explanation I can think of is that the startup files are damaged or something or maybe you have it set to ignore them via a modified MSDOS.SYS file (when I say a modified MSDOS.SYS file, don't panic, since Windows 95, it was changed to just a hidden system text file with some configuration data tossed in, so just unmark the hidden and system attributes and you can edit in any text editor.) That or someone actually IS hitting F5. d-: That is what it means when it says bypassing, that it has been told to do so. In this case unintentionally, but, nonetheless, something's telling it to do so. I'd say particularly check that MSDOS.SYS doesn't have some option to do this specified. I can't remember what would do it off the top of my head, but, it should be pretty self explanatory and say something obvious. Of course, also ensure CONFIG.SYS and AUTOEXEC.BAT are both 100% readable and in the ordinary format. If you work on disk images in linux or something, you need to make sure that you get both CR and LF at the end of each line as well since obviously these are MSDOS files, not *nix.
Franga .
2006-Feb-09 22:45 UTC
[syslinux] menu.c32 error "Windows is bypassing your startupfiles"
This only occurs when i use the menu.c32 i have 2 configuration files this is my standard: PROMPT 1 DEFAULT local DISPLAY messages/ghost TIMEOUT 100 label local LOCALBOOT 1 label g KERNEL memdisk keeppxe APPEND initrd=images/c201.img When i use this and hit "g" i have no problems, PXE gets the same image i used in the menu. Loads it, and goes into ghost. My disk image has an automated processs, and i know 100% it works we have imaged over 60 machines in the last 2 days using the configuration i give you above. the problem only occurs when we switch to using a menu. i can garentuee no keys are stuck and no user is pressing anything (there is no users here till monday). i have tried on multiple machines and get the same responce each time. My Disk: Loads everything into a RAM Drive, Initilizes the network card, Gets its IP from DHCP, Mounts a share, Runs GHOST with its correct ghost image, Runs GHOSTWALKER to change the PC name and SID Reboots. As i said this process works 100% when i dont use the menu configuration. But as soon as i convert to the menu config i get the "Windows is bypassing startup files". I have tested the 4 seperate images that work in 4 seperate rooms perfectly. And as stated i can garentuee no keys are stuck and no1 is pressing any key at all. any thoughts? - Zen
Reasonably Related Threads
- menu.c32 error "Windows is bypassing your startup files"
- ONTIMEOUT LOCALBOOT -1 and menu.c32 -
- Usin ISO Linux & Memdisk to create a Viritual Floppy drive that Linux & Windows can load driver disk from.
- MEMDISK - floppy=1 Outputs: Disk is hard disk, 1440 K, C/H/S = 80/20/18
- OFF TOPIC: Chainloading CD-ROM boot after ISOLINUX + MEMDISK.