Jump to content

infuscomus

Members
 View Profile  See their activity

  • Posts

    139

  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Posts posted by infuscomus

    XP/W2k3 x86 on Modern Hardware

    in Microsoft Windows XP

    Posted

    @Dietmar

    For XP textmode setup can you check if changing these in txtsetup.sif allows you to connect windbg during text mode setup? 

    	Modifying txtsetup.sif
	If you are developing for XP or 2000, or want some other debug configuration than the default for 2003, you are going to need to change the file txtsetup.sif. The file contains the following line:
	 
	OsLoadOptions = "/fastdetect /noguiboot /nodebug"
	 
	To invoke the debugger, modify the above line to remove the
	/nodebug and add the desired debug switches, for example:
	 
	OsLoadOptions = "/fastdetect /noguiboot /baudrate=115200 /break"
	 
	The above will run the debugger off COM1 at 115200 baud and cause the HAL to stop at a breakpoint in the beginning of its initialization. The /break makes it easy to activate the verbose debug tracing to aid in finding the problem. Note that if you are modifying the txtsetup.sif file for Windows Server 2003 you could instead modify the line starting with SetupDebugOptions=. This line in the file contains the options invoked when the F8 key is pressed during setup. Changing this, if you are building a custom CD-ROM will allow you to optionally use the F8 debugger control but use different debug options. Now that you know how to modify txtsetup.sif, you need to get the changes into the installation. There are two ways to do this: Winn32.exe installation or a custom CD-ROM.

    XP/W2k3 x86 on Modern Hardware

    in Microsoft Windows XP

    Posted

    So _PmHalDispatchTable is part of struct _PM_DISPATCH_TABLE 

    typedef struct _PM_DISPATCH_TABLE {    ULONG   Signature;    ULONG   Version;    PVOID   Function[1];} PM_DISPATCH_TABLE, *PPM_DISPATCH_TABLE;

    It's initialized as null

    PPM_DISPATCH_TABLE PmAcpiDispatchTable = NULL;

     called and loaded by HaliInitPowerManagement 

    NTSTATUSHaliInitPowerManagement(    IN PPM_DISPATCH_TABLE  PmDriverDispatchTable,    IN OUT PPM_DISPATCH_TABLE *PmHalDispatchTable    );
	*PmHalDispatchTable = (PPM_DISPATCH_TABLE)&HalAcpiDispatchTable;

    I've discovered that XP only fills the table up to HaliIsVectorValid whereas Vista has some additional functions XP does not have

    HalAcpiGetTableDispatch
    HalAcpiGetRsdpDispatch
    HalAcpiGetFacsMappingDispatch
    HalAcpiGetAllTablesDispatch


    I think these functions being absent from XP's PM_DISPATCH_TABLE is why the vista acpi.sys fails since it seems to depend on these to find ACPI tables.

    @Mov AX, 0xDEAD

    what do you think?

×
×
  • Create New...