Displaying 3 results from an estimated 3 matches for "mbfts".
Did you mean:
mbft
2010 May 21
6
Get MEMDISK parameters from WinPE 32/64-bit?
Hi.
I'm working on replacing a PXELINUX/MEMDISK loaded DOS based
installation image with a PXELINUX/MEMDISK loaded WinPE ISO image. So
far everything seems to work well (appending "bigraw" to memdisk solved
booting problems on several machines), but I kind of miss the option of
using getargs.com to get/set environment variables from the memdisk
command line.
Is there any way to
2011 Aug 06
4
[PATCH] ifmemdsk.c32: Allow boot options based on presence of MEMDISK
...<option> [...]] --info [<option> [...]]\n\
+ ifmemdsk.c32 [<option> [...]] [<detected_cmd>] -- [<not_detected_cmd>]\n\
+\n\
+Options:\n\
+ --info . . . . . Displays info about MEMDISK(s)\n\
+ --safe-hooks . . Will scan INT 13h \"safe hook\" chain\n\
+ --mbfts . . . . . Will scan memory for MEMDISK mBFTs\n\
+ --no-sequential Suppresses probing all drive numbers\n\
+\n\
+If a MEMDISK is found, or if a particular MEMDISK is sought by the
options\n\
+and is found, then the 'detected_cmd' action will be taken, else the\n\
+'not_detected_cmd...
2009 Dec 08
1
[PATCH] doc: document mBFT and "safe hook"
...c:
+
+ 1. Walk INT 13h "safe hook" chain as far as possible, marking hooks as
+ having been reviewed. For MEMDISK hooks, the driver then follows the
+ pointer to the mBFT and gathers the RAM disk details from the included
+ MDI.
+ 2. The OS driver scans low memory for valid mBFTs. MEMDISK instances
that
+ have been "disconnected" from the INT 13h "safe hook" chain can be
thus
+ discovered. Looking at their associated "safe hook" structure will
+ reveal if they were indeed reviewed by the previous stage.
--
1.5.3.4
- Shao Mille...