Ghost Console 184.108.40.2063 and WinPE
I have 2 questions.
1. How do I define a clone task in Ghost Console ver 220.127.116.113 that will successfully execute on a "client" pc that is booted via PXE to a WinPE environment?
A little information about the setup. Ghost Console is standard type setup. Client boots to WinPE via PXE from the said console. WinPE is a WIM built with Ghost Solution Suite 2.5 GBW. I have modified the WIM with client files from older console. I remmed out the statement "ghost32.exe /setosdrives /blind >> x:\ghost\startlog.txt" as the older version of ghost32 does not seem to know what to do with the switches. I tried to let the start.bat command "start ngctw32.exe -console" do its magic but it would show up as a process for a few seconds and then disappear. I have ran ngctw32.exe -install as that appears to be the only way to get the client to stay active. This allows for communications between the client and console.
I start a task and the client starts to reply like it should, updates the x:\ghost directory with ghost.exe etc.. It then gets the command from the console to start ghost and connect to the right session but ghost can not start. the ngctw32.log file shows that it gets the command but that there is no response. I do a dir on the ghost directory and the ghost.exe is there. I attempt to execute ghost.exe from the command line and it returns that there is no ghost.exe.. I delete ghost.exe from directory and copy the ghost32.exe to ghost.exe and ghost can launch but still ngctw32 can not start it. Is there someway to define a task that will acknowledge that the client is in a 32 bit PE environment and not in DOS? I imagine if I could do that with the cloning part, I would have to do the same with the config part as well.
2. This question has to do with the above setup. I am using the GBW from the Demo of GSS2.5 to build the above WinPE WIM. Is this compatible and allowed under the Demo aggreement? I don't want to do anything that would not be considered appropriate use so I will stop this if you say so and use some other WinPE development tools if I have to. Regardless, Can I use WinPE as a "virtual boot partition" to boot bare metal machines, connect to a console and have clone tasks successfully run on them from a ver. 18.104.22.1683 console.