cc333

It would be nice if they'd backport 6.9.x so I can run this program without having to rely on VxKex, which works well enough but makes the program feel slow and glitchy. c

UPDATE: I just discovered, by chance while researching something else, that Dell had apparently released an updated Windows 7 ISO back in 2016 for select models with Skylake processors (including the OptiPlex 7050), which, naturally, includes the updated NVMe and USB 3.0 drivers, along with any updates released up to then (of which there are many). I don't know how to get it from Dell directly, but I found a copy of the 7050-specific ISO on the Internet Archive, which I'm downloading now. I see no reason why this ISO won't work, so it appears that this is the solution I was hoping for! c

It's a Dell OEM ISO, so it has a few updates (SP1 and such). Yes, but apparently that's not enough? c

Answering myself... I devised a workaround: Using the untouched Windows 7 ISO, install to a regular SATA hard drive Configure the installation with NVMe drivers so it can see/boot from the SSD Use Clonezilla to move the newly NVMe-enabled installation to the SSD I'd still like to figure out why integrating drivers is so weirdly broken, but this ought to work for now while I wait for a fix. c

I'm trying to get Windows 7 installed on a computer, and I have to slipstream NVMe drivers so setup sees my drive, but then Setup blocks me with "A required CD/DVD drive device driver is missing." This would be fine, except I've already integrated ALL of that, so I shouldn't be getting this error, should I? Every driver I try results in either "no device drivers were found" or, if I come across a valid driver and I tell it to load by clicking "Next", it will work for a bit and then tell me "no new devices could be found." I'm using NTLite to add the drivers to boot.wim and install.wim. What am I doing wrong? c

Not really. I tried all the suggestions to no avail. Plus, it happens with a fresh installation. Surely things couldn't get corrupt that fast? c

This is driving me insane! After years as a holdout, I've finally decided to upgrade to Windows 10, because there was some software I wanted to use which wasn't compatible with 7 (I subsequently discovered a workaround, but I wanted to forge ahead with 10 anyway). However, no matter what I do, 10 will eventually begin crashing with the stop code "PFN LIST CORRUPT" almost constantly, to the point where it's no longer usable (this morning, it happened when I moved the mouse!) I've tried fresh installations. I've tried not installing any programs. I've tried installing to an NVMe SSD. I've tried installing to a spare SATA SSD. I've tried spare, known-good RAM, and I've tested it (it passed). I even tried rebuilding my whole d*** computer (Dell OptiPlex 7050 SFF) with all new hardware. As it happens, the motherboard died shortly after this stop code began appearing, so I thought it might've been a precursor to that, but no. The exact same thing happens with the new motherboard. What the h*** is going on? I've never had this kind of problem with Windows 7! c

Now that you put it that way, you are probably right. c

It seems absurd to m that they would want to save money by not hosting older updates and drivers. They have hundreds of billions of dollars, but they can't spare a few million to host some outdated updates that could actually be useful to someone? c

I thought all versions of 10 supported Firewire, provided the correct drivers were installed? c

I think they mean to say that Cleartype (?) hurts their eyes. It doesn't bother me tons (my eyesight, while not awful enough to mandate correction, isn't a perfect 20/20), but I can still tell when it's on, and I tend to prefer how sharp and crisp text is when it's off. Why add extra blur when I don't have to? Recent MacOS versions have it too, but it's more subtle and less annoying (I can still tell the difference when it's off, though). XP had it, too, and for some reason, it wasn't so bad (maybe due to the fact that it was fully optional and off by default). I don't recall Windows 2000 having it natively, but maybe it (or something like it) was backported, perhaps by way of an XP update? c

Ah, yes. I know how to use NTLite. I also remember using it's older cousin, nlite, to slim down XP and 2000 installs (one time I think I got an XP install down to, I think, 200 MB or less, and a 2000 install under 100 MB). Is it possible to somehow pre-activate Windows 10 after I've slimmed it down? I vaguely recall being able to do that with XP. Yeah, you're probably right. I will likely go with whatever the last version is, though, because it's easier. Of course, I have the problem of finding a license key that will work. I could've sworn I had one I got free as a perk from a CS class I took at the local Community College, but I can't seem to find it anywhere. I do have it in a VM, which I painstakingly upgraded – one release at a time – from 1809 to whatever the current is (22H2?). I also was able to update (a copy) of that VM further to the current release of 11, which actually isn't as awful as I thought – once I got rid of that ridiculously useless thing they call a "task bar." It feels more or less like a version of 10, to be honest. Why did they bother upping the version number? Microsoft's logic has escaped me in recent years (the naming scheme they used from the earliest Windows NT releases up to 7 made perfect sense to me). Ha! That's a bit extreme, yes? And if your range was much more than 50 feet, you most certainly would be violating lots of rules with your "jammer." I'm going by the rules and broadcasting on one frequency – 1610 AM. Interesting. Another instance of stock Windows 10 being dishonest and deceptive. An all to common theme in the industry nowadays. c

Hi! It's been awhile since I posted here! I'm mainly using Mac OS nowadays, but I still maintain a Windows 7 VM, and I have a Dell OptiPlex 7050 running Windows 7 Professional that I use for playlist automation (I run a small, unlicensed AM radio station; the neat part is that it's not illegal: look up Title 47, CFR Part 15, Subsection C, § 15.219 of the FCC rules). So, despite it being over 16 years old now and EOS since 2020, it's still perfectly usable and secure enough to at least get done what I'm trying to do, as you can see here: I had an earlier version of this running on XP, but unfortunately, it got too old to run the versions of the above apps I wanted (clockwise from top left: Butt, PlayIt! Live, Stereo Tool). 7 is still in that sweet spot where current versions of these things are still supported, so I'm going to use it while I still can (that said, I'm planning for an eventual upgrade to (ugh!) Windows 10 because, unfortunately, the fun doesn't last forever, and there's no Mac or Linux version of PlayIt! Live). Here's to keeping Windows 7 alive, one PC at a time! c

At least the acronym (BSoD) will still be valid, since both black and blue begin with the letter 'b' c

Hmm, how fascinating. It must be something about your specific hardware that only works best on Vista, and malfunctions (and sounds bad) on any other version. My hearing is fairly good, and I still can't really tell the difference between 44.1 and 96 or 192, so I just go with 44.1 to save on disk space. MP3 at the highest possible bitrate (320) is tolerable, I find, but once it starts dropping below 192, it becomes increasingly awful. My preference, of course, is uncompressed WAV or AIFF (I guess FLAC is supposed to be good, but I tend not to use it much because support for it isn't as universal as it is for MP3 and WAV). c