Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Tripredacus

Supervisor
  • Content Count

    12,180
  • Donations

    $50.00 
  • Joined

  • Last visited

  • Days Won

    8

Tripredacus last won the day on July 12

Tripredacus had the most liked content!

Community Reputation

482 Excellent

5 Followers

About Tripredacus

  • Rank
    K-Mart-ian Legend
  • Birthday September 29

Contact Methods

  • AIM
    atrbludgeon
  • Website URL
    http://tripredacus.net/

Profile Information

  • OS
    Windows 7 x64
  • Country

Flags

  • Country Flag

Recent Profile Visitors

19,618 profile views
  1. You say that you wake the computer. Are you waking the computer (is it in sleep?) or do you have your monitor set to sleep and not the computer? Are you using the option to lock the system with screen saver, setting a screen timeout or manually locking with Windows+L? If you are using the auto-lock option, does the same thing occur when you manually lock the OS? If that is the case, I would probably set up a ProcMon or PerfMon session, then lock the system, to help identify what processes are active at the time of the disk activity.
  2. Being able to check from within the OS itself is trivial. As in the op, the disks were not allowed to be booted. Now the documentation for DISM FFU does show what is and isn't allowed: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/deploy-windows-using-full-flash-update--ffu In typical fashion, we cannot be entirely certain if the line of "Captures of disks that have Volume Shadow Copy Service (VSS) enabled are not supported" means: - vss is enabled and a capture is present or - vss is enabled but a capture hasn't occurred yet. The worst part is that while DISM will fail a capture for verify specific reasons (not generalized, or vss is enabled) the log file do not make sense. It will just show some strange message that you have to figure out what is causing it. As an example, this is the errors that DISM will throw if the OS is not generalized COfflineHiveT<class CEmptyType>::Init#63 failed with 0x0. CWindowsOSHelper::GetOSInformation#197 failed with 0x800703f1 CDiskReaderT<class CEmptyType>::GetOSInformation#280 failed with 0x800703f1. CManifest:Initialize#836 failed with 0x800703f1. CManifest::CreateInstance#536 failed with 0x800703f1. FfuCaptureInternal#420 failed with 0x800703f1. FfuCaptureImage#116 failed with 0x800703f1. I did not save the log file for my test capture which was a disk that had an OS that had VSS enabled and was not generalized, but the errors were different. There seems to be a load order regarding what DISM looks at for compatibility, as the log had different errors entirely with nothing in common with this one. I also am not sure about this statement: "Deploy Windows faster on the factory floor by using the Full Flash Update" since I can't imagine how it would be faster to push an image tens or hundreds of gigs in size vs an image that is ~8 GB.
  3. Put those files into a container first. Also you may want to see if the limitation is with the destination file system or not. Explorer can be a limiting factor as it does not support all 255 characters in ASCII, but command.com does. Other programs may also not care about symbols in filenames. To see what kind of symbols you can use, on a modern OS you can use Character Map. Say select Arial and then change the character set to DOS: United States. It will show all 255 characters you can use to create paths (or possibly) filenames with on Win9x, including "No-Break Space."
  4. We don't need more than one "Windows 10 is terrible" threads.
  5. DISM FFU (sector based) does not work if VSS is enabled, among other things. In the end, it was one of those other things that determined I could not use it... the fact that the OS on the disk was not generalized.
  6. I had to install drivers only twice. I think the last time was in October of last year. Their software does have an option to disable auto-update, but not auto-download. It is kind of annoying.
  7. You'll have to wait a while before adding a link in your signature.
  8. I also use an RX 580, but specifically the Sapphire model that has the BIOS switch. At the time I was researching for a new video card, I was only able to find that Sapphire sold cards with 8 GB and supported legacy. The other brands (and still some of Sapphire's) were UEFI only. That doesn't make a difference in regards to drivers, but for viability on a Win7 legacy system in general.
  9. Sharing information on how to download custom Vista ISOs on this site is forbidden. Make sure to read and abide by the forum rules in order for this topic to remain active.
  10. I have three disks that have Windows 10 on them that I have to image. The caveat is that I cannot boot into these disks to see if VSS is enabled prior to doing this. If VSS is enabled, is there a file or folder present that is there and is not if disabled? What about registry keys?
  11. That font doesn't look bad to me. Maybe it is a bit thin. For Twitch, I know that they changed something recently with their fonts, perhaps in the past month. Even on Chrome on Win7 it looks different. Not usuable but something definately changed. But perhaps Twitch didn't change anything and maybe something changed in Chrome. Also that site you put your screenshot on put some giant black box over it, I had to edit the local HTML to see the picture. Maybe put screenshots to someplace else like Imgur.
  12. I didn't know it was the case either until I had requested a custom firmware. One in particular was when I was dealing with a particular board that only supported 32bit EFI, but our imaging platform runs on 64bit EFI. In the initial request, the ODM had provided a BIOS that disabled 32bit EFI and enabled 64bit. This wasn't correct for our uses, and they corrected it by providing a BIOS that has 32bit EFI enabled for Hard Disk and 64-bit enabled for USB/LAN. However, this ability may vary based on the hardware. I only have these two situations from personal experience (the other being the NUC that could do dual 32/64bit EFI) to go on. Physical hypervisors may be different, I haven't bothered to play around with them, nor with bothing to boot EFI on VMWare. Only that in Hyper-V, the hypervisor doesn't seem to care and it is only the VMs that are set to being EFI or not. Also then again, I don't know if you can do 32bit and 64bit on Hyper-V at the same time.
  13. Be it either with WMIC, Powershell or directly interacting with WMI itself. The situation is that Windows reads from DMI during boot and this is the information you can find in the hardware based WMI classes such as Win32_Baseboard. The problem I run into is that if I change the data in the DMI, Windows does not return the new information when reading from the WMI class again. It seems to be because it had populated that information on boot, it doesn't expect it to change. I have verified the information is changed in the firmware, but the relative fields in WMI do not update automatically.
  14. A UEFI isn't really 32bit or 64bit. The Firmware vendor uses a hidden ("BIOS") setting to enable booting 32-bit or 64-bit EFI applications. The hardware market is kind of "rigged" these days, where most firmwares will only run a 64bit EFI application. The exception is for low-powered devices which may be set to run 32bit. There do exist some hardware with some BIOS versions that support booting either that I have encountered in the past. The question regarding your test on the Surface Pro, that apparently worked, is whether or not the image you have created has the EFI boot application or not. I suspect that it never really mattered what the disk type was for booting EFI, but that the market just figured to have gotten past 2 TB disk sizes by now and reality just hasn't caught up yet. Also the consideration that the industry only really cared about the security functions of UEFI, such as Secure Boot and whatever else, as being the reasons why EFI/GPT was/is being pushed so hard.
×
×
  • Create New...