Jump to content

RUSerious

Member
  • Posts

    69
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About RUSerious

Contact Methods

  • Website URL
    http://

Profile Information

  • OS
    Windows 10 x64

Recent Profile Visitors

1,745 profile views

RUSerious's Achievements

2

Reputation

  1. Many thanks for your extensive replies jaclaz. I’ve been using some ‘older’ HP laptops for the past several years now. These have suspect USB drivers and were likely some of the earliest BIOS versions to offer UEFI options / support. So I think you nailed down the cause of this issue and what led me to believe that IF controller’s "flippable" bit was set to "removable", THEN it could not be bootable. I did try several variations with BOOTICE to see if any combination might work with my HP laptop / "removable" stick combo, but nothing worked. BOOTICE does however confirm that the sticks not bootable for me are set as "removable", and that those sticks that are bootable are set as “fixed”… in that BOOTICE designates "removable" setting with an RM# and the flip with an HD#. And BOOTICE seems to treat both the same with respect to options available. Thanks again for correcting me on this.
  2. This is with respect to the USB stick controller with a "flippable" bit that can tell OS whether the device is "removable" or "fixed". And with my difficulty in getting removable HDD sticks to be seen as BIOS bootable. Maybe some related setup restriction that is tripping me up? Thanks
  3. Big thanks for your reply, correction, and link to more relevant thread. Using the same setup used for many other USB sticks with no problems. BIOS MBR win10 64bit. Booting an OS within a VHDX on a USB stick seems to be a very good stress test for a USB stick. Most cheap sticks don’t make it through the first boot attempt. I’m guessing a desire to use lower quality chips without any heat ‘ speed adaptations. Some sticks will also hang the boot process. Had one SanDisk Extreme stick where SanDisk went back and forth (fixed or not) on the exact same model. I came to the conclusion at the time -- from info I could find -- that a stick ’HDD’ was not bootable because it was not seen as fixed. I must be missing some other issue tied to this. Thanks again for the reply / correction / direction. edit: https://msfn.org/board/topic/184310-any-relation-between-a-usb-stick-being-bootable-or-not-and-fixed-or-not-‘-removable/
  4. Via win10, I’ve got all the BCD files in place on a stick for it to be bootable. And WinNTSetup 5.2.6 gives stick 3 green lights as a Boot drive; But I know from previous boot attempts that this stick is not BIOS bootable -- will not be seen during boot process. Is there any way for WinNTSetup, or any windows app, to see this BIOS bootable bit within a stick’s ‘firmware’? Thanks for the awesome app!!
  5. THANKS for the insights on Windows 10 builds. I'm trying some different things. I thought it might have been one of the optional updates >> drivers, that were offered (that I installed) that caused the issue. There is a Realtec driver in there that I will definitely not install again (major PITA from Realtec drivers on other hardware in the past). Very valuable to know of issues others have had with anything 1904x. THANKS Surprised that the update process varies so much between builds.
  6. Seeking feedback on which Win 10 Version ' Update is the most stable. Was using, and now back to 16299-1709 in VHDX / MBR -- which was very solid. Recently tried 19043.1110 VHDX / GPT which is very unstable on same hardware -- frequent BSOD ' lockups. Using the awesome WinNTSetup as installer. With default Windows drivers. Feel free to recommend an app for updating drivers from what Windows uses. Thanks
  7. 10 v2004 ... I use this awesome app to install to VHDs. When I selected 10 v2004 in windows update, it failed stating something about would not install into a VHD. Does anyone know if 10 v2004 can be built and installed into a VHD? IOW, did this fail only because it was an update via windows update? Thanks
  8. Anyone figure out how to do a feature / build / version update (1703 to 1709) within a VHDX file? Normal updates (Win+X > Update & security) work fine, but MS will not allow version updates on a USB or VHD / VHDX drive. Tried obvious of mounting / attaching the VHDX, then cloning it to an internal partition, and then editing BCD to boot to the clone. Acts likes it going to boot to the VHDX clone (on the internal HDD partition), but just ends up with the eternal gray screen. Familiar with BOOTICE if that helps...TIA
  9. The first couple posts of this thread are a bit confusing as to what is the best tool or combination of tools. Would be nice to edit those to clarify what is now known to be the best method... Thanks
  10. That was my first thought, since the retail shelf does get pretty outdated. But still, never would have expected the USB 3.0 drivers on top of the line laptops to be that bad -- right out of the box. Thanks
  11. Wanted to see what the actual top speed of an mSATA SSD in an mSATA USB 3.0 enclosure might be, so went to a retail store with several top of the line laptops. Tried 5 of the highest priced laptops they had and was surprised that only one was over 400 MB /s. Even more surprised that 3 where barely over 100 MB / s. And yes, the SSD was plugged into ports that were clearly marked with the 'SS' for USB 3.0. Was using Crystal Disk Mark on one partition of the SSD to run tests on another partition of the SSD. Any ideas for why these top dollar laptops had such poor USB 3.0 performance? Guess it pays to test before you buy.
  12. Good to know, Thanks jaclaz BTW, found an easy way to get an XP VHD. Use these instructions to get the VHD from MS: http://www.picohelp.com/1264/how-to-run-windows-xp-in-windows-8-with-virtualbox-6-simple-steps.html If your not on Windows 7, and can’t extract from the WindowsXPMode_en-us.exe file, then run that exe file and make a copy of the extraction folder (it creates) before clicking OK on the Windows 7 ONLY message (which deletes the extraction folder). Then use the tips in link above to get to the actual XP VHD. Then use a VM app as in link above to run the VHD.
  13. YES, THANK YOU. Did this: Bootice >> BCD Edit >> Set Default (made no difference). Then did this: Bootice (Physical Disk tab, system / boot partition chosen) >> Process PBR >> BOOTMGR (NTLDR was already selected, changed to BOOTMGR) >> Install / Config And that did it .!! Did not change / Process MBR since Windows NT 5.x / 6.x MBR was already selected. Bootice (Physical Disk tab, system / boot partition chosen) >> Process MBR >> Windows NT 5.x / 6.x MBR
  14. Desperate for help. Tried to install Windows XP to use a good laser printer (no good drivers after XP). Tried to use WinNTSetup v3.8.6 to make a XP VHD – no go. So then tried to use WinNTSetup v3.8.6 to install Windows XP to a 4 GB partition. Used my system / boot partition (with BCD files) as the boot drive. All seemed to go well until reboot and XP install said it could not find all the install files needed. Now stuck with a system that will only boot to a blue install error screen. Have EasyBCD and BOOTICE and tried to remove any reference to WindowsXP in any BCD files I could find on any partition – but system still wants to boot to the Windows XP install error screen. Now booting to system from a portable drive – that if I remove, system freezes. Don’t want to mess it up any worse. So could someone PLEASE tell me how to remove whatever it is that will not allow my normal BCD options to load at boot. MANY Thanks
  15. Yes, I used WinNTSetup to install 8.1 to a VHD (don't remember all the details (relearn when I do 10)). I keep a VHDa to use / update, and a VHDb to boot to for when I want to back up VHDa (both on my HDD). One issue is that VHDa keeps growing in size -- by GBs. I don't know the cause of these huge increases as recovery images have been disabled. And hard to imagine that normal MS updates are adding this data. Will hopefully figure this out when I do 10.
×
×
  • Create New...