Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×


  • Posts

  • Joined

  • Last visited

  • Donations


About mjphelan

  • Birthday 10/28/1970

Contact Methods

  • Website URL

mjphelan's Achievements



  1. ilko_t: Yes, the lst file was replaced, this was because the existing one did not work with the version of UBCD4WIN I had avaliable (Latest downlaod from the UBCD4WIN site) jaclaz: I'm using hte version supplied with the current download of WinSetupFromUSB and I was following hte instricitons within the origional thread. OS is Windows 7 64 bit, Key is 16 gig Sandisk U3 Cruiser Micro. I made the assumption that Win7 x64 was the cause. not realy an issue for me since I can work around using the older HP Tool for now.
  2. For this key (and the others I have) the HP Tool is the only way to format the key with NTFS, the RMPREPUSB failes with error code 6 or error code 1. The changes as advised worked fine. now for some in deapth reading on this Grum doohicky ;o) Many thanks for the assistance
  3. Ok bit confused, I made a couple of request for help posts, that got deleted... with no explanation as to why. Have I offended someone by asking for help? edit: doh, that will teach me to wahct the whole forum, not just one thread ;o) Posts got split out.
  4. On a hunch, I changed map --mem (hd0,0)//Images/goback.ima (fd0) to map --mem (hd0,0)/Images/goback.ima (fd0) Now I'm recieving the folowing Output Booting GOBACK Removal Tool Filesystem type is ntfs, Partition type 0x07 FAT12 BPB found with 0cEb (jmp) leading the boot sector. probed C/H/S = 80/2/36, probed total sectors = 5760 chainloader (fd0)+1 Error 25: Disk read error The same change for Memtest86 reports the error Filesystem type is ntfs, Partition type 0x07 chainloader (hd32) Error 21: Selected disk does not exist *mumbles*
  5. Awome Project.. Began setup todayusing a 16 gig Sandisk U3 Cruiser Micro. The aim was to allow the installation of Server 2003, XP Pro 32 bit, adn wIndows 7 64 bit from the USB Drive, and provide some diagnostics tools to techs. Primary Windows source (the top box) Server 2003 R2 - Straight from CD 1 XP SP3 via BartPE (Using UBCD4WIN) - Prepared using Nlite Windows 7 64 bit - Prepared using Windows System Image manager PartedMagic Gotchas Discovered: I managed to get the "Unable to write MBR" issue, it had a two fold fix. 1) Make sure all the OS source files are on the local hard drive, for some reason if anything other than the ISO is on the network, the build fails in one way or another. Note: This could just be the network I am on, it's highly secured due to the nature of the business 2) As posted previously, use the 2.0.6 version of the HP USB Formatting tool. Note: I awarded myself a muppet star after searching for ages on 't interweb for this version, only to find the note 2 pages later on this thread that it's included. Labeling of the Boot Loader Entries For Ease of use by the various techs, I needed to change the entries on the Grub boot loader to more accurately reflect the various Operating system installations. Fix: simply edit the .lst entries accordingly. Windows Server 2003 setup - works as expected Windows 7 64 bit Setup - works as expected Gparted - works as expected UBCD4WIN Initially, on selecting any option I recieved a "file not found" for all the items on the UBCD4WIN sub menu. for example Booting GOBACK Removal tool map --mem (hd0,0)//images/goback.ima (fd0) Error 15: File not found Press any key to continue For DBAN I managed to fix this by copying the "menu.lst" from my UBCD source to the memory key as ubcd4win.lst however the error persists for all the other tools within UBCD4WIN. I have verified that all the files are present on the USB key (dban.bzi, freedos,.img, goback.ima, memtest.iso, ntfs4dos.img) and the entries as far as I can tell are correctly listed in ubcd4win.lst. title GOBACK Removal Tool map --mem (hd0,0)//Images/goback.ima (fd0) map --hook chainloader (fd0)+1 rootnoverify (fd0) Still researching the issue, but I thought I'd post the story so far just in case ;o)
  6. Just out of interest, do you also have the following section? <ImageInstall> <OSImage> <InstallTo> <DiskID>0</DiskID> <PartitionID>1</PartitionID> </InstallTo> <InstallToAvailablePartition>true</InstallToAvailablePartition> <WillShowUI>OnError</WillShowUI> </OSImage> </ImageInstall> I've removed the double extend and tried both with and without the above to no avail. Just in case there is somethign I'm missing, I've attached the full answer file (with sensitive data removed) In my case, I am intentionally not adding a product code as this will be dealt with later. tmpautounattend.xml
  7. Operating on the sometimes less is more principal, I cut the XML down to <DiskConfiguration> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Extend>true</Extend> <Order>1</Order> <Type>Primary</Type> </CreatePartition> </CreatePartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> <WillShowUI>OnError</WillShowUI> </DiskConfiguration> <ImageInstall> <OSImage> <InstallTo> <DiskID>0</DiskID> <PartitionID>1</PartitionID> </InstallTo> <InstallToAvailablePartition>true</InstallToAvailablePartition> <WillShowUI>OnError</WillShowUI> </OSImage> </ImageInstall> No Joy Added the bold bit below <DiskConfiguration> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Extend>true</Extend> <Order>1</Order> <Type>Primary</Type> </CreatePartition> </CreatePartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Extend>true</Extend> <Format>NTFS</Format> <Label>WIN</Label> <Letter>C</Letter> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> </ModifyPartitions> </Disk> <WillShowUI>OnError</WillShowUI> </DiskConfiguration> <ImageInstall> <OSImage> <InstallTo> <DiskID>0</DiskID> <PartitionID>1</PartitionID> [b] </InstallTo> <InstallToAvailablePartition>true</InstallToAvailablePartition>[/b] <WillShowUI>OnError</WillShowUI> </OSImage> </ImageInstall> No Joy I'm confused, this should work but isnt...
  8. I'm having exactly the same issue... The relavent part of my autounattend.xml is <DiskConfiguration> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Size>100</Size> <Extend>false</Extend> </CreatePartition> <CreatePartition wcm:action="add"> <Extend>true</Extend> <Order>2</Order> <Type>Primary</Type> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Format>NTFS</Format> <PartitionID>2</PartitionID> <TypeID></TypeID> <Order>2</Order> <Letter>C</Letter> <Label>Primary</Label> </ModifyPartition> <ModifyPartition wcm:action="add"> <Active>true</Active> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> </ModifyPartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> </DiskConfiguration> Install process is automated up untill the Partition selection screen, where it halts. If I simply select "Next" the installation proceeds in a fully automated manner

  • Create New...