Tripredacus

Supervisor
  • Content count

    11,204
  • Joined

  • Last visited

  • Days Won

    14

Tripredacus last won the day on March 8

Tripredacus had the most liked content!

Community Reputation

256 Excellent

3 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

Recent Profile Visitors

6,676 profile views
  1. I've gone into the about:config on many versions in the past 9 years and never saw this message.
  2. I went into my about:config in Firefox and now see this message! It is 52.0.2. What is it talking about?
  3. I also just remembered that I had this problem on Shiva for many years, but I had attributed it to having a custom splash screen. In a case where Windows would not boot, I would need to use escape key to cancel the splash screen. You may need a PS/2 keyboard for this. For me, that issue went away after changing the video card.
  4. Well sure you can install Windows 7 onto it. We will have to see what people experience with it. I know there are some games that do need some updates, and I haven't found out if this CPU blocking thing only effects Windows Update, or effects updates themselves. For example, what if there is a game that needs an update that isn't available in the catalog? I think my example of H1Z1 requiring an update is not yet a good example because you can get those from MS with just your browser. I'm just thinking of the future and I think I'll let it play out.
  5. Welcome to the MSFN!
  6. The last thing on this log is [0015CABC] Initing hsflop.pdr Is it possible to disable the floppy drive in the BIOS? Have you also done the step-by-step confirmation boot? This sometimes helps.
  7. It will be a long time for me to consider using that, since it is Windows 10 only. I will try to stay using Windows 7 as long as possible. When I have to make a new PC for Windows 10, I will be looking at Ryzen as a possibility.
  8. I think it really depends on usage. I have never run out of hard drive space on OS volume with actual programs and I typically use 80GB disks. My current PC has an SSD, I think 160GB but the only game installed on it is Minecraft. Data understandable to put on another volume. Programs are usually not as forgiving. As an example, if you were to install Office on a different volume, and for whatever reason reinstall/change your OS, that Office installation won't be usable. But it depends on which programs they are for sure.
  9. So apparently one change I found from 1511 (and earlier) to 1607 is that if you specify the wallpaper with an answer file, if you use a BMP it ignores it but a JPG works. What a weird thing to change.
  10. Using an & changes the results to ignore. Probably because 'vista' isn't a valid function for that page, and there is no value for it either. Using & looks like it makes the search ignore the words afterwards. It is really a space, so %20, although you can use a + there if you want. http://www.catalog.update.microsoft.com/Search.aspx?q=KB3164033%20vista http://www.catalog.update.microsoft.com/Search.aspx?q=KB3164033+vista
  11. Things to remember with the XML is that the boot.wim only uses the two windowsPE passes. And then, if you are using Setup to do the install, and use an answer file, it will only use that one. So say you have an XML with just the windowsPE passees in it and nothing else, then no other actions will be taken. Setup will ignore any XML that is in the image itself because you specified it to use another. But Setup always uses an answer file even if you don't specify the /unattend option. So installing using Setup will never use an answer file that already exists within an image. So you can do these two methods. 1. deploy with imagex/DISM, the answer file in the image (c:\windows\system32\sysprep\unattend.xml) is read on first boot after imaging. This XML does not have windowsPE phases. 2. deploy using Setup, the answer file has the windowsPE phases as well as the other things from the XML inside of the image. The other option of using WDS, you can specify a separate answer file for boot.wim and install.wim. This is the only method I know where you can use the two files like that.
  12. I guess I've been asking for trouble my entire life!
  13. Can we get clarification on this 2nd XP, if it is a normal install or it is an XP made with nLite?
  14. If it is a 0x7B on stage 2 of installation, the 2nd stage of XP install will be the reboot and it continues installing from the target/hard disk. Then it would likely mean that the hard drive is detected during stage 1 (text mode) meaning it is writeable but the OS cannot boot from it. If you are using an F6 driver, it may be the incorrect one. If you are not, then you likely need to find the correct one. Fortunately you have a working XP already, you can find the driver version from there.