• Content count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About click-click

  • Birthday

Profile Information

  • Country

Recent Profile Visitors

626 profile views
  1. I'm back in business now. I don't know what happened the last time when my MBR was overwritten. Maybe I unknowingly used the old version. This time the yellow ball stayed yellow. Sorry for the confusion BTW, what is the ini setting for /nobootsect ? WinNTSetup.log
  2. Sorry, old version from a disk that I restored. I will redo an install ans send the correct info.
  3. From the drop-down in the GUI (do not update boot code). Did not know there was an ini entry or cmdline parm for that. I must have missed the discussion about it. What is the ini entry supposed to be? I see BootSect=2 after I updated to the newer .ini WinNTSetup.log
  4. During WinNTSetup. It happens at the very end after the updating boot code message. The yellow ball then turns green. I can't find a log file. Is it supposed to be on the drive where the system is installed? If you have a binary compare app, I can send you the before and after versions of the MBR I'm not sure if the mbr exe uses the same amount of code for the MBR like Bootit Bare Metal.
  5. Just tried the new version. MBR0 is still being updated during setup and partially overwriting my 3rd party bootManager
  6. Oh, Sorry, I missed seeing the [WinNT6\TWEAKS] section. Did you add a new option in this update to not update the mbr? Yellow doesn't necessarily mean booting a system will fail as indicated in the information balloon.
  7. Hi JFX, XP install is not a problem, because I am still able to reactivate Bootit with the BBM USB Install ISO. On the other installs, the BBM USB install ISO cannot reactivate and requires you to do a new install because too much of the code in the MBR was overwritten. I would like to avoid restoring the MBR after using WinNTSetup and it would be nice if updating the MBR could be avoided when possible. I still don't understand why none of my reg tweak selections did not appear in the GUI. Was I just missing the RegTweaks= entry? Thanks..
  8. I have bee having some minor issues with WinNTSetup lately. My .ini file that I have been using for ages is now missing all the tweak check-marks that I had selected a while back. I'm wondering why WinNTSetup is not setting these selections. I created a new ini with ctrl+s and noticed the following entries that have been added which I do not have in my old ini file: RegTweaks= [WinNT6\READY] OEM=\sources\$OEM$ Reboot=0 BCD=1 BootSect=2 Win7USBBoot=0 AddOtherOS=0 I seemed to have missed any mention as to what these entries do. After adding them, my check-marks were back. Another problem I am having, is that my bootmanager (Bootit Bare Metal from Terabyte Unlimited), is overwritten when I do a new install with WinNTSetup. I believe BBM sits in the MBR on HD0. WinNTSetp shows the MBR as yellow, which should be ok, but the MBR gets overwritten anyway even though I specify not to update the boot code. Once this happens, my bootmanager is gone. Can you think of a way to avoid this? I'm not sure if this has something to do with the BIOS on my new laptop. On my old Thinkpad T500 I never had to reinstall the bootmanager. Sometimes I had to reactivate it when I reinstalled XP, but that was about it.
  9. Ooops .... deleted
  10. Now that was easy. Thanks - I has forgotten about that. I did complicate matters because I used option 2 instead of option 3 and the Win7PE ended up with a blus screen. After the fact, I found a note to myself: "Use option three in Make_PE3 for rebuild (_Make_PE3.cmd). Do not copy files from current windows7 since this will break IE8 if IE9 or greater is installed on the current Win7." I had a backup of my MakePE3 aetup, so I restored that and only added the usb3 drivers without copying any windows files from my current system (Option3) and I was back in business. After booting the flash on the new lappy, I could see the flash listed and had access to it.
  11. Rebuild with usb3 support. Thanks for the other links - appreciate it.
  12. Hi, I have a new laptop that only has USB3 ports and my MakePE3 doesn't recognize anything on those ports. I can boot, the MakePE iso from the flash drive. but after the system is up there is no flash drive listed. I need to add usb3 drivers to MakePe, but it's been so long since I built a new one, I'm not sure anymore how to add this driver. Before I start researching again, could someone that knows please give me some quick instructions on how to best acomplish this?
  13. This happened using the latest version of WinNTSetup ( On my W7 (Starter) system, I created a VHD via Disk Management. Initialized the disk and selected volume type 'New Simple volume'. I then mounted the volume and started WinNTSetup. Select location of Windows installation files: R:\Win10_1511_2_English_x86\install.wim Select location of the Boot drive: c: (Using current boot drive since VHD not allowed) Select location of the Installation drive: c:\W10_Home.vhd Edition: Windows 10 Home Once started, I got the standard message about changing the boot code. I selected BOOTICE in order to later see the boot info. Everything ran to near completion when I got the mentioned errors which most likely came from W7 since you don't use such a dialog . If I run the same configuration and select 'do not change boot code' I do not get any errors and can install and activate W10. I did notice that even though I selected 'do not change boot code', WinNTSetup shows a msg '"changing boot code" at the end of the setup stage.
  14. I just tried installing W10 to a vhd from an active system and towards the end, I see the following msg: The update operation may be unreliable since the volume could not be locked. Continue anyway? If I select yes, I get Write file failed! Access is denied. I'm not sure if I'm following the correct procedure for installing to a vhd. I've always used an empty partition up to now. Anyone know why I'm getting an error?
  15. Makes sense. All I ever added was the PosReady key to keep the updates coming. I never knew that the windowsembedded key served a similar purpose.