How to config the Remote Boot Manager?

Steven,

I haven't seen such behavior with RBS.
Usually you see the progress bar showing the download of SDI file.

How big is the test1.sdi?

Could you run "SDIMgr test1.sdi" command and show us the output?

Switch to startrom.n12 boot program. At least you won't need to press F12.

Use Netmon or EtheReal network monitoring app to see the traffic between your target PC and the server. You will be interested in
the part after the dhcp handshake.

--
Regards,
KM, BSquare Corp.

> I've built a sample Embedded WinXP and want to deploy it on a target
> pc machine. And I've cofigured the Remote Boot Manager as follows:
>
> Client Mac Address: XXXXXXXXXX
>
> Action: boot
>
> Boot Server: 192.168.1.100(the develop machine)
>
> Boot Program : startrom.com
>
> Boot Image: test1.sdi (This file is stored in the
>
> "D:\Program Files\Windows Embedded\Remote Boot Service\Downloads")
>
> The boot parameters is empty.
>
> The check option "Use DHCP port(67)" has been checked. For the
> DHCP server is another machine.
>
> Now, I reboot the target pc, and then PXE appears: Intel UNDI PXE-
> 1.0 ,and then it got the IP address,and a message box "Press F12
> for network service boot" appear on the target PC, and then a dark
> screen for several seconds, and then the target pc reboot.
>
> I am not sure what's wrong? The configuration for Remote boot
> manager is wrong or the SDI file is not correct? Anyone can help me?
> Thanks!
> --
> Composed with Newz Crawler 1.7 http://www.newzcrawler.com/

Hello KM:

The sdi file size is about 256M and the actual size of the image
is about 113M.

Here is the result of running the command:

D:\Program Files\Windows Embedded\utilities>sdimgr "D:\Program
Files\Windows Emb

edded\Remote Boot Service\downloads\test1.sdi"

Microsoft (R) Windows Script Host Version 5.6

Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

SDI File Manager version 1.00.621

Copyright (C) 1999-2001 Microsoft Corp. All Rights Reserved.

SDI File : D:\Program Files\Windows Embedded\Remote Boot
Service\Down

loads\test1.sdi

MDB Type : ---

Boot Code Offset : 0x00000000.00000000

Boot Code Size : 0x00000000.00000000

Vendor ID : 0x0000 (0)

Device ID : 0x0000 (0)

Device Model : {00000000-0000-0000-0000-000000000000}

Device Role : 0

Runtime GUID : {00000000-0000-0000-0000-000000000000}

Runtime OEM Rev : 0

Page Alignment : 1 (4096 bytes)

Type Offset Size Base Address Attr

---- ------------------- ------------------- ------------------- -----
-----

DISK 0x00000000.00001000 0x00000000.10000000 0x00000000.00000000
0x00000000

It looks like the sdi file is wrong, isn't it?Thanks a lot!

BR,

steven

10/30/2004 2:05:12 AM

KM <konstmor@nospam_yahoo.com> wrote in message

<#PD26FevEHA.612@TK2MSFTNGP15.phx.gbl>

> Steven,

>

> I haven't seen such behavior with RBS.

> Usually you see the progress bar showing the download of SDI file.

>

> How big is the test1.sdi?

>

> Could you run "SDIMgr test1.sdi" command and show us the output?

>

> Switch to startrom.n12 boot program. At least you won't need to

press F12.

>

> Use Netmon or EtheReal network monitoring app to see the traffic

between your target PC and the server. You will be interested in

> the part after the dhcp handshake.

>

> --

> Regards,

> KM, BSquare Corp.

>

>

> > I've built a sample Embedded WinXP and want to deploy it on a

target

> > pc machine. And I've cofigured the Remote Boot Manager as

follows:

> >

> > Client Mac Address: XXXXXXXXXX

> >

> > Action: boot

> >

> > Boot Server: 192.168.1.100(the develop machine)

> >

> > Boot Program : startrom.com

> >

> > Boot Image: test1.sdi (This file is stored in the

> >

> > "D:\Program Files\Windows Embedded\Remote Boot

Service\Downloads")

> >

> > The boot parameters is empty.

> >

> > The check option "Use DHCP port(67)" has been checked. For

the

> > DHCP server is another machine.

> >

> > Now, I reboot the target pc, and then PXE appears: Intel UNDI

PXE-

> > 1.0 ,and then it got the IP address,and a message box "Press

F12

> > for network service boot" appear on the target PC, and then a

dark

> > screen for several seconds, and then the target pc reboot.

> >

> > I am not sure what's wrong? The configuration for Remote boot

> > manager is wrong or the SDI file is not correct? Anyone can help

me?

> > Thanks!

> > --

> > Composed with Newz Crawler 1.7 http://www.newzcrawler.com/

--
Composed with Newz Crawler 1.7 http://www.newzcrawler.com/

Hi Steven,

> I've built a sample Embedded WinXP and want to deploy it on a target
> pc machine. And I've cofigured the Remote Boot Manager as follows:

Can you give us more info about what you want to do, and exact steps that you done so far?
Have you created post FBA image on your target and then captured SDI file? In not then you can't make remote boot.

It look to me that you need a way to copy pre FBA files to your target device? If so then use first bootable XPe CD with WinPE.

Regards,
Slobodan
PS: Have you seen progress bar (you should be able to see it for some time)


"Steven" <hlsun@winbond.com.tw> wrote in message news:%23p5u8C7vEHA.1976@TK2MSFTNGP09.phx.gbl...

> Hello KM:
>
> The sdi file size is about 256M and the actual size of the image
> is about 113M.
>
> Here is the result of running the command:
>
> D:\Program Files\Windows Embedded\utilities>sdimgr "D:\Program
> Files\Windows Emb
>
> edded\Remote Boot Service\downloads\test1.sdi"
>
> Microsoft (R) Windows Script Host Version 5.6
>
> Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
>
> SDI File Manager version 1.00.621
>
> Copyright (C) 1999-2001 Microsoft Corp. All Rights Reserved.
>
> SDI File : D:\Program Files\Windows Embedded\Remote Boot
> Service\Down
>
> loads\test1.sdi
>
> MDB Type : ---
>
> Boot Code Offset : 0x00000000.00000000
>
> Boot Code Size : 0x00000000.00000000
>
> Vendor ID : 0x0000 (0)
>
> Device ID : 0x0000 (0)
>
> Device Model : {00000000-0000-0000-0000-000000000000}
>
> Device Role : 0
>
> Runtime GUID : {00000000-0000-0000-0000-000000000000}
>
> Runtime OEM Rev : 0
>
> Page Alignment : 1 (4096 bytes)
>
> Type Offset Size Base Address Attr
>
> ---- ------------------- ------------------- ------------------- -----
> -----
>
> DISK 0x00000000.00001000 0x00000000.10000000 0x00000000.00000000
> 0x00000000
>
> It looks like the sdi file is wrong, isn't it?Thanks a lot!
>
> BR,
>
> steven
>
> 10/30/2004 2:05:12 AM
>
> KM <konstmor@nospam_yahoo.com> wrote in message
>
> <#PD26FevEHA.612@TK2MSFTNGP15.phx.gbl>
>
>
>

> > Steven,

>

> >

>

> > I haven't seen such behavior with RBS.

>

> > Usually you see the progress bar showing the download of SDI file.

>

> >

>

> > How big is the test1.sdi?

>

> >

>

> > Could you run "SDIMgr test1.sdi" command and show us the output?

>

> >

>

> > Switch to startrom.n12 boot program. At least you won't need to

> press F12.
>

> >

>

> > Use Netmon or EtheReal network monitoring app to see the traffic

> between your target PC and the server. You will be interested in
>

> > the part after the dhcp handshake.

>

> >

>
>
>

> > --

>

> > Regards,

>

> > KM, BSquare Corp.

>

> >

>

> >

>

> > > I've built a sample Embedded WinXP and want to deploy it on a

> target
>

> > > pc machine. And I've cofigured the Remote Boot Manager as

> follows:
>

> > >

>

> > > Client Mac Address: XXXXXXXXXX

>

> > >

>

> > > Action: boot

>

> > >

>

> > > Boot Server: 192.168.1.100(the develop machine)

>

> > >

>

> > > Boot Program : startrom.com

>

> > >

>

> > > Boot Image: test1.sdi (This file is stored in the

>

> > >

>

> > > "D:\Program Files\Windows Embedded\Remote Boot

> Service\Downloads")
>

> > >

>

> > > The boot parameters is empty.

>

> > >

>

> > > The check option "Use DHCP port(67)" has been checked. For

> the
>

> > > DHCP server is another machine.

>

> > >

>

> > > Now, I reboot the target pc, and then PXE appears: Intel UNDI

> PXE-
>

> > > 1.0 ,and then it got the IP address,and a message box "Press

> F12
>

> > > for network service boot" appear on the target PC, and then a

> dark
>

> > > screen for several seconds, and then the target pc reboot.

>

> > >

>

> > > I am not sure what's wrong? The configuration for Remote boot

>

> > > manager is wrong or the SDI file is not correct? Anyone can help

> me?
>

> > > Thanks!

>

> > > --

>

> > > Composed with Newz Crawler 1.7 http://www.newzcrawler.com/

> --
> Composed with Newz Crawler 1.7 http://www.newzcrawler.com/

Hello Slobodan:

Thanks for your help!

OK, first , what I want to do is to port a driver from desktop
WinXP to XP Embedded. But I don't know well

about the XP Embedded. So I'd like to build a XP Embedded image for
practicing purpose. Then I start the MS Target

Designer and choose a Template from the Design Templates, and then
check the dependencies and then build the target

image. and the result is a directory. I guess the following work I
have to do is to pack the directory to a sdi file

and then deploy it on the remote machine. That's what I want to do!

But then I fail to reboot the remote machine. I do a check
according KM's suggestion and find that the SDI file

is empty. I pack the image directory again according the following
instruction

http://msdn.microsoft.com/library/de...l=/library/en-
us/dnxpesp1/html/ram_sdi.asp

but it fails in the second step,

D:\Program Files\Windows Embedded\utilities>sdimgr "D:\Program
Files\Windows Emb

edded\Remote Boot Service\Downloads\image.sdi" /readpart:f:

Microsoft (R) Windows Script Host Version 5.6

Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

SDI File Manager version 1.00.621

Copyright (C) 1999-2001 Microsoft Corp. All Rights Reserved.

D:\Program Files\Windows Embedded\utilities\SDIMgr.wsf(2294, 4)
SDIAUT.SDIFile.1

: The process cannot access the file because it is being used by
another process

But I don't find any other program is using the sdimgr.wsf.Do you
have such experipence

or would you like to give me some suggestions, This is the first time
for me to touch the XP Embedded.

Thanks a lot!

BR,

Steven

11/1/2004 9:34:46 AM

"Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message

<#6eSFL7vEHA.1988@TK2MSFTNGP12.phx.gbl>

> Hi Steven,

>

> > I've built a sample Embedded WinXP and want to deploy it on a

target

> > pc machine. And I've cofigured the Remote Boot Manager as

follows:

>

> Can you give us more info about what you want to do, and exact

steps that you done so far?

> Have you created post FBA image on your target and then captured

SDI file? In not then you can't make remote boot.

>

> It look to me that you need a way to copy pre FBA files to your

target device? If so then use first bootable XPe CD with WinPE.

>

> Regards,

> Slobodan

> PS: Have you seen progress bar (you should be able to see it for

some time)

>

>

> "Steven" <hlsun@winbond.com.tw> wrote in message news:%23p5u8C7vEHA.

1976@TK2MSFTNGP09.phx.gbl...

> > Hello KM:

> >

> > The sdi file size is about 256M and the actual size of the

image

> > is about 113M.

> >

> > Here is the result of running the command:

> >

> > D:\Program Files\Windows Embedded\utilities>sdimgr

"D:\Program

> > Files\Windows Emb

> >

> > edded\Remote Boot Service\downloads\test1.sdi"

> >

> > Microsoft (R) Windows Script Host Version 5.6

> >

> > Copyright (C) Microsoft Corporation 1996-2001. All rights

reserved.

> >

> > SDI File Manager version 1.00.621

> >

> > Copyright (C) 1999-2001 Microsoft Corp. All Rights Reserved.

> >

> > SDI File : D:\Program Files\Windows Embedded\Remote

Boot

> > Service\Down

> >

> > loads\test1.sdi

> >

> > MDB Type : ---

> >

> > Boot Code Offset : 0x00000000.00000000

> >

> > Boot Code Size : 0x00000000.00000000

> >

> > Vendor ID : 0x0000 (0)

> >

> > Device ID : 0x0000 (0)

> >

> > Device Model : {00000000-0000-0000-0000-000000000000}

> >

> > Device Role : 0

> >

> > Runtime GUID : {00000000-0000-0000-0000-000000000000}

> >

> > Runtime OEM Rev : 0

> >

> > Page Alignment : 1 (4096 bytes)

> >

> > Type Offset Size Base Address

Attr

> >

> > ---- ------------------- ------------------- ------------------- -

----

> > -----

> >

> > DISK 0x00000000.00001000 0x00000000.10000000 0x00000000.00000000

> > 0x00000000

> >

> > It looks like the sdi file is wrong, isn't it?Thanks a lot!

> >

> > BR,

> >

> > steven

> >

> > 10/30/2004 2:05:12 AM

> >

> > KM <konstmor@nospam_yahoo.com> wrote in message

> >

> > <#PD26FevEHA.612@TK2MSFTNGP15.phx.gbl>

> >

> >

> >

> > > Steven,

> >

> > >

> >

> > > I haven't seen such behavior with RBS.

> >

> > > Usually you see the progress bar showing the download of SDI

file.

> >

> > >

> >

> > > How big is the test1.sdi?

> >

> > >

> >

> > > Could you run "SDIMgr test1.sdi" command and show us the

output?

> >

> > >

> >

> > > Switch to startrom.n12 boot program. At least you won't need to

> > press F12.

> >

> > >

> >

> > > Use Netmon or EtheReal network monitoring app to see the

traffic

> > between your target PC and the server. You will be interested in

> >

> > > the part after the dhcp handshake.

> >

> > >

> >

> >

> >

> > > --

> >

> > > Regards,

> >

> > > KM, BSquare Corp.

> >

> > >

> >

> > >

> >

> > > > I've built a sample Embedded WinXP and want to deploy it on a

> > target

> >

> > > > pc machine. And I've cofigured the Remote Boot Manager as

> > follows:

> >

> > > >

> >

> > > > Client Mac Address: XXXXXXXXXX

> >

> > > >

> >

> > > > Action: boot

> >

> > > >

> >

> > > > Boot Server: 192.168.1.100(the develop machine)

> >

> > > >

> >

> > > > Boot Program : startrom.com

> >

> > > >

> >

> > > > Boot Image: test1.sdi (This file is stored in the

> >

> > > >

> >

> > > > "D:\Program Files\Windows Embedded\Remote Boot

> > Service\Downloads")

> >

> > > >

> >

> > > > The boot parameters is empty.

> >

> > > >

> >

> > > > The check option "Use DHCP port(67)" has been checked.

For

> > the

> >

> > > > DHCP server is another machine.

> >

> > > >

> >

> > > > Now, I reboot the target pc, and then PXE appears: Intel

UNDI

> > PXE-

> >

> > > > 1.0 ,and then it got the IP address,and a message box

"Press

> > F12

> >

> > > > for network service boot" appear on the target PC, and then a

> > dark

> >

> > > > screen for several seconds, and then the target pc reboot.

> >

> > > >

> >

> > > > I am not sure what's wrong? The configuration for Remote

boot

> >

> > > > manager is wrong or the SDI file is not correct? Anyone can

help

> > me?

> >

> > > > Thanks!

> >

> > > > --

> >

> > > > Composed with Newz Crawler 1.7 http://www.newzcrawler.com/

> > --

> > Composed with Newz Crawler 1.7 http://www.newzcrawler.com/

--
Composed with Newz Crawler 1.7 http://www.newzcrawler.com/

Hi Steven,

I guessed that you are at the beginning of development rather then at the end (this mean than you should created new thread and ask
new question that is not related to remote boot, you can't use it at the beginning of development).

Few starting points that you should bookmark:

Thing NG archives that you should search for all your questions first, if answer is not there then you can ask in this NG. (Googling
is usually much faster when learned how to do it then asking question and waiting for response)
http://groups.google.com/groups?hl=e...owsxp.embedded

And you should read this:
http://msdn.microsoft.com/embedded/u...e/default.aspx

For deploying image to target HDD you have few options some difficult to make some harder to use:

1. Boot computer from first XPe CD that contain Win PE and use network share.
2. Place Windows XPP on your target HDD and use it to access network and copy XPe files.
3. Boot your XPe from network and use it for deploying new image. (More advanced to do option)
4. Some other deployment program or medium (there are various approaches).

Regards,
Slobodan




"Steven" <hlsun@winbond.com.tw> wrote in message news:%23sKckR8vEHA.612@TK2MSFTNGP15.phx.gbl...

> Hello Slobodan:
>
> Thanks for your help!
>
> OK, first , what I want to do is to port a driver from desktop
> WinXP to XP Embedded. But I don't know well
>
> about the XP Embedded. So I'd like to build a XP Embedded image for
> practicing purpose. Then I start the MS Target
>
> Designer and choose a Template from the Design Templates, and then
> check the dependencies and then build the target
>
> image. and the result is a directory. I guess the following work I
> have to do is to pack the directory to a sdi file
>
> and then deploy it on the remote machine. That's what I want to do!
>
> But then I fail to reboot the remote machine. I do a check
> according KM's suggestion and find that the SDI file
>
> is empty. I pack the image directory again according the following
> instruction
>
> http://msdn.microsoft.com/library/de...l=/library/en-
> us/dnxpesp1/html/ram_sdi.asp
>
> but it fails in the second step,
>
> D:\Program Files\Windows Embedded\utilities>sdimgr "D:\Program
> Files\Windows Emb
>
> edded\Remote Boot Service\Downloads\image.sdi" /readpart:f:
>
> Microsoft (R) Windows Script Host Version 5.6
>
> Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
>
> SDI File Manager version 1.00.621
>
> Copyright (C) 1999-2001 Microsoft Corp. All Rights Reserved.
>
> D:\Program Files\Windows Embedded\utilities\SDIMgr.wsf(2294, 4)
> SDIAUT.SDIFile.1
>
> : The process cannot access the file because it is being used by
> another process
>
> But I don't find any other program is using the sdimgr.wsf.Do you
> have such experipence
>
> or would you like to give me some suggestions, This is the first time
> for me to touch the XP Embedded.
>
> Thanks a lot!
>
> BR,
>
> Steven
>
> 11/1/2004 9:34:46 AM
>
> "Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
>
> <#6eSFL7vEHA.1988@TK2MSFTNGP12.phx.gbl>
>
>
>

> > Hi Steven,

>

> >

>

> > > I've built a sample Embedded WinXP and want to deploy it on a

> target
>

> > > pc machine. And I've cofigured the Remote Boot Manager as

> follows:
>

> >

>

> > Can you give us more info about what you want to do, and exact

> steps that you done so far?
>

> > Have you created post FBA image on your target and then captured

> SDI file? In not then you can't make remote boot.
>

> >

>

> > It look to me that you need a way to copy pre FBA files to your

> target device? If so then use first bootable XPe CD with WinPE.
>

> >

>

> > Regards,

>

> > Slobodan

>

> > PS: Have you seen progress bar (you should be able to see it for

> some time)
>

> >

>

> >

>

> > "Steven" <hlsun@winbond.com.tw> wrote in message news:%23p5u8C7vEHA.

> 1976@TK2MSFTNGP09.phx.gbl...
>

> > > Hello KM:

>

> > >

>

> > > The sdi file size is about 256M and the actual size of the

> image
>

> > > is about 113M.

>

> > >

>

> > > Here is the result of running the command:

>

> > >

>

> > > D:\Program Files\Windows Embedded\utilities>sdimgr

> "D:\Program
>

> > > Files\Windows Emb

>

> > >

>

> > > edded\Remote Boot Service\downloads\test1.sdi"

>

> > >

>

> > > Microsoft (R) Windows Script Host Version 5.6

>

> > >

>

> > > Copyright (C) Microsoft Corporation 1996-2001. All rights

> reserved.
>

> > >

>

> > > SDI File Manager version 1.00.621

>

> > >

>

> > > Copyright (C) 1999-2001 Microsoft Corp. All Rights Reserved.

>

> > >

>

> > > SDI File : D:\Program Files\Windows Embedded\Remote

> Boot
>

> > > Service\Down

>

> > >

>

> > > loads\test1.sdi

>

> > >

>

> > > MDB Type : ---

>

> > >

>

> > > Boot Code Offset : 0x00000000.00000000

>

> > >

>

> > > Boot Code Size : 0x00000000.00000000

>

> > >

>

> > > Vendor ID : 0x0000 (0)

>

> > >

>

> > > Device ID : 0x0000 (0)

>

> > >

>

> > > Device Model : {00000000-0000-0000-0000-000000000000}

>

> > >

>

> > > Device Role : 0

>

> > >

>

> > > Runtime GUID : {00000000-0000-0000-0000-000000000000}

>

> > >

>

> > > Runtime OEM Rev : 0

>

> > >

>

> > > Page Alignment : 1 (4096 bytes)

>

> > >

>

> > > Type Offset Size Base Address

> Attr
>

> > >

>

> > > ---- ------------------- ------------------- ------------------- -

> ----
>

> > > -----

>

> > >

>

> > > DISK 0x00000000.00001000 0x00000000.10000000 0x00000000.00000000

>

> > > 0x00000000

>

> > >

>

> > > It looks like the sdi file is wrong, isn't it?Thanks a lot!

>

> > >

>

> > > BR,

>

> > >

>

> > > steven

>

> > >

>

> > > 10/30/2004 2:05:12 AM

>

> > >

>

> > > KM <konstmor@nospam_yahoo.com> wrote in message

>

> > >

>

> > > <#PD26FevEHA.612@TK2MSFTNGP15.phx.gbl>

>

> > >

>

> > >

>

> > >

>

> > > > Steven,

>

> > >

>

> > > >

>

> > >

>

> > > > I haven't seen such behavior with RBS.

>

> > >

>

> > > > Usually you see the progress bar showing the download of SDI

> file.
>

> > >

>

> > > >

>

> > >

>

> > > > How big is the test1.sdi?

>

> > >

>

> > > >

>

> > >

>

> > > > Could you run "SDIMgr test1.sdi" command and show us the

> output?
>

> > >

>

> > > >

>

> > >

>

> > > > Switch to startrom.n12 boot program. At least you won't need to

>

> > > press F12.

>

> > >

>

> > > >

>

> > >

>

> > > > Use Netmon or EtheReal network monitoring app to see the

> traffic
>

> > > between your target PC and the server. You will be interested in

>

> > >

>

> > > > the part after the dhcp handshake.

>

> > >

>

> > > >

>

> > >

>

> > >

>

> > >

>

> > > > --

>

> > >

>

> > > > Regards,

>

> > >

>

> > > > KM, BSquare Corp.

>

> > >

>

> > > >

>

> > >

>

> > > >

>

> > >

>

> > > > > I've built a sample Embedded WinXP and want to deploy it on a

>

> > > target

>

> > >

>

> > > > > pc machine. And I've cofigured the Remote Boot Manager as

>

> > > follows:

>

> > >

>

> > > > >

>

> > >

>

> > > > > Client Mac Address: XXXXXXXXXX

>

> > >

>

> > > > >

>

> > >

>

> > > > > Action: boot

>

> > >

>

> > > > >

>

> > >

>

> > > > > Boot Server: 192.168.1.100(the develop machine)

>

> > >

>

> > > > >

>

> > >

>

> > > > > Boot Program : startrom.com

>

> > >

>

> > > > >

>

> > >

>

> > > > > Boot Image: test1.sdi (This file is stored in the

>

> > >

>

> > > > >

>

> > >

>

> > > > > "D:\Program Files\Windows Embedded\Remote Boot

>

> > > Service\Downloads")

>

> > >

>

> > > > >

>

> > >

>

> > > > > The boot parameters is empty.

>

> > >

>

> > > > >

>

> > >

>

> > > > > The check option "Use DHCP port(67)" has been checked.

> For
>

> > > the

>

> > >

>

> > > > > DHCP server is another machine.

>

> > >

>

> > > > >

>

> > >

>

> > > > > Now, I reboot the target pc, and then PXE appears: Intel

> UNDI
>

> > > PXE-

>

> > >

>

> > > > > 1.0 ,and then it got the IP address,and a message box

> "Press
>

> > > F12

>

> > >

>

> > > > > for network service boot" appear on the target PC, and then a

>

> > > dark

>

> > >

>

> > > > > screen for several seconds, and then the target pc reboot.

>

> > >

>

> > > > >

>

> > >

>

> > > > > I am not sure what's wrong? The configuration for Remote

> boot
>

> > >

>

> > > > > manager is wrong or the SDI file is not correct? Anyone can

> help
>

> > > me?

>

> > >

>

> > > > > Thanks!

>

> > >

>

> > > > > --

>

> > >

>

> > > > > Composed with Newz Crawler 1.7 http://www.newzcrawler.com/

>

> > > --

>

> > > Composed with Newz Crawler 1.7 http://www.newzcrawler.com/

> --
> Composed with Newz Crawler 1.7 http://www.newzcrawler.com/