• Content count

  • Joined

  • Last visited

Community Reputation

224 Excellent


About Tripredacus

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

Contact Methods

  • AIM
  • Website URL

Profile Information

  • OS
    Windows 7 x64
  • Country

Recent Profile Visitors

4,254 profile views
  1. I usually resort to making it so that the OS installs the driver when it boots. Of course, this wouldn't apply to a mass-storage driver.
  2. Hmm they had removed the developer tools at one point? Phew I'm glad I've been putting off updating then.
  3. Welcome to the MSFN!
  4. Some files can be marked with the H flag and not also the S flag.
  5. I still use Vista occasionally for refurbs and see this issue. While it seems there are specific KBs to fix this in 7, I never had heard about any similar fixes for Vista. I'm sure that a fix exists for it, but that the userbase still doing Vista installs is comparatively low.
  6. Oh yes, thanks for reminding me. If you have set up a software mirror from within Windows using Device Manager, that can turn out even worse. In that case, you should still do a full backup before hand, with the idea that you'll be restoring data. And if it survives, you'll have less headache and at least you'll have a backup of everything.
  7. Because of the risk of data loss. I've seen scenarios where the volume becomes corrupted, changed to RAW, doesn't appear anymore, array broken, Windows using the wrong driver in the new OS, the RAID software not working with the new OS and/or driver, etc. It is not impossible, but you can't know what the outcome is before-hand. So many variables in play. The safe way is to make a full backup of the array to another disk set. The easiest is if you are using a controller card and your OS is not on it. Then you simply remove the card from the board, then do the upgrade (or change the OS entirely). After the new OS is set, then you put the card back in and install the driver and software and it should be just fine. This is the safest example I can think of, because if you remove the card from the system (but leave the disks connected to SATA but not power) you shouldn't have any problems since no changes were done with the array at all. Even in this case, it is best to make a backup of the data, in case something happens, then you can just copy it back to a fresh array.
  8. SVG Viewer is pretty much deprecated. If you are still using an application that uses (functional) SVGs, you might have problems in Windows 7. By now, at least Firefox can use some of the SVG functions (drawing, fill and motion) but does not support others such as gradient... which I think that functionality came directly from IE's gradient function anyways. That just covers the basics. If you are not using any advanced SVG that do things such as linking or any full SVG applications, you can get away with not using it anymore. When doing an in-place upgrade, make sure you can find the drivers you need ahead of time for the new OS. The important ones are chipset, video, audio and lan. You should download these before doing the upgrade, and also perhaps put them on a CD or USB drive. If you have a RAID array, it is advised that you do NOT do an in-place upgrade.
  9. This is already happening. Not just with schools. Many people have reported that putting multiple Windows 10 systems on their network is saturating their available bandwidth. And like a lot of things with Windows 10, the settings to change to prevent this from happening often does not work or change the situation.
  10. I find most of my games locally at thrift or flea markets. Online can be a problem because the shipping can really add up. If Ebay is not your thing, there are some alternatives like other classified sites. I do not know one for Denmark. I know there is for France, where I go to look for things sometimes. If you are talking about download only games, I'm not sure. I don't deal with those really.
  11. Welcome to the MSFN!
  12. It will be a wait-and-see type thing I suppose. I don't do any work within Windows 10 using .cmd files. I only use those in WinPE. My work within the OS uses the ComSpec environment variable to pass commands to be run using cmd.exe.
  13. Let's hope their choice of changing 'cmd' to run Powershell prompt doesn't screw with anyone's scripts or programs that call CMD to perform specific things, such as installing programs. On this new build, is the ComSpec environment variable changed as well?
  14. You can see it in the properties of the device in Device Manager.
  15. Ok well there are some caveats. It may depend on what edition you are using. For example, Retail (which allows for transfer to new hardware) may be more forgiving than System Builder edition which doesn't. Also I do not consider a motherboard to be a minor upgrade. A person should expect to have to reactivate Windows if you change the motherboard. For my own personal experience, I've only had to reactivate a Windows 7 system after changing a motherboard. Not for anything else like video cards, disk drives or network cards. Fortunately, for Windows 7, it is fairly easy to reactivate. Ensuring internet access is present, most of the time you can just run slmgr.vbs -ato. And nowadays, the phone activation is better than it once was, where the Activation number will give you an option to text you a link where you can go to a website to do the number groups if need be. Way easier than talking to someone on the phone!