Jump to content

mats

Member
  • Posts

    202
  • Joined

  • Last visited

  • Donations

    $0.00 

Everything posted by mats

  1. If you can build an image from server 2003 with pe2005 and then try my version. It's still in our labs but it is working on about ten diffrent systems so far
  2. are you running the two nics in the same machine? If you are, try dissabeling the nforce nic
  3. THe nforce nics has been a little tricky but the 905 should be easy. I'll se if i can find a Dell during the day and test it.
  4. take a look at my posts in http://www.msfn.org/board/index.php?showtopic=53366
  5. To add another question. What nic do you got and on wich motherboard? Chances are that someone here got it working
  6. We left ghost about 3 years ago but can't ghost explorer modify ghost images?
  7. MS Gold and Certified partners also have PE access from about jun
  8. you will have to contact ms to get that patch unless you have a premier agrement. If you do you can download it on the premier webb
  9. Chris I agree on the os point. Then it comes to security I don't. If you can get physical access to a system you own it since you can do the same with any linux cd or ntfsdos. This will probly fix itself then winfs becomes standard but until then efs is the easy way to keep data secure
  10. Actually WinPE nowdays should be availible as a product so I would say call your nearest MS office and ask them. Earlier you had three ways to get it, Be an OEM, have a valid SA agremment or hire MS consulting to do something that includes PE
  11. Yes there is PE2005 builds of XP64 according to the docs
  12. IF sysinternals makes a verion built on pe2005 it should be poosible to run it from RIS. Information on howto setup PE to boot from RIS/RAM can be found in the winpe.chm file located in the docs directory
  13. The file is SERVERSP1-REMOVELIST.TXT wich is located in the samples directory.
  14. Delete winnt.sif. Setupldr will look for winnt.sif (or any sif i think) and if it doesn't find it it will look for a minint folder and boot from that instead
  15. Nope it wan't save it but if you place your diskpart commands in a script and run the script at each boot you will get the same effect
  16. Yes you can I posted this in the tread boot pe form HD earlier 1. Grab a copy of mkbt and nt2peldr from bart 2. make a working ramdisk booting pe iso, place it in c:\ with the name test1.iso 3. copy setupldr.bin from a server2003sp1 disc to c:\peldr 4. run mkbt -c -x c: c:\peboot.bin 5. run nt2peldr c:\peboot.bin 6. Edit boot.ini and add a line c:\peboot.bin="PE From ram" 7. Create a winnt.sif file with the following in it [setupData] BootDevice = "ramdisk(0)" BootPath = "\i386\System32\" OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=test1.iso" Architecture = "i386" Reboot the system and enjoy If you don't want to boot from a ramdisk image simply create the minint folder and place the contents of your pebuild/i386 folder in minint
  17. Yes you can do this with the built in diskpart command. take a look at how you script diskpart and it should do the trick
  18. Ofcource It is on page three in this thread but here it is again http://www.microsoft.com/downloads/details...&displaylang=en. You will need to download and extract this kit to for example C:\WSSRA. Inside there is a file WSSRA_Deployment_Toolkit.msi. Run this and install to C:\WSSRA. After that you will have a C:\WSSRA\Deployment Kit\MSAAPFTree\WinPESupport folder and in that you have ramdrv.sys
  19. Probobly because this isn't a "real" driver but a software mess that replaces a true nic in hardware
  20. I took a look at the driver int the WSSRA deployment kit and that driver is ok. However the included inf files shouldn't be used. They are way to old to work with pe2005. They also made a type in the WinPESys.inf file. To get it working: 1. copy the ramdrive file from the WSSRA kit to \system32\drivers 2. run reg exe load HKLM\PETEMP \system32\setupreg.hiv 3. run the attached ramdrv.reg 4. run reg exe unload HKLM\PETEMP 5. make a new iso with oscdimg 6. boot it and you should hav a ramdrive at r: ramdrv.reg
  21. I' ll quete myself again According to MS you need to install recovery console to boot PE from boot.ini I do present a better solution in the rows below. If you need to boot a larger pe than 256MB you have a very bad design. Fix that first. A Pe image cabable of handeling about a hundred diffrent hw plattforms, loading images, resizing disks and loading firmware can be assambled in less than 200 mb. Every unnedded mb takes time to load and if you got 20K plus workstations, that counts You dont need to include images or installation folders on the iso. You call theese from pe using variables. That saves time and space but requires some coding skills
  22. You say intel board Not by any chance a PIII? They had serious issues with theri nic:s and auto speeds. Firmware helps in some cases. hard locked nic speeds helps in some cases. The best way to fix it? Build your image from server2003sp1 media and use the ramboot feature
  23. I'll quote myself According to MS you need to install recovery console to boot PE from boot.ini Well, there is another way of doing this. i prefer the new ramboot style so that will be used in this example. The iso filename should be max 8.3 according to noodles so i used test1.iso. Ofcourse you can name it whatever you like. 1. Grab a copy of mkbt and nt2peldr from bart 2. make a working ramdisk booting pe iso, place it in c:\ with the name test1.iso 3. copy setupldr.bin from a server2003sp1 disc to c:\peldr 4. run mkbt -c -x c: c:\peboot.bin 5. run nt2peldr c:\peboot.bin 6. Edit boot.ini and add a line c:\peboot.bin="PE From ram" 7. Create a winnt.sif file with the following in it [setupData] BootDevice = "ramdisk(0)" BootPath = "\i386\System32\" OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=test1.iso" Architecture = "i386" A little Easier i think, Or just simply use virtual pc
  24. Hi Krusty I dont know with ghost since we use pqideploy instead but i think you must take a new ghost of your sorce machine and take the whole disk. I found this on the net on how to restore an entire disk ghost.exe -clone,mode=load,src=Z:\E-Client\20008\images\G-Img.gho,dst=1 -sure
  25. ah that could be it. Have you tried to clone the entire disk instead of a partition? You should clone the entire disk to get the bootsector and mbr correct. I Checked with my people and we got E620 working in our enviroment without problems


×
×
  • Create New...