Hi Mark,
Sure, a good place to start is:
http://www.microsoft.com/whdc/DevToo...g/default.mspx
You can download and install the debugging tools, then once installed go to
File > Symbol File Path. In the dialog for the location of the symbols put
in "SRV*c:\symbols*http://msdl.microsoft.com/download/symbols" (no quotes).
Your boot.ini should look like:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Embedded"
/fastdetect /noguiboot
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Embedded
(Debug)" /debug /baudrate=115200 /debugport=com1
Once you get the debugger to connect hopefully you will get stop error
information that will help you with the debugging process.
Feel free to post back here if you get stuck.
HTH,
Brad
"Mark Mesich" <(E-Mail Removed)> wrote in message
news:2863A016-58FE-483A-B8F2-(E-Mail Removed)...
> Hey Brad,
>
> Yes there is a serial port, but I am not familiar with debugging this way.
> Are there any docs which may provide some more information on setting up
> this
> environment?
>
> Thanks,
> Mark.
>
>
> "Brad Combs" wrote:
>
>> Hi Mark,
>>
>> Do you have a serial port on the device that you can hook up debugger on?
>>
>> Brad
>>
>> "Mark Mesich" <(E-Mail Removed)> wrote in message
>> news:42ACB5CA-29D6-4366-A3C6-(E-Mail Removed)...
>> > Thanks for your reply Brad.
>> >
>> > Unfortunately I cant even get to the point where the FBA runs - hence
>> > there
>> > is no log. On the machines that I have been successful with the FBA
>> > runs
>> > almost immediately upon boot. However, with the machine that does not
>> > work,
>> > the Windows XP boot screen gets displayed - but nothing more. FBA
>> > never
>> > starts.
>> >
>> > Have you ever seen this before, or have any ideas?
>> >
>> > Thanks,
>> > Mark
>> >
>> >
>> > "Brad Combs" wrote:
>> >
>> >> Mark,
>> >>
>> >> Take a look at \Windows\fba\fbalog.txt to see whats happening, or at
>> >> least
>> >> you can see the last thing that was successful. If you think it will
>> >> be
>> >> helpful attach the log to this thread and maybe we can help.
>> >>
>> >> HTH,
>> >> Brad
>> >>
>> >> "Mark Mesich" <(E-Mail Removed)> wrote in message
>> >> news:A00B4E45-F221-4530-91AE-(E-Mail Removed)...
>> >> > Hi All,
>> >> >
>> >> > I have a machine which is currently running Windows XP with no
>> >> > trouble
>> >> > at
>> >> > all and I would like to build an image of XPE to run on this
>> >> > machine.
>> >> > However, I seem to be having trouble getting the resulting image to
>> >> > boot
>> >> > properly. I have done (just about everything I can think of, but
>> >> > most
>> >> > recently) the following:
>> >> >
>> >> > - Installed Windows XP
>> >> > - Installed a second drive and configured it properly.
>> >> > - Run TAP.EXE to generate the devices file.
>> >> > - Used Component Designer to generate a component for the devices on
>> >> > this
>> >> > machine (as per the tutorial)
>> >> > - Used Target Designer to build an image for the machine based on
>> >> > the
>> >> > devices component and some others as identified in the tutorial.
>> >> > (All of the above complete with no errors.)
>> >> >
>> >> > I have gone through this process on two other machines with success.
>> >> > However, on this third machine the resulting image simply sits on
>> >> > the
>> >> > Windows
>> >> > XP boot screen and never launches the FBA. The same results happen
>> >> > no
>> >> > matter
>> >> > how I build the image - i.e. targeted at C:\ withe ARC path
>> >> > multi(0)disk(0)rdisk(0)partition(1)\WINDOWS or as my second drive
>> >> > D:\
>> >> > with
>> >> > ARC path multi(0)disk(0)rdisk(1)partition(1)\WINDOWS.
>> >> >
>> >> > Does anyone have any ideas as to what I might be missing/doing
>> >> > wrong?
>> >> > Is
>> >> > there any way to log what is happening during the boot sequence to
>> >> > see
>> >> > what
>> >> > is happening (or not happening)?
>> >> >
>> >> > I am about to go insane, so any help or suggestions would be GREATLY
>> >> > appreciated!
>> >> >
>> >> > Thanks,
>> >> > Mark.
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>