Leaderboard
Popular Content
Showing content with the highest reputation on 02/12/2021 in all areas
-
Hello , thanks for the advice , the thing is - I never said that I (personally) use any Antivirus at all , someone asked and I just said 3.5.1 works because I know this for sure. As for me , I don't trust any "antivirus" . The best antivirus is brain. :-) Don't you agree ?2 points
-
Introduction: Here, you will find a list of AMD/Intel CPUs/chipsets and Intel/NVIDIA/AMD GPUs which support Microsoft® Windows Vista™. If you have any additions that aren't currently listed, feel free to reply with them and they will be added as soon as possible. Supported CPUs: Intel (Desktop/Server): Note: Windows Vista has been known to work with Pentium III and even some Pentium II processors, however this configuration is extremely suboptimal and the OS is practically unusable on these processors, so using at least a Pentium 4 (Prescott), plus installing Windows Vista Service Pack 2 is recommended for acceptable performance. Intel Pentium 4 (Prescott, 2004-2005) *x64 is only supported from the Pentium 4 505 Processor and newer Intel Pentium 4 Extreme Edition (Prescott, 2005) *Supports both x86 and x64 Intel Pentium 4 HT (Northwood, 2003-2004) *x86 only Intel Pentium 4 HT (Prescott, 2004-2005) *x64 is only supported by F-series, 5x1, 517, 524 and few OEM models in E-series (SL7QB, SL7Q8) Intel Pentium 4 HT (Prescott 2M, 2005) *Supports both x86 and x64 Intel Pentium 4 HT (Cedar Mill, 2006) *Supports both x86 and x64 Intel Pentium D & Pentium Extreme Edition, all models Intel Celeron, all Netburst-based models (Williamette & Northwood-128, 2002-2003) *x86 only Intel Celeron D (Prescott, 2004-2005) *x64 only supported by 3x1, 3x6, 355 models Intel Celeron D (Cedar Mill, 2006-2007) *Supports both x86 and x64 Intel Celeron *all Core-based and newer models up to Ivy Bridge based Celerons; Braswell/Haswell and later do not properly work with Vista. Intel Core 2 Duo, all models Intel Core 2 Extreme, all models Intel Core 2 Quad, all models Intel Pentium up to Sandy/Ivy Bridge G series processors; Haswell and later do not properly work with Vista. Intel Core i3 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i5 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i7 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Xeon 1.4 "Foster" - Intel Xeon 3.2 "Gallatin" *x86 only Intel Xeon, all models from 2.8 "Nocona" to 3rd generation Ivy Bridge Xeon processors; Haswell and later do not properly work with Vista. Intel (Mobile): Intel Pentium M, all models *86 only Intel Pentium 4-M, all models *x86 only Mobile Pentium 4, all models *x86 only Mobile Pentium 4 HT, all models *x86 only Intel Atom *all models up to Bonnell microarchitecture (2012); Silvermont (2014) and later may not properly work with Vista (not yet tested). Intel Core Solo, all models Intel Core Duo, all models Intel Core 2 Solo, all models Intel Core 2 Duo, all models Intel Core 2 Quad, all models Intel Core 2 Extreme, all models Intel Pentium up to Sandy/Ivy Bridge mobile processors, Haswell and later do not properly work with Vista. Intel Core i3 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i5 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i7 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. AMD (Desktop/Server): AMD Athlon 800 - Athlon 1000 (Pluto/Orion, 2000) *x86 only AMD Athlon 800 - Athlon 1400C (Thunderbird, 2000-2001) *x86 only AMD Duron 800 or later (2000-2003) *x86 only AMD Athlon XP, all models (2001-2003) *x86 only AMD Athlon 64, all models AMD Athlon 64 X2, all models (X2 & K10) AMD Phenom, all models AMD Opteron, all models AMD Sempron (Palermo, Socket 754; July/August 2005) *x64 only supported by all models with an OPN ending in BX and CV) AMD Sempron (Palermo, Socket 939; October 2005) *x64 only supported by all models with an OPN ending in BW AMD Sempron "Manilla" or later, all models AMD FX (Bulldozer Family), all models AMD Ryzen (all Summit Ridge models; Raven Ridge has yet to be tested) AMD (Mobile): AMD Mobile Sempron, all models (2003-2006) *x86 only AMD Mobile Athlon 64, all models (2004-2005) AMD Turion 64, all models (2005) AMD Kite Platform - AMD Carrizo Platform, all CPUs & APUs (2006-2015); Bristol Ridge (2016) may work but has yet to be tested. Supported GPUs: Intel GPUs: Intel 915GM/GMS will work with Windows Vista by using XP drivers, however Aero Glass isn't supported due to lack of WDDM drivers. Intel GMA 950 (Desktop: 945GC, 945GZ, 945G; Mobile: 945 Family) or newer, last Intel GPU to support Vista is Intel HD 4000 series (Ivy Bridge; Desktop and Mobile). Download Intel HD 4000 Graphics Drivers for Vista: 32 bit - 64 bit ATI/AMD GPUs: ATI Radeon 9250 and all later GPUs released prior to the 9500 will work with Vista using XP drivers, however Aero Glass isn't supported due to lack of WDDM drivers. ATI Radeon 9500 or later; last AMD GPU to support Vista is AMD RX 300 series; drivers are coming soon. The first official version of ATI Catalyst to support Vista is version 7.1. The last official version of AMD Catalyst to support Vista is version 13.12 (Download: 32 bit 64 bit). However, newer versions up to 15.6 Beta for Windows 7 can be modified to work on Vista. View this thread for more details. NVIDIA GPUs: NVIDIA GeForce FX 5100 and later NVIDIA GeForce 8 series to GeForce 300 series; download recommended driver here: 32 bit 64 bit NVIDIA GeForce 400 series and later; last NVIDIA GPU to officially support Vista was the GTX 980 along with driver version 365.19. Download here: 32 bit 64 bit - Note: Vista 3D Vision support was dropped around version 310.00. The GTX 1060, 1070, and 1080 can also be made to work with Vista, as driver versions up to 372.70 work with Vista, albeit not officially supported by NVIDIA. Download here: 32 bit 64 bit - Note: DirectX applications aren't properly utilized by these drivers under Windows Vista, so this will cause a bottleneck in performance over using the GTX 980 or older, where the 365.19 drivers (more optimized for Vista as they're officially supported) can be used. Final Apple Mac Computers to support Vista via Boot Camp: iMac; all Late-2009 models Macbook Air; all Mid-2009 models (32-bit only) Macbook and Macbook Pro; all Mid-2010 models Mac Mini; Mid-2010 (This is the only Mac Mini to support Windows Vista 64-bit; earlier models are 32-bit only.) Mac Pro; Mid-2010 Miscellaneous Hardware: Looking for an Xbox One Controller driver for Windows Vista? View this thread for download + how to install (HUGE THANKS TO @GTAGAME for this.) Download Elgato HD 60 S Capture Card drivers here - to install, extract the exe with 7-ZIP and manually install the drivers in Device Manager (thanks again to GTAGAME for pointing this out).1 point
-
There is no listing of all 200 tweaks per se. The setup only installs seven new Control Panel applets shown in the online screen shot and a half dozen new desktop context menu shortcuts, also shown in the screenshot. But, after installation, if you click on the "Tweaks Guide" link in the start menu you will see a guide to detailed instructions on installing the the other tweaks. The setup package is uninstallable, so you can read the tweaks guide and keep it and uninstall everything else. Hope that helps.1 point
-
Disabling Javascript in your browser won't protect you at all from "Remote OS detection via TCP/IP Stack FingerPrinting", which is what appears to have happened in your posted screengrab... More stuff for you to read, am afraid... https://en.wikipedia.org/wiki/TCP/IP_stack_fingerprinting1 point
-
1 point
-
Basically, I'm just on this copy of Windows I'm on because it's just been working. I've had my problems, but I haven't worried about tweaking or fixing more than just simply using the computer. Really the only option, compared to Linux, which was just a complete and total disaster when I tried it - rather would use my computer than have to work on it all the time.1 point
-
Yes, this is quite true. ^_^ Indeed, it can also be made into a rather fun learning experience if you learn and slowly digest that information within a safe environment such as a virtual machine. So, if you ever somehow broke something you could simply roll back to the previous snapshot and start from where you left off.1 point
-
If you're looking for a fully integrated OS like Windows, I think you'll be disappointed in most Linux distros. The big distros like Ubuntu, Mint, and Fedora come close, but I still have to do more troubleshooting (sound and wireless networking is a hot mess on Linux) than on Windows 10. However, it may be a solution to some of these people complaining about the telemetry, lack of customization, high system requirements, and UI changes in Windows 10, as long as you're willing to deal with a steep learning curve.1 point
-
Delete api-ms-win-core-memory-l1-1-0.dll from the Pale Moon folder and then it will run, falling back to Vista-compatible binaries in system32 installed by the VC++ 2015-19 runtime. This is the second program broken by Windows 10-derived runtime libraries (Code::Blocks was the first). Though in this case, there are no missing functions, but apparently that DLL delay-loads some functions that are certainly valid, but have ".dll" attached to them, making them invalid.1 point
-
1 point
-
You know , actually I'm not surprised at all , esp. with all that what's going on in the world after 2001. I have a suggestion , how about we start to make spelling errors > like "ckhromyum", "gugle" ,I guess they are looking for key-words , aren't they ? What do you about that ?1 point
-
Whoa , this poor user is banned after giving a good advice ! Someone really didn't like Chromium being able to run on Vista ....1 point
-
I'm not French , all of my settings are en-GB , English, keyboard and local too. Edit : tried to set everything to US (region , keyboard, location) no luck.1 point
-
I just tested this on NM28/UXP and it still does! Test site to verify: http://browserspy.dk/browser.php (Please note this pref doesn't modify the reported Windows NT version contained in the User Agent String (navigator.userAgent), so a website checking both strings via JS may get conflicting results: )1 point
-
To fake the OS which gets reported by javascript, hope this pref still works: general.oscpu.override = Windows NT 6.31 point
-
Hi, 7Customizer is a tool for creating customizing and deploying Windows 7 installation (both 32bit and 64bit editions). It works on both English and non English installation sources. Follow the development of 7Customizer on Twitter. Click here. VERY IMPORTANT NOTE Since this thread is now sticky it will draw more attention. It will also draw repetitive posts that reports the same problem. Before you post in this thread: Read the first post of this thread(the one you are reading right now) first and then read the visual guide here. Then if you find a problem or bug report it in this thread. 7Customizer is still in development stages and it is still in testing phase. It might not work for you or crash with error. If that happens report it in this thread. Note: This thread is dedicated for debugging and testing and discussing issues related to 7Customizer only. If you need help regarding DISM or regarding a certain problem in a driver you wish to integrate or anything that is not related to 7Customizer , you should post your problem in the appropriate forum. Note: Read about 7Customizer components XML here Table of Content: 1. Functions and features 2. Screen shots 3. Requirements 4. Important notes 5. Other notes 6. Known bugs 7. Reporting bugs 8. Using 7Customizer in XP 9. To do list for current release 10. To do list for future releases 11. Feature that are not likely to be implemented 12. Making a bootable USB with customized Windows 7. 13. Guides 14. License Agreement 15. Version History 1. Functions and features: The functions that are implemented and tested by me and the forum members are: 1. Languages integration (Windows UI language not the setup language) 2. Updates integration 3. Basic unattended installation 4. Driver integration 5. Tweaks 6. Services 7. ISO Creation 8. Presets 9. UAC trigger 10. Clean mount folder 11. Wallpapers integration Implemented but still need testing: 12. Themes integration 13. Windows 7 Enterprise edition support 2. Screen shots 3.Requirements: 1. Windows Vista or Windows 7. (32 bit or 64 bit) 2. WAIK for Windows 7 (here). You could use WAIK in any language (English,German, Italian ,...... etc) 3. Windows installation source. To use 7Customizer just extract the files and start 7customizer.exe 4. Important notes for using 7Customizer: 1. Make sure you have enough free space (at least 5 GB of free space is recommended) in your drive where 7Customizer is located (7Customizer will warn you if the drive does not have sufficient space) 2. It is highly recommended to run the program in a folder that does not have white spaces for example, c:\7Customizer\. 3. It is highly recommended to place your installation source in a directory that does not have white spaces for example, c:\win7. 4. When choosing the path for ImageX and DISM, make sure you choose the same exe architecture (x86 or amd64) as your Windows. eg when using Windows 7 x64 choose the ImageX located in amd64 inside the WAIK installation. 5. Always test the result in a virtual machine first (VirtualBox, VMware player or VirtualPc). 6. It is highly recommended to use 7Customizer on an unmodified (clean,untouched .. etc) windows installation source. 7. It is highly recommended to place 7Customizer in the root folder (e.g D:\7customizer). It is not recommended to place 7Customizer in your home directory folders (e.g. Documents,Desktop,... etc). 5. Other notes: 1. The languages you integrate are not for the setup part. It is for the Windows UI. 2. The keyboard, date ,currency and time zone ,in the unattended part, are not for the setup part. They are used for the user settings after the installation is done. 3. Fill the whole information in the unattended part or the setup will fail. 4. Always integrate drivers that supports Windows 7. Drivers that does not support Windows 7 might not be integrated properly or might not be integrated at all. 5. If you face issues integrating drivers, these issues are related to DISM not 7Customizer. Do not report these issues. I can not help you with that. 6. 7Customizer does not support Windows Server 2008. I am not planning to support it. However, if I plan to support it, it will be after finishing 7customizer. 7. When removing components, the resulting ISO's size might not decrease. However the installation size of Windows 7 will decrease. 6. Known bugs 1. 7Customizer sometimes fails to read the images information correctly (This is related to using 7Customizer on a modified installation source)(This issue is still not solved, if you still face this problem attach your log.zip). 2. When selecting updates 7Customizer, some time you will be able to select one update only. If you select more than one update 7Customizer will crash.(This issue is solved in 0.4.4 but it is still not tested). 7. Reporting bugs Before you report a bug make sure you read the requirements and important notes and known bugs. When you report a bug please provide the following info: You must post the log file (log.zip) created by 7Customizer. This will help track the problem. The log file is inside the work folder. 1. Any information that you think it is useful 2. Screen-shot 3. When posting your autounattend.xml do not forget to remove your product key. 4. All the information ,screen-shot ...etc should be in ENGLISH. 8. Using 7Customizer in XP Note: I have tested 7Customizer in Windows XP. It did not work well. 7Customizer is developed and tested in Windows vista or 7. I will not test nor support 7Customizer under XP because WAIK for 7 does not support XP (This is from Microsoft). However to use 7Customizer in XP you will need two tools: DISM and ImageX. 1. To get dism in xp, jaclaz has posted a link to install dism on XP (it is in the first page of this thread). 2. To get ImageX in xp, download and install WAIK for Vista. You could also Google for this and you might find an easier way. 9. To do list for 0.5.x release Removing components. Add more components to be removed. Fix any pending issues that were reported by the users. Update the visual guide. 10. To do list for future releases:(in no particular order) Make a setup for 7Customizer Select default wallpaper remove themes and wallpapers from the list Command line interface Adding applications Join workgroup/domain A list of last selected installation sources An option to set the Users folder location, program files locations and other folders. Check if 7Customizer can be supported under XP. Check whether the start orb could be replaced or not. uxtheme patch. OEM branding. integrate icons. 11. Feature that are not likely to be implemented Progress bar instead of the command line progress (not likely because the whole execution is done through the command line) Partition disk (not likely to be implemented) Burn ISO to DVD(not likely because they are lots of programs that burn iso to DVD) When saving the image, include all the editions (Rebuild all as in vlite or stefanRTR's win integrator) Integrating languages in the setup part. (It is really unnecessary). 12. Making a bootable USB with customized Windows 7 To make a USB from the customized Windows 7, use WinToFlash (Click here) . To make a bootable USB, it requires an empty flash drive (If you have files in the flash drive, WinToFlash will erase them). Start the wizard in WinToFlash and give it the directory where the customized Windows is located and the flash drive directory and click Next. It will do its job, when it finishes you will have a bootable USB flash drive with your customized Windows 7. 13. Guides English Visual Guide click here . German guide click here (by beatmaster). Japanese guide click here (by DH.Omega). French guide click here (by myselfidem). Italian guide click here (by ascatem) Swedish guide click here (by grabben) Spanish guide Click here 14. License Agreement: (blah blah blah) 7Customizer is a freeware tool. You could use it only for any personal non-commercial purposes. 15. Version History: ===v0.5.0 Beta 1=== 18 March 2011 Added: Components removal. Added: 7Customizer will create a log.zip file that will contain all the info I need to fix the issues. So if you face a problem attach the log.zip. Updated: 7Customizer requires .net framework 3.0. That means it will run directly in Windows Vista. Note: 7Customizer 0.5 is a beta release. I am releasing it to show you how I am implementing "components removal" using components.xml which I will write a post about it. ===v0.5.0a=== 6 October 2011 Update: Fixed an issue reported by justibus where the file in the components.bat are not surrounded by quotes. ===v0.5.0b=== 6 November 2011 Update: Fixed an issue reported by justibus where the components tree wasn't build correctly. Added: More components submitted by justibus. ===v0.5.0c=== 9 November 2011 Added: An option to disable verifying deletion of files, which drastically reduces the amount of time to build the customized image. Added: More components submitted by justibus. 7Customizer_0.5.0b was downloaded 75 times 7Customizer_0.5.0a was downloaded 785times 7Customizer_0.5.0 was downloaded 3675 times Regards 7Customizer_0.4.4.rar 7Customizer_0.5.0c.rar 7customizer changelog.txt1 point