Jump to content

thesimpsons

Member
  • Posts

    26
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About thesimpsons

thesimpsons's Achievements

0

Reputation

  1. It is slow when the system gets the image from the ghost server. Ghost indicates the speed of getting the image on the screen. It tells you how fast the data transfer from ghost server to the system you want to image. On the different controller, the speed was fast as I expected (1600MB/min or above). But on this particular Serial Attached SCSI the speed was very slow (300Mb/min) considering the new Serial Attached SCSI suppose to be faster than regular SCSI (called parallel SCSI.) Do you think it is becasue ghost doesn't support this new type of controller or it is becasue BartPE with the driver problem on the controller? Thanks.
  2. Anyone has any ideas why ghost is very slow on the Serial Attached SCSI drives when booting up from BartPE and connected to ghost server over gigabit network? This is not multicast. The speed was 300MB/min or less while the speed on parallel SCSI was above 1600MB/min. Thanks.
  3. Hi Everyone, I have new Dell Precision Workstation 490. I tried to re-image from ghost server using BartPE as a boot disk but the speed was very slow when trying to get image from ghost server. It was about 200MB/min. This is way too slow compare to others Dell that I have. The average speed for other Dells is about 1500MB/min on the gigabit network. I figured this is becasue of the SCSI controller on the Dell 490. So, I took another SCSI controller along with the hard drive and put them to the Dell 490, the speed when downloading the image was great again. I don't know if this new SCSI controller is supported by bartPE and Ghost 8.3. Here is the information on the SCSI controller: http://support.dell.com/support/downloads/...69&libid=46 It is called Dell SAS 5/iR Adapter. It uses the new hard drive that looks similar to seriral ATA. It is something like Serial SCSI. The interface looks exactly like the serial ATA. One more thing, is the PXE boot on BartPE with Windows 2003 RIS faster than the BartPE boot CD? Any ideas? Thanks.
  4. Hi Indy, Can you show me how you work on BartPE boots with PXE and Windows 2003 RIS? I really to see how this thing works. Thanks.
  5. Well, I tried to ghost Vista beta2 and it worked fine when adding switch. But, it failed again when i tried Vista new build (5472, CTP released a few days ago.) I mean I did the same steps, but it failed just like before adding the switch. I don't know why. Do you guys have any ideas about this? About the recomendation from fizban2, i had a hard time trying to figure out which one I should download to run the imageX and others. I downloaded BDD and WAIK but found nothing that could help me to run imageX and others. Please advise. Thanks.
  6. Ghost80 will work with Vista. I have to add the switch -fdsp when doing the re-ghosting. Without the switch, the error will come up when the system starts.
  7. Thank you very much. I will try that and let you know the result. Was you be able to do it with Imagex?
  8. Can you be a bit more specific about this? Wher can I download this program and is there any article about this? Thanks.
  9. Hi Everyone, I am wondering if any of you out there have been trying to ghost Windows Vista? I have 12 Dell Precision and would like to install Windows Vista on all of these machines. One of the method I have tried was to install Windows Vista Beta2 on one machine then ghost this machine to the file server. The ghost process went fine without any problem. However, another dell 380 machine with the same hardware configuration would not run Vista after the ghost process is done (run ghost from image.) It keeps saying that the system is misssing winload.exe file. I mean, I have done quite a lot with ghost for other operation systems but never have any problem like this. Do you guys experience some proplems like this with Windows Vista? Thanks.
  10. It WORKS!!! Thanks a lot, guys. peshuteject.exe /eject:x /reboot works GREAT. Thanks again.
  11. Here is the bat file: z:\ghost32.exe -fx -sure z:\eject.exe z:\shutdown.exe -r -f Where Z is the mapped drive. As I looked into the directory I saw that X:\i386\system32 I noticed that shutdown.exe is in here. However, X drive is the CD drive, if the system eject the CD drive then the shutdown.exe won't execute. Even when I copied shutdown.exe to RAM drive which is B in this case, shutdown.exe still could not execute. I tried peshuteject.exe, the same result. System ejected CD but won't reboot. Any ideas? Thanks.
  12. I tried your method but it doesn't work.
  13. Do I have to put those into PEbuilder as a plugin or just put the execute file in the mapped drive and the command in the bat file? Thanks. using peshuteject.exe can only eject CD but not reboot the system. Is /shut is the right switch?
  14. The first two commands you recomended works fine. After finished getting image, ghost exited, system ejected CD but would not reboot. The problem here is that the bat file contains these commands is on the mapped drive, when CD is ejected it would not execute shutdown command. Is there any way we put this shutdown command somewhere else to make it execute? Is it posible to put in in RAM disk?
  15. Now, this bat file is located on the mapped drive on the network, right? I can put eject.exe on the same mapped drive and issues run it from the bat file. But what about shutdown -r -f ? Is it on the same mapped drive or it has to be build in with PEBuilder? This shutdown.exe can be found in C:\Windows\System32, right? The question is whether shutdown.exe can be execute after the CD is ejected if shutdown.exe is on the same mapped drive? i will try this method tomorrow and will let you know the result.
×
×
  • Create New...