Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/03/2021 in all areas

  1. Warning: This only works with versions between 11.0-11.1.2 / 12.0.0 in 64-bit versions of Vista, later versions still do not work. Officially the latest version compatible with Vista in both artitectures is VMware 10.0.7 but VMWare 11.1.2 and 12.0.0 also works in Vista. Process: Install VMware 10.0.7, when starting the program choose the 30-day trial as there will be problems with the license when installing VMware 11 or 12 Create a virtual machine and install Windows 7 there or on another partition or another PC. Then install VMware 11 or 12 there. Returning to Vista, stop all VMware related services and processes Remove the VMware folder from ProgramFilesx86 and replace it with the VMware 11/12 folder Replace all VMware-related files in system32\drivers with those of VMware 11/12 The same as point 4 nothing more than with ProgramData\VMware Restart Windows Vista VMware 11 in Windows Vista !!!
    1 point
  2. The staff is aware that there are currently spambots sending out private messages to random members here on the forum. We are actively dealing with the situation but if you happen to get one of those spam messages, please do not simply ignore or delete it but use the report system so that we can permaban every account responsible for these messages. Thank you for your patience!
    1 point
  3. Hi everyone, My name is Ricardo and I'm 25 years old. I am a big collector of vintage hardware and software and have been for about half of my life. My daily occupation is IT support for other companies and mainly with Windows client/server networks. Besides this I have always been a big fan of social events, tinkering, cars and I have a big general interest towards fascinating things.
    1 point
  4. So, Ruffle is written in Rust and AFAIK all Rust applications require SSE2 capable system... Thanks, but no thanks. I'll keep my flawed Flash player instead of throwing my PC in the trash and spending on a newer one!
    1 point
  5. I have been able to watch 4k video in Serpent 52 on Windows 2000, but it is set to Vista user agents usually.
    1 point
  6. I know people who do that, but can't understand why. Why not just use an OS that doesn't require such tweaks, like W7? W7 still requires tweaks, but at least they can all be done through GPOs or reg edits or built-in OS toggling. No third party software needed to make it not drive you insane! Compatability for 8x can be even worse than 7 so I can't see that being a bonus, either. Security updates for 8x will end before or at the same time as security updates for 7 do, IIRC.
    1 point
  7. Only to confirm your impression, but on the very opposite side of the spectrum (low power machines, where a comparison is more likely to show noticeable differences). I just got two extremely el-cheapo (and old but in themselves "good enough") netbooks, identical, Asus EEE PC 12.1" 1201T (a not-so-common model sporting an AMD MV-40 processor). These machines are (were) intended as "pure" netbooks, i.e. minimal browsing and "normal" everyday activities in a rather light and portable format with a several hours lasting battery. Put on them both the max RAM (2 GB) and new 240 GB SSD drives. On the first I restored (from recovery partition) the original OS (Windows 7 Home Premium 32 bit), which I then updated to SP1 and via Windows Update to an as much "current" situation as possible. On the second I experimented an install of Windows 10 home (last release 2020, directly from MS original iso). I won't detail the amount of troubles I had to actually install the stupid Windows 10, as it would become a rant, but trust me it wasn't easy (on the other hand in the Windows 7 one having to deal with Windows Update (non)response times has been as well really trying) Anyway, after having run them both a few hours and having let them "settle", I briefly tested the two PC's side by side (literally). Quick sum up: 1) booting times: Windows 7 is seemingly a tadbit slower to get to the desktop, but Windows 10 is "faking", if I count the time until the Start button responds, W7 is faster 2) CPU usage: Windows 7 uses far less CPU at rest (including running in the background some of the built-in ASUS tools), W10 has a sh**tload of processes eating CPU time 3) RAM usage; Windows 7 at rest is around 532 MB, W10 at rest is around 1.1 GB (more than double) Right now I am re-setting/re-installing the second netbook to Windows 7, and make it identical to the first one. jaclaz
    1 point
  8. Without patching the operating system in a way that makes sfc /scannow fail? Enlighten us, please... The W10 PowerToys are useless IIRC. The XP ones were more useful. Well, I think I'd go mad if I didn't have OpenShell on W10 when I have to use it You're saying people should just use the default sorry excuse for a start menu? It looks more like what an 8x real start menu would have looked like but the point is functionality not look necessarily. Best solution: upgrade to Windows 7, and forget about Windows 10, if you can!
    1 point
  9. There is a new extended kernel version released. Development was hindered greatly by the struggle to make new x86 shell32 functions well, function. ntdll is the source of that discontent and the secret may lie in either the Server 2003 version or even one from a later Vista build. Most x86 programs rely on the shell32 functions, which means that there will not be much in the way of new x86 programs working aside from what has been shown already. However, SetThreadErrorMode has been stabilized on x86 and WMP 11 x86 (the default WMP on Vista x64 as well) is working again (x64 version continued to work anyway). TryAcquireSRWLockShared is implemented on both Vista x86 and x64; there were several programs I'm aware of asking for it.
    1 point
  10. Here I sit at the end of 2020 setting up a new high-end Dell workstation running Win 10 Pro for Workstations 20H2... The machine has double the processor speed, double the RAM bandwidth, 3x the GPU speed, and 6x the I/O throughput capacity of my prior workstation, and I'm thinking I've got it in pretty good shape with "only" 137 processes running to support an idle desktop... Seems snappy enough, though not knock-your-socks-off faster compared to my circa 2012 workstation running Win 8.1. Seems just about equally interactive, actually. It's not like Visual Studio starts up instantly. The machine's specs are way beyond the computer of my wildest dreams when I was younger yet somehow still feels disappointingly bloated even after a half day of setting up and tweaking. Guess I still have to tweak some more. I installed the latest VMware Workstation version and booted up a Win 10 VM I hadn't used in a while and realized it's still on v1909 build 18363.693 and still runs Big Muscle's Aero Glass for Win 8+ just fine. Sigh. I thought I had gotten used to these stupid, Windows 10 square borderless windows and now I see these windows with borders and rounded corners and feel the pain all over again. Elegance is worth something and its loss hurts forever. I hate how a machine that can complete a copy of a 2 GB file in well under a second still puts up a progress bar for the deletion of a single small file because I guess Microsoft feels laypeople need more feedback. Why does bloat have to expand to equal the rate of hardware improvement? Where is that written? -Noel
    1 point
  11. The previous version of patched driver caused crash (memory protection BSOD). This was probably due to Dword at 144h that I left untouched but it seems it may be code size so I had to adjust it. Now it should go a bit step further, file reuploaded: http://rayer.g6.cz/1tmp/7772mod.vxd
    1 point
×
×
  • Create New...