How to Debug routine in Infopackge

Hi All,
  I have an ABAP routine in the Infopackage. How can I debug the code.
Thanks.
Regards,
bw_newbie

Hi,
See here:
debug abap routine in infopackage
debug the code at infopackage level
Hope this helps...

Similar Messages

  • How to debug routine in process type "Deletion of overlapping requests"

    Hi all,
    I created a process chain including a process of the type "Deletion of overlaopping requests from InfoCube".
    In this process I created a routine to decide which requests to delete. Now I would like to debug this routine, but do not know how.
    Merely setting a breakpoint does not seem to help.
    Does anyone have a hint how to debug this routine?
    Many thanks,
    Stefan

    Hi,
    put a "BREAK-POINT." statement into your code (don't forget to remove it afterwards). Then you activate your process chain and go the menu Execution at the top of RSPC. There you choose "Execute synchronous to Debugging". The process chain should then kick off and stop at the point where you put the break point.
    Hope it helps.
    Stefan

  • How to debug a ABAP Routine which is in Infopackage Data selection Tab

    Hi ,
       Please let me know How to debug a ABAP Routine which is in Infopackage Data selection Tab.

    Hi,
    You can try to create infinite loop:
    DATA: STOP.
    WHILE STOP IS INITIAL. ENDWHILE.
    Start InfoPackage and then go to SM50 and swich on debugging for your process. Then in debugger you can change value of STOP variable to skip the loop.
    Krzys

  • How to debug start routine for the custom code?

    Hi Experts,
    Can anybody tell me how to debug the start routine? Also could you please guide me where to write the custom code in the start routine.
    Thanks in advance.
    Sharat.

    Rajkumar,
    Thank you for your help. but the blog link that you send it to me does not mention anything about ABAP debugger screen.
    What should I do once I get in to the ABAP debugger? the link only tells how to get to the ABAP debugger that I know.
    Also it say that I have to use the infinite loop to debugg the start routine.
    Can anybody tell me how to debugg start routine with the scren shots please. I don't know how to use infinite loop in the start routine. Is their any easy process step by step to see my particular record behavior in the start routine?
    I will assing you the points. again thank you.

  • How to debug the routines in the transformations as well as start,endroutin

    Hi all,
    Can anyone explain me how to debug the routines in the DTP, as well as the how to debug the start and end routines>?
    I am new to bi 7 ?
    thanks
    Pooja

    Hi,
    In Execute tab change the processing Modes to 'serially in the dialog process for debugging' . then you can see the option 'simulate'.
    http://help.sap.com/saphelp_nw70/helpdata/en/45/8594ebd17f1956e10000000a11466f/content.htm
    Step by step doc,
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0038ad7-a0c7-2c10-cdbc-dd674682c8e7?quicklink=index&overridelayout=true

  • How to debug payment advice program

    Hi experts,
    iI copied program from RFFOUS_C and named as ZRFFOUS_C.
    payment advice is printing through ( ZRFFOUS_C) this program?
    If yes  how to debug this program ?.I want to konw the values printing in payment advice sheet  came from which subroutine.?
    I tried but i didn't get.I tried in this way, put the break point in the program and execute then fill the values and execute
    then the following message is displayed "A:FO:098 29.01.2009 PNB".
    I want to konw document (REGUP-BELNR) YOUR DOCYUMENT (REGUP-XBELNR) about this values came from which sub routine.
    If u know anybody pls gime the answer.pls help me in this .

    well at first you need to set a breakpoint somewhere in your program.
    Then you need to check if your program is customized for payment slips, otherwise standard program will get triggered but not yours.
    And finally you probably need to switch on "update task debugging" since output types are quite often processed in update task.

  • How to debug through DTP in quality?

    Hi Experts,
    Please shed some light on how to debug through a DTP in quality? I am not able to find my code.
    I have a charcteristic routine & end routine written.
    I am able to get to the debugger screen, through DTP ( serial debugging) / manage DTP.
    But i am not able to find my code.
    Sharat

    HI
    Try to  change the breakpoints (see push buttons). I think by default none is set.
    /people/community.user/blog/2007/03/29/sap-netweaver-70-bi-extended-capabilities-to-debug-a-data-transfer-process-dtp-request

  • How to debug the smart forms

    Hi All,
    Can any body guide me how to debug the smart forms.
    Thanks & Regards,
    Satish.

    Hi,
    The the best way to debug the form is to put a breakpoint in the function module generated by the smartform.
    Procedure:
    Open the smartform we want to debug.
    Goto Environment -> Function module name.
    Open the function module in SE37. From the menu GOTO -> main program. Open the last include.
    This incude contains the entire code ie the code we have written in initalization + form routines + program lines + sap generated code.
    Even we can search for the text nodes, folders, templates, tables, graphics, address nodes etc with their names.
    Put a breakpoint at any point you want.
    If we issue any doc which triggers this form, when the control reaches the break point it will stop.
    Please note that hard-coding the break points in the code ( Program lines ) is not recommended and it can´t be done unless if it is development server.
    So, always put a session break point in the related function module.
    We can use SFTRACE transaction to know the sequence of the control flow.
    If you want to break at each and every text that is printed on the output form put the break points in the forms.
    1. %write_text  to break at text element.
    2. %WRITE_TEXT_MODULE  to break at text module.
    3. %WRITE_INCLUDE_TEXT  to break at include text.
    Please put a break point at the first sy-subrc check.
    If the control reaches this point, you can find the name of the element in the varible NAME and the content in the text node in %TEXT.
    Its easy to understand the sequence of the printing if we put a breakpoint as stated above.
    Regards,
    Satish.

  • How to debug a runtime stack underflow error?

    I'm really struggling to resolve a stack underflow that I'm getting.  The traceback I get at runtime is:
    VerifyError: Error #1024: Stack underflow occurred.
    at flash.events::EventDispatcher/dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at flash.net::URLLoader/onComplete()
    This is particularly difficult to debug because when I run in debug mode it does not happen at all.  It only happens when compiled as a release.
    Does anyone have any tips on how to debug a Stack Underflow?  Are have a clean explanation of what that means for Flash?
    In case it helps, this error is occurring when I click a button whose handler makes an RPC call, which uses a URLLoader, an AsyncToken, and then invokes the set of AsyncResponder instances associated with the AsyncToken.  With some server-side logging as well as some logging hacked into the swf, I know that the UrlLoader is successfully doing and GET'ing a crossdomain.xml file, is correctly processing it (if I wreck it, I get a security error), and is also successfully completing the "load" request (the server sends the data)... the underflow seems to be happening in the Event.COMPLETE listening/handling process (as is, of course, implied by the traceback as well).
    mxmlc used = from flex_sdk_4.5.0.20967
    Example player (I've tried a few) = 10.2.153.1

    Peter Blazejewicz wrote:
    crossposted:
    http://stackoverflow.com/questions/6270837/how-to-debug-a-runtime-stac k-underflow-error
    Yes... I intended to say so here but didn't get to it yet.  View traffic was extremely low here and I thought I'd see how stackoverflow compared.  I tend to check there first for most languages usually, but thought I'd try here as well to see if I should break that habit.
    As per the SO post, my specific problem was resolved by switching my variable initialization routine from the "initialize" application event, to the onCompletion event.  Although I am obviously "happy" about this since this issue cost me a lot of time and hair, it does not really indicate how I would go about debugging such an internal error in the future, so the question is technically unanswered.
    As to the question from Flex harUI, I am compiling indirectly via the MXMLC in the SDK, through the Amethyst Visual Studio plugin (which I'm auditioning).  The only libraries involved are from the flex_sdk_4.5.0.20967 SDK.  The project is quite small (a test project), consisting only of 1 MXML file and 2x .AS files.

  • WHERE AND HOW  IS DEBUGGING USED ?

    WHERE AND HOW  IS DEBUGGING USED ? PLEASE GUIDE ME WITH EXAMPLES.
    REWARD POITS GUARENTEED !!

    Hi,
    check these...
    ABAP DEBUGGING
    http://help.sap.com/saphelp_webas620/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9cbb7716-0a01-0010-58b1-a2ddd8361ac0
    Debug Program scheduled Background
    Re: Debugging Report which is scheduled in background
    3 types update,normal and system debugging
    check this for update debugging
    If you set "Update Debbugging" you can debug the codes which works in update tusk.
    SAP std often runs the routine (function or form) to update the database in update tusk mode, these routine start as soon as a commit work is done.
    The commit is called at the end of the program, so you can't debug them by "normal debbugging" because it ends as soon as the program ends
    or----
    All the database updates are performed by the update work processes by calling the functions/subroutines in update tasks.
    These tasks are executed after a commit work is reached in the application. By default you cannot debug these functions.
    TO debug these u need to explicitly activate update debugging.
    for system debugging check the below link
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/5f0640555ae369e10000000a155106/content.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/frameset.htm
    For debugging tutorial:
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/5a/4ed93f130f9215e10000000a155106/frameset.htm
    http://www.sapdevelopment.co.uk/tips/debug/debughome.htm
    http://www.sap-basis-abap.com/sapab002.htm
    System Debugging
    If you set this option, the Debugger is also activated for system programs (programs with status S in their program attributes). When you save breakpoints, the System Debugging setting is also saved.
    Update Debugging
    Update function modules do not run in the same user session as the program that is currently running in the ABAP Debugger. These function modules are therefore not included in debugging. Only if you select the Update Debugging option can you display and debug them after the COMMIT WORK.
    Normal Debugging
    Normal debugging is the one we do it by the normal dynamic break points or by /H or by using stattic break points.
    You can switch to diffferent debuggin modes while processing.
    BREAKPOINT
    In the source code we set the Break-point there by clicking the stop button, the system will stop there when you execute the program.
    Watchpoint
    For watchpoints, we need to give some condition and when this condition is satisfied, program will stop
    example : if you want to debug only
    for matnr value 100 than set watch point
    matnr = 100. when value reaches 100 than
    program stops at that point.
    more at
    http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/content.htm
    check these documents as well
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/abap/abap-runtime-tools/the%20new%20abap%20debugger%20-%20an%20introduction.pdf
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/f720ea47-0801-0010-f7a3-bd37d44fee8d
    here r some links for debugging...
    Go through these threads for more information on debugging,
    1) debugging
    2) debugging
    3) Debugging
    4) Debugging
    some more links .....
    Introduction: http://www.saplinks.net/index.php?option=com_content&task=view&id=24&Itemid=34
    A PDF file to know knowledge about Debugging
    Some more links:
    http://www.sap-basis-abap.com/sapab002.htm
    Debug Background Programs: http://www.sapdevelopment.co.uk/tips/debug/debug_backjob.htm
    Debugger: http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
    Cheers
    VJ

  • How to debug the LSMW coding???

    Hi Experts,
    Any one please tell how to debug the lSMW codings?
    Thnx,
    Mohana

    Hi,
    Go to the 5th Step that is
    "5 Maintain Field Mapping and Conversion Rules"
    select this radio Button and execute then
    you will maping your defining fields to source structure fields
    then where ever you want to write validations
    you just select that field and click on RULES tab
    then select radio-button User defined routine
    then you will get a window
    you just click on continue button
    then you will get a PERFORM opposite to your selected field
    save and come back
    then select the 6th radio button
    that is " 6 Maintain Fixed Values, Translations, User-Defined Routines"
    and execute
    there you will find your user defind routine
    you just double click on the routine
    then you will get a editor for writing your code for validations
    you just pass p_in as input and you will get the result in p_out parameter
    then you will put a Break point or put command like "BREAK-POINT"
    then it will automatically triggered while running this project.
    To view your generated code, you need to bring it up in the initial screen of your object.To do so,
    click on the User Menu button & check the Display Read Program & Display Conversion Program will take
    you into the generated code. Place your soft breakpoint as you normally do.
    Another option: go to the step DISPLAY READ PROGRAM or DISPLAY CONVERTION PROGRAM.
    Now you will see the ABAP editor with the code. Place the breakpoint (soft break point using STOP button on application tool bar) where ever you desire.
    Regards.

  • How 2 debug a Perform subroutine in sap script

    Hi,
    I have a perform endperform in Script. But tht is not working in some case. i m trying to debug but i m not able to go inside the routine and see wht it is doing? . can any one help me how to debug a subroutine in sap script.

    Hi Panigrahi,
    1) Put a break point in your perform.
    2)  YOu should change the dispatch option in your Output screen of the transaction which triggers your sap script. The dispatch option should be 1 (Send with a periodically scheduled job).
    Then save your transaction.
    3) Go to se38 and run the program RSNAST00.
    Give the Object Key as the Document Number for which you are triggering the script output.
    The control will stop in your perform.
    Regards,
    Ravi

  • How to debug in SAP Netweaver Developers Studio?

    Hi there,
    I am trying to debug and slove my error in SAP NWDS.
    I am building portal application->JSPDynPage
    I am trying to debug the jsp code behind page, it doesn't realli give error message like the java beans does.
    I am quite new to this and do not know how to set the function to test and debug this page can anyone provide any solution ?
    I have have this prob pls refer to this link
    <a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=192104">https://www.sdn.sap.com/irj/sdn/thread?threadID=192104</a>
    Thanks loads
    Quatre

    Hi Quatre ,
    -Select the breakpoints in your Dynpages /beans in ur project
    -To debug u have to change the prespective to debug which u can find in
    window/open prespective /Debug in NWDS
    -Select the Run/Debug or the Debug icon in the toolbar.
    -Fill the project name ,application name in  the in the wizard opnend .
    - Follow the debugging using the next step over F6 ,step return F7 keys .
    These link may be helpful:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/66/547f09281d464b951c9a3a6b06a12d/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/a8/def86ab54da5418a3575373934ca00/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/d4/31e24044b80b06e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/be/cffcb407c67842b122bd1296dc810f/frameset.htm
    U can always find out the way in the PDK development /how to debug/
    ie in NWDS /HELP /SAP WAS AS Documentation /SAP J2ee Enterprise Java Beans/Java development User Guide /Running and Debugging
    Cheers,
    Swathi Rao
    Do offer pts:-)

  • How to debug web app with weblogic?

    I wrote a web app that includes jsp files and some javabeans, then I put the jsp files to directory
    mydomain\applications\DefaultWebApp
    then I complied javabeans and put those classes to
    mydomain\applications\DefaultWebApp\WEB-INF\classes
    Then I start the weblogic,it runs very well.
    I modified some javabean, complie them and put classes override the old classes,
    but the web app can not find the new classes.
    Any one know How to debug web app(with javabeans) in weblogic?
    thanks!

    how to config the hot deploy?
    thxSorry, for this delay in responding. I had set notify me with email option in Watch This topic; but I never did get any email notification.
    I use wls6.1; I think the process may be very similar to this in wls8.x. In wls6.1 (sp5), this is done via the -
    Dweblogic.ProductionModeEnabled=False or
    Dweblogic.ProductionModeEnabled=True
    in the startup cmd/sh script. Out of the box, wls6.1 is set to Dweblogic.ProductionModeEnabled=False which automatically enables hot deploys.

  • How To: Debug missing Drivers in MDT

    The definitive post on missing drivers in MDT (most comprehensive list I've done so far)…
    Please to NOT post questions from this thread, instead create a new thread.
    How to debug Network Driver Problems
    One of the earliest hurdles an MDT administrator will come across is the management of device drivers, specifically networking drivers. With most other drivers, like Audio, printer, and video drivers, a quick call to Windows Update or install over the network
    will resolve the Installation. However unless the Network (and storage) Drivers are installed into Windows from the start, it will be much more difficult to install the rest of the system.
    This post should help you get started if you find a machine that did not install a device driver properly, and you want to know how to find and import the correct drivers.
    Installing network drivers in the
    full OS
    Step 1 - Try network connection again
    It's possible that you might get a DHCP error from MDT, but when you try again later to connect the Deployment Share it works! This may be caused by a slow or malfunctioning DHCP server in your network. Re-check your DHCP servers, ensure that PortFast is enabled
    on your routers. If all else fails get your network administrators to document the DHCP delay. A long delay in modern networks is unnecessary. 
    Step 2 - Verify connectivity
    You may not have a driver problem but a network problem. Check the physical connection on the computer (Network installs on MDT *REQUIRE* a wired network connection, no Wi-Fi). Open a web browser. Check the IP Address (ipconfig.exe /all). Ping the Deployment
    Server, manually connect to the Deployment Share. IF you can't connect to the Deployment Share, neither can MDT.
    Step 3 - Find the Correct Driver Package
    Before you load the driver into MDT, first verify that you have the correct driver. There are scenarios where you may *think* you have the correct driver, but the driver will never run because the package is designed for a different OS/SKU/Platform/whatever.
    Install the driver package by:
      ○ Open the Device Manager (devmgmt.msc).
      ○ Find the network device in the list (ensure this is the wired device, not the wireless device)
      ○ Right click on "Properties" and click on the "Details" tab.
      ○ From the "Details" tab, select the property "Hardware Ids" select all the values, and copy to the clipboard, it would be a good idea to save for later. Should look something like:
          PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA&REV_04
          PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA
          PCI\VEN_8086&DEV_1502&CC_020000
          PCI\VEN_8086&DEV_1502&CC_0200
      ○ From the "Driver" tab, click on "Update Driver…", click on "Browse my computer for driver software" locate the driver package on the local machine or USB Drive, and install the package.
      ○ You should get a confirmation that the driver package was installed.
      ○ IF you do not get confirmation, MDT driver installation may not work.
     Windows will install the driver starting with the *.inf install package, and will typically include a *.sys (binary) and a *.cat (digital Signature). If the driver package has been re-packaged into a *.cab, *.zip, or other compressed *.exe file, the
    package must be extracted first. This is a hard requirement for any driver used by MDT and/or SCCM. All driver packages that are signed by Microsoft (WHQL) will be installed from the *.inf file, and you should only use devices that have the Microsoft WHQL
    Logo as a sign of quality.
     If you need a help on where to find driver packages for your devices, the 3 largest Computer OEM manufacturers supply drivers grouped by Make and Model that are easily imported into MDT and SCCM. See:
    http://deploymentbunny.com/2014/07/08/back-to-basicwhere-to-find-drivers-for-servers-and-clients/
    Step 4 - Load driver into MDT
    If you have more than 20 driver packages, or if you anticipate you will have more than 20 drivers, you should start grouping your drivers in sub-folders for organization. One popular method is to group by Computer Make and Model. Ensure that you are using the
    correct Driver Selection Profile in your task sequence. If you are unsure, disable any selection profile(s) to ensure the driver is installed correctly.
    Step 5 - Run the full MDT installation
    During installation MDT will perform the following:
      ○ Run the PNPEnum.exe utility and capture output to PnPEnum.xml. The VEN_Xxxx and DEV_Yyyy from the "HardwareIDs" property above must be present in this list. Otherwise we won't have a match.
      ○ Search through the %DeployRoot%\control\drivers.xml file looking for a match for the HardwareID. MDT may filter the search based on the folder search type.
      ○ MDT will copy each matching driver to the local c:\drivers directory using the xcopy.exe command. You can search (grep) for the string "xcopy" in the ZTIDrivers.log file, that will get you list of all driver packages matched by MDT.
      ○ MDT will allow the machine to boot into the NEW OS, and Driver Installation will begin in the OS. IF there are multiple drivers found and copied locally, the Windows (not MDT) will determine the best one. The c:\windows\inf\SetupAPI.*.log files
    will detail which drivers copied locally were installed (or *not* installed).
    Installing Network Drivers in
    WinPE
    Step 6 - Try the network connection again
    (See above
    Step 7 - Verify Connectivity from within WinPE
    Verifying network connectivity will be a bit more difficult in WinPE, since we have a limited User Interface, so all investigation must be done in the debugging mode (Press F8) cmd.exe
      ○ Try connecting to the Deployment Share:
      c:\> net use * \\MDT\DeploymentShare$ /u:UserDomain\UserName *
      ○ Try pinging the Deployment Server:
      c:\> Ping.exe MDT.Corp.contoso.com
      ○ Verify that you have an IP address ( ipconfig /all ) If you have an AutoConfiguration address - Driver OK - WinPE can't reach the DHCP server. If you have "Media Disconnected" - Driver OK - Physical adapter not plugged to network. If
    no devices are listed - Driver bad - Driver not installed.
      ○ Check the x:\windows\system32\WpeInit.log - This log will show the network driver (if found) being installed.
    Step 8 - Verify driver packages are getting included into WinPE
    Firstly, verify the correct driver package from within the full OS above. By default MDT will import *all* Storage and Networking drivers into your WinPE image. However it is possible to change the subset of files copied via "Selection Profile" or
    other method. Cross check your WinPE Driver Settings.
      ○ From within the MDT console, right click on the root of your Deployment Share and select properties.
      ○ Click on the "Windows PE" tab, and the "Drivers and Patches" sub tab for both x86 and x64.
      ○ Your Network Drivers package must be in the "Selection Profile" if enabled.
    Finally verify that the correct Network Driver package is being copied to WinPE. If necessary this may include setting up a debugger to watch the MDT Provider build the WinPE Image from scratch. My preference is to use the SysInternals 
    http://live.sysinternals.com/Dbgview.exe tool.
      ○ Open up the MDT console.
      ○ Download and run the DbgView.exe tool.
      ○ Update the deployment share in question.
      ○ The DbgView tool should show what drivers were copied to each WinPE Image.
    Other
    Whenever you add a driver into the MDT console, you must update the deployment share for that drivers to be added to your WinPE Image. If you are unsure, select "Completely regenerate the boot images." to ensure the drivers is imported. Additionally,
    you must copy the updated LitetouchPE_x??.wim and *.iso files to the other consumers of the WinPE image like WDS/PXE and or any USB offline media.
    Note that some Broadcom NetXtreme class of drivers have a multi-function driver architecture that may have difficulty loading in WinPE. Ensure that you load the "RIS" class of drivers from Broadcom in your MDT environment. 
    Note that by default MDT does *NOT* support the installation of Windows over Wireless network devices (Wi-Fi). The MDT installation sources must either be available through wired networking, or offline (USB Flash) media.
    This post does not discuss origination of drivers within MDT ( Chaos vs. Total Control ), that is a different topic.
    http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
    Further Help
    If you are still having problems with drivers in via MDT, ask the experts in the MDT Technet Forum:
    Include a short description of the problem. Including the Make/Mode if necessary.
    Include the HardwareIDs from the Device Manager (Devmgmt.msc) into the post (from above).
    Copy your known good driver package (step 3 above) to OneDrive.
    Copy the following log files to a public site like OneDrive and include the link:
      ○ PnpEnum.xml (from Client)
      ○ Bdd.log (From Client) - or at least the ZTIDrivers.log file.
      ○ c:\windows\inf\SetupAPI.*.log (from client)
      ○ %DeployRoot%\control\Driver*.xml
      ○ %DeployRoot%\control\SelectionProfile*.xml
      ○ %DeployRoot%\control\settings.xml (if problems in WinPE)
      ○ x:\windows\System32\WpeInit.log (if problems in WinPE)
      ○ If the MDT server is not including your driver package in WinPE include the DBGView log.
    This post is by Keith Garner - Keith was a developer on the MDT team where he developed the ZTIDrivers.wsf script, he also worked for the Windows Hardware Quality Labs as a technical PM on Driver Quality, and developed samples for the
    Microsoft Device Driver Kit (DDK) specifically around the area of Device Driver installation in the OS (Windows NT 5.0, 2000 and Windows XP). (So yes, I know drivers :^).
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

    OK. I have redone the drivers for WinPE which has reduced the image size by about 200MB. Unfortunately the problem persists.
    Is there anyway to turn on some sort of boot logging so I can see what driver it is failing on?
    I am also still seeing the weird behavior of it working over PXE but blue screens when booting from USB. Can anyone explain that?
    JJ

Maybe you are looking for