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. ×

daremo

Member
  • Content Count

    25
  • Joined

  • Last visited

  • Donations

    $0.00 

Community Reputation

0 Neutral

About daremo

Profile Information

  • OS
    Windows 7 x64
  1. I think you can start by investigating the bcd store on the AIO DVD, and locate the entry that points to the dART environment. It most probably is a wim file (either boot.wim, or another small wim or winre file). Say it is boot.wim. Use dism to enumerate the images included in the boot.wim file, and check the descriptions, and one of them should be the dart image. you can then use dism to mount the image using its index, and make a standalone copy or place it on USB, or add it to your own boot.wim. Without having a copy of the AIO iso (i found a few of them on the torrentz, which specify dart
  2. your problem is changing the active partition. When booting, bootloader needs to know on which partition the bcd store exists. You had initially set up a partition as active and created a BCD store, then you later change your active partition, and the system is unable to find the bcd store to load a system. If you are using a dedicated partition for BCD store (the reserved, "system" partition), then keep that partition as the active one at all times! You can always use a win7 dvd to boot into winpe, in case you have problems boting up the system. You cana lso use bcdedit to edit the existing b
  3. JFX is right. While capturing an image with imagex, you must have captured the existing boot folder and bcd store data. As a default, imagex can skip certain files, but you can use the "/Config <drive:\folder\myconfig.ini" option to direct imagex to use your custom config file which should specify which folders and files to skip during capture operation. Since you have a single drive - single partition, your boot files (BCD store) are on the same partition, instead of the system reserved partition. Because default imagex configuration does not exclude \boot folder and files (as well as boot
  4. Or you can use imagex /apply and place the contents of install.wim onto c: drive. Place imagex and other necessary files and install.wim on D-drive, then use imagex /apply to extract and write the contents of install.wim onto C-drive. Then, you can use BCDBOOT command- Bcdboot.exe <source> [/l <locale> ] [/s <volume-letter> ] [/v] <source> is windows source folder /l <locale> is locale (such as en-us) /s <volume-letter> is the target drive /v is verbose mode So you should issue- bcdboot C:\windows\ /l en-us /s C: /v
  5. For some type of drivers such as new network drivers (but not the sata drivers), it is possible to update the bartpe without going through the full rebuild option. You need to check out the minint folder and subfolders and see where the dll, inf, cat, and sys files are located, then for the new drivers, you should copy the relevant files to the respective subfolders. I have done that for additional or new network drivers, by extracting the bartpe iso to my hd, and copying the inf, dll, sys, cat files to the subfolders of minint, and making a new iso. However, with sata drivers or drivers that
  6. I had a similar problem with a HP laptop booting BartPE and WINPE1 from USB stick several years ago, and the main reason was that while the system was loading (windows is loading files), the USB bus would be reset, and the connection to the USB stick would interrupted leaving me with a black screen or the WINPE logo and no activity whatsoever (I could see the USB stick stop flashing). I could only boot the laptop with the built-in cdrom drive, and using bartpe and winpe1 burned on CDRs. Eventually, I had to reorganize the internal HD after managing to boot the system with a winpe CDR, and conf
  7. I don't know, but logically thinking I expect the security settings to be reset, since part of sysprep is creation of new SIDs... therefore something must be going on regarding file security and the new security principals, right? File comparison: there are many file comparison utlities both free and commecial that use different comparison methods (incl. full binary comparison, md5 or other file hash comprison, same name, same size, etc.). I have mostly used NoClone, and it can compare thousands of files wherever they recide. It will list identical files (duplicates) with their full paths. If
  8. I am not sure I understand what you are trying to figure out, as the above explanation is not clear enough for me, but based on what litle I gleaned from the above post and others, I can point out the following which may or may not help you in the right direction... 1. Since you are using virtualization, you can always mount the Virtual Disk (VD), and look at the contents of a bcd store in detail; before and after a sysprep. So you have a means of comparison you can use to determine what changes (and possibly where those changes may come from). 2. You can also extract the boot.wim or install.w
  9. A question regarding your situation... Do you have both drives installed on the same computer at the same time, when you are creating and then deploying the wim file (such as HD1 and HD2)? If so, then I doubt the problem is only a matter of fixing BCd store (via repair or manual editing). There is also the issue of HD order in the BIOS, and in the Win registry (mounted drives, etc) that might come into play, besides the hardware related information being used to set up Windows Activation data. How about the following scenario: 1. HD 1 (500 GB) (first HD in the BIOS) 2. HD2 (320 GB) (second HD
  10. ADDENDUM I encountered a slight problem when native booting a winpe differencing VHD file (i.e. a standard or customized boot.wim file applied to a VHD file). I was trying to set up the following situation: 1. Internal HD partitioned C (Active, primary) to be used for bootmgr and bcdstore (and grub), D (logical drive on extended partition) to be used to store VHD files, E (logical drive on extended partition) to be used to store differencing VHD files. 2. bootwim.vhd (fixed vhd with 5gb cap, single partition, primary) located on D drive. Obtained by applying boot.wim file on to bootwim.vhd 3.
  11. I'm not sure how to take this statement. If you have an attached VHD, and apply a wim file, and you're not happy with the result, you can always do a quick format of the VHD, modify your wim, and reapply. If this is a situation where you already had data in the VHD and are applying a wim and not happy with the results, the only UNDO option you have is making use of a differencing VHD: 1. Keep your original data in the parent VHD (parent vhd), 2. create a differencing VHD (child vhd), 3. apply wim on the differencing vhd 4. test results... If not happy, remove the differencing disk, recreate
  12. Problem is I don't have office 2007 to do tests, as I use Office 2003, so it's difficult to find out what is going on, forcing me to guess. Now, with the comment from Ponch, which is opposite of what Novie is saying, I'm wondering if Novice has a named/defined the range K10:M10 somewhere on the worksheet? I suspect Ponch tested this out on a clean worksheet, and that forces me suspect that Novice has a named range or something similar defined for K10:M10 on his worksheet. Perhaps selecting the first cell of a "named range" is forcing the formula to h-light/select the full named range???
  13. I am pretty sure the original post mentioned that after a wim file is applied to a drive, the user has also run repair operation which usually scans and fixes the BCD store issues. So, yes, editing BCD store manualllyor running repair (or booting with original win 7 DVD and choosing repair int he install screen) should fix the problem, but it user complains about blue screen + Non Genuine Windows message. Sooo... what is exactly going on and after doing the following: 1. create wim 2. deploy wim to another drive how can you get the system working from the new drive without issues (and solve th
  14. Thank you, Jaclaz, for the corrections and clarifications over MBR/PBR. It is unfortunate that so many companies are using terminology in an ambiguous manner (even using words interchangably and wrongly), or use technical descriptions that are imprecise. I have come across a good web-site on the subject of multi-boot and multi-boot process that deal with Windows and other boot managers and the details of booting (theoretical/practical) and HD boot sector/MBR, etc. which I hope would be of some use to us to get a better understanding, especially, in the light of your corrections: Boot and Mul
  15. I am not sure how to turn off the help from Excel, but your problem regarding automatic selection of a range of cells reminded me what might be at play. However this is based on Excel 2003, so may not be applicable in your case. When you are starting a formula but especially when you use the SUM function (via the toolbar icon), Excel seems to select a range of cells in a column that are "contiguous". If, for example, in a column you have a range a1 to a5 [A1:A5] and another range from a7 to a10 [A7:A10], and you are inputting a formula or SUM at A11, then Excel hi-lights the range [A7-A10] ins
×
×
  • Create New...