TAP on Target

  • Thread starter Thread starter Richard
  • Start date Start date
R

Richard

Okay, I'm going a little nuts here.
I designed an image for my target last year and all is fine. Now that board
has hit the EOL.
I'm trying to TAP to run a report on the new target board. I boot from the
Windows XP Pro and I get the message saying I need to activate again and new
installs say too many activations. BTW, This licensed version of XP Pro
only gets used for development of new targets (Running TAP and that is
all). So I try the CD1 and Boot into PE but PE can not find the network
adapter.

How are others working around all this? I have SP2 FP2007.

Thanks,
Richard
 
Just installed Pro again from scratch, it gives 30 days so that is okay. I
just don't need to activate it....
 
Just installed Pro again from scratch, it gives 30 days so that is okay. I
just don't need to activate it....
 
The 30 days should be enough. Make sure that you install the drivers and then
run TAP. Capture all the OEM#.inf files in the \windows\inf directory. These
will be sued to create any missing driver components.

--
Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit
 
Hey Mike, Long time....
Did you ever run across the EWF Delphi API header files for SP2?
I sent you some a long time ago for SP1 but of course the api changes some
in SP2.

Richard
 
Richard said:
Hey Mike, Long time....
Did you ever run across the EWF Delphi API header files for SP2?
I sent you some a long time ago for SP1 but of course the api changes
some in SP2.
Click to expand...

Hi Richard,

No, I still haven't found the time since calling EWFMGR.EXE works fine
for my purposes and it was easy to add communication to FBWFMGR.EXE.

I use a component called DosCommand to run these programs.
http://maxxdelphisite.free.fr/doscmd.htm
 
Back
Top