search for: int13h

New module which check if the PLoP Boot Loader already has booted a CDROM or USB drive by checking for the presence of the PLoP INT13h hook. The following assembly code (NASM) can detect the PLoP INT13h hook: mov eax,'PoLP' ; Reverse of 'PLoP' mov ebp,'DKHC' ; Reverse of 'CHKD' int 13h cmp eax,' sey' ; Reverse of 'yes ' jz plop_INT13h_active Signed-off-by: Gert Hulsel...

Hello, I have a problem with a comboot 16 bits program for syslinux, I use the API openFile, ReadFile and CloseFile for read my own config file. It's ok. I use the int13h to write a floppy disk (syslinux runs on a USB stick), after the first call to int13h, all the call to openFile return an error. Do you know what's the problem? Is it possible to use int13h when we use syslinux API? Thank you and excuse my bad english... YB

I wrote a COM32 module which detects if the PLoP bootmanager was used to boot a CDROM drive or USB drive, by checking for the presence of the PLoP INT13h hook. The PLoP INT13h hook check works like this (NASM syntax): mov eax,'PoLP' ; Reverse of 'PLoP' mov ebp,'DKHC' ; Reverse of 'CHKD' int 13h cmp eax,' sey' ; Reverse of 'yes ' jz plop_int13_active More info: http://forum.plop.at/...

...4) other than using legacy LBA32 -- i.e., always assuming Sectors/Heads of 63/255. In NT5+, this is what it does on a "Basic Disc" which cannot store geometry information, at least through NT5.1 (XP/2003) Service Pak 1 (SP1). Unfortunately, assuming LBA32 is not compatible with Extended Int13h Disk Services. And for broken BIOSes, it can cause issues with 3rd party boot managers and disk utilities. This isn't an issue with using the Logical Disk Manager (LDM) Disk Label (Partition Table Format) aka "Dynamic Disc" because all NT5+ (2000+) instances on the system can read i...

...wo of the disk probes (by Shao; Thank you), expands the debug output, adds an additional check in the third probe and expands/reorders the debug output. At this time, it appears to resolve the MEMDISK issues that Jason Vasquez first noticed. The additional check in the third probe is to follow up INT13h AH15h with INT13h AH01h and examine CF and AH. The Dell Latitude E6400 appears to not ever set CF (like it should) with either of these two BIOS calls. I felt that attempting to compare the initial to returned registers around AH15h might not yield positive results on other systems (the results o...

Microsoft has their "boot" version of their iSCSI software initiator. Apparently this still requires that the network card be iSCSI Boot "enabled." Intel seems to be the only obvious company out there supporting it on their Server adapters - I was wondering if there are any thoughts/plans on implementing iSCSI Boot functionality in the HVM Boot ROM? Or maybe there''s

With windows, if your "virtual" floppy is drive B:, then windows will treat it specially. It will basically copy the contents into memory from real mode using int13h, knowing that it will not be able to access the device after it switches to protected mode. I asked a few days ago about support for making a memdisk image behave as drive B:, but got no answer. :-( We have our assembly language guy looking at it, but it is slow as he isn't very familiar...

greetings, i just know i have read several times on this list and in other places that on a RAID5 array that the MBR should be placed on the /boot partition. is this truly correct and if so, why? my experiences of putting the MBR on the /boot partition are contrary to that it will even work and boot that way... comments please? regards, - rh -- Robert Hanson Abba Communications

I''ve now given up trying to get grub working with my particular e1000 adapter, I''ve tried all the patches and all I can get is something that works a little bit but never past the grub menu. I''m sure I read something somewhere about a tool which would combine a multiboot image + modules into a single bootable item which could be loaded by lilo, and am hoping that the

...and that is all that the chipset needs to be able to boot in RAID mode on the existing AHCI controllers. There is no raid "card" in these systems - aka no special extra raid cpu to control anything. All the RAID BIOS does is boot the system to load GRUB ( and maybe GRUB uses the same BIOS INT13H service to load the kernel). After that, kernel drivers take over - and that is MDADM doing the rest of the job, as Intel RAID bios is MDADM compatible. Call it FAKE raid, call it BIOS raid or whatever - it is in fact just a Linux software mdadm raid - with the added ability to boot directly from...

Hi, I once again have a problem with memdisk failing to boot a harddisk image to update my Thinkpad X200s firmware. I extracted the harddisk image from the eltorito type 4 ISO using the isobar tool. Then I added memdisk using this image as initrd to my grub, rebooted and it boots into PC DOS and then freezes (ctrl-alt-del still works to reboot the system). Inside Qemu however it works fine

Hello CentOS, Does anyone know if there's a driver out there that'll enable CentOS 4.x to use the Intel Matrix SATA RAID settings on the 915 chipsets? -- Best regards, Mickael mailto:mike at kamloopsbc.com www.MickaelMaddison.com

...memdisk is fast, small conventional memory footprint and the emulated drive is writeable, very, very, cool!!! I (together with someone else) have written a real-mode Dos CD-Rom driver "eltorito.sys" (only 4KB) that supports a bootable CD-Rom drive in "no emulation" mode, using INT13h/ah=42 read calls to get the block from the CD device... Very handy for Dos based boot disks that need to have hardware independent CD-Rom support... At the moment it has some small bugs, but when it is stable maybe you can mention it in your memdisk documentation... One small question, can isoli...

Hi SysLinux, i'm using pxelinux.0 and memdisk to successfully boot dos on my PXE capable workstation. But aber the DOS boot I need to get access to Drive A: again. My DOS bootimage is putting all necessary stuff into it's own RAMdisk. How can I disable memdisk, so that it releases drive A: (does not necessarily free the allocated memory for it's RAMdisk ..) with kind regards / mit

...device). Going in details as far as I can see, it loads successfully the boot sector, OS2LDR, OS2KRNL, OS2LOGO, CONFIG.SYS but stops there after attempting to find the correct .ADD driver to load in CONFIG.SYS. I believe that the IBMINT13.I13 driver is the only way to go when it comes to using INT13h disk access (that is what memdisk does - redirect interrupt 13 calls to the ram disk it creates in memory) but if we cannot get the sources for this driver, then creating an alternate driver is the only way to go. Is there an alternate Interrupt 13 driver for OS/2? I have also looked into some...

I used syslinux 4.03 for my brand new usb-stick (16GB FAT32, no Partition Table). It works, but on some computers i get "boot error". My investigation reveals three bugs in the boot code. Int 13 function 8 destroys the contents of register ES. Ah, now it is corrected in version 4.04 pre 5. Well done. I am happy now. But there are still other bugs. Look on version 4.04 pre 5,

SYSLINUX 2.10 2004-06-18 That is all I get when I boot my system off a CompactFlash card in an IDE adapter, no matter how long I wait. What debugging steps are recommended? I'm willing to get down and dirty with assembler, and I'd appreciate suggestions of what to suspect and where to start. Details: This is a Crucial 128MB CompactFlash card in a non-hot-swap CF-IDE adapter which

OK, I have managed to get software RAID 1 running on my wonderful Proliant server but now have two challenges: 1) Fresh after an OS install and reboot, the RAID array starts to do its stuff but straight away (as part of the boot messages) I am told that the second disk is 'not ready for command' and the system hangs as soon as resyncing starts. I think this is fixed by adding an hdparm

...an access your floppy drive as B: when MEMDISK is loaded. > > -hpa > > >H. Peter Anvin hpa at zytor.com >Thu, 29 Aug 2002 00:25:32 -0700 > >Bernd.von.Osten at bccomponents.com wrote: >> >> BWLOADHI has a "bwloadhi /u" option, which uses an additional int13h >> function to trigger the unload procedure. Maybe this can be implemented in >> Memdisk as well? >> > >Something like that would work. > >> At the moment I'm thinking about a quick and dirty test program (IMDL - >> IsMemDiskLoaded), which detects the pre...

Hello, In some weeks I'm going to reinstall some old RedHat9 based servers with Promise FastTrak TX2000 "semi-hardware" RAID1 controllers. I just tried to install CentOS 4.0 on a computer with a spare card and as usual both HDD attached to the RAID1 controller are seen separately by the installer because the specific driver for the TX2000 wasn't loaded. Nothing new here, it