Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 05/12/2021 in Posts

  1. I also personally run pure Debian with XFCE.....I use Windows 10 for my business... "Rome wasn't built in a day" comes to mind.....;) We will never change Microsoft.....they got lost along the way...it is a shame that everything comes down to money.....this is why I will never respect Microsoft for what they have become.... bookie32
    3 points
  2. Yup, not here anymore either: https://support.microsoft.com/en-us/topic/may-2021-updates-for-microsoft-office-e89b2f2b-29f0-4692-b7c1-e05d55e18b33 from; https://docs.microsoft.com/en-us/officeupdates/office-updates-msi
    1 point
  3. No Office 2010 updates offered this month. This could well finally be the end.
    1 point
  4. http://ftp.unicamp.br/pub/apoio/iexplorer/ie60sp1/ie60sp1.zip This seems to be a Portuguese version of IE6 SP1, try it.
    1 point
  5. what is most stupid is removing some simple useless component ubuntu wants force to your causes whole DE flagged to be removal. Same wont happen on mint or debian or anything else with same it is because companies do not care about privacy, security or customer opinions. They care about increase shareholder value at any cost good examples being ads everywhere on windows, forcing ms account even to simple tasks and on ubuntu side was Amazon spyware preinstalled on systems. I wish companies and others here would do same and stop using Windows, but no since "Linux is unknown and nerd os". Redhat is way better than Windows 10 for security, privacy and reliability I personally run pure Debian with XCFE for having full control over my system. Volunteer made projects rarely does anything bad.
    1 point
  6. A lot of companies here in Sweden don't trust Microsoft with their security....Several use Redhat now...Ubuntu is a disgrace to the Linux community! bookie32
    1 point
  7. I came across this page, which provides instructions and official Microsoft (Digital River) download links to the files needed to create a bootable Vista installation DVD. A couple of additions/notes to the instructions: The name of the subdirectory where you place the installation files cannot have any blank spaces in it. (For example, I had created a "Vista64 ISO files" subdirectory, and the PE CLI objected, thinking it was supposed to look for "Vista64.") Microsoft's instructions for installing the WAIK say that it's distributed as an IMG file, but it's actually an ISO. The file to click on, on the WAIK disc once it's burned, is startcd.exe. The PE CLI needs to be opened with administrator rights, otherwise when you enter the commands it will return an "access denied" error. And yes, there is no space between "-b" and "C:" right after "oscdimg", and both lines displayed are typed as one single, continuous line. When burning the ISO, you of course know not to use the native Vista DVD burner -- it doesn't do anything useful (at least for me). I used Power2Go instead.Finally, if you want to install a fresh copy of Vista you will of course need a valid license key. In my case, I downloaded the files and created the disc for myself because my PC vendor didn't supply any OS discs and I wanted something more than a "recovery" disc. Enjoy! --JorgeA EDIT: additional info
    1 point
  8. For anyone that might be interested in the possibility to continue using partially defective RAM, I have one such module in my laptop. I figured from Memtest86 results (addresses) that the faulty parts are somewhere near the end, somewhere in its last 40 megabytes. There's just one 2 GB stick. So one can tell the OS to not use the last 40 MB by running this in the Command Prompt: bcdedit /set {current} removememory 40 If there's 2x 1 GB sticks for instance and those 40 MB would be in the one in the first slot, it would be a good idea to swap their places as cutting whole 1064 MB isn't desirable. Those addresses in hexadecimal notation address the bytes, so one has to convert to decimal and do some math or use some (online) conversion tool to get the megabytes and calculate the difference from that point to the end of the module. If I remember correctly, I actually put the result in the {globalsettings}, not {current}, so that way, it works for the recovery environment and other Windows versions booted through that Windows Boot Manager instance, not just the running OS from which bcdedit was run. There's also truncatememory that can be used instead of removememory, which accepts address, but I've never used that option (https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/boot-parameters-to-manipulate-memory). In case someone has very minimal faulty bits, they can be more precisely mapped out using: bcdedit /set {badmemory} badmemorylist PFN1 PFN2 PFN3 ... Individual 4 KB blocks (pages) can be mapped out of action this way, so whatever addresses Memtest86 gives, they have to be rounded down to the nearest page (so one gets the multiple of 0x1000) and then the last 3 zeros have to be cut from the result to get the Page Frame Number that Windows accepts in hexadecimal notation with a 0x prefix. RAMMap can be used to verify that bad pages are no longer on the list. Got this from Super User. Also, badmemoryaccess doesn't have to be explicitly set anywhere, it already defaults to no if not present; with default configuration, it's only explicitly added and set to yes on the entry for launching Windows Memory Diagnostic, so parts marked as bad are accessible and can be tested.
    1 point
  9. They probably wont change, which is why most people who want control of their PC have to chug along with older Windows, deal with 10 or move to Linux distros like Mint or Arch, since those are by smaller companies. Canonical fell to what Microsoft started doing.
    1 point
  10. = Quick and Dirty YouTube = Just a few lines of code to download most videos from YouTube, set up an Enhanced Cygwin-Lite install: https://msfn.org/board/topic/177106-running-vanilla-windows-98-in-2020-and-beyond/page/17/?tab=comments#comment-1175895 Download the script named 'yt' and copy the file to C:\CYGWIN\BIN. Nevermind visiting YouTube, just use a search engine like Dogpile (doesn't obfuscate YouTube URL) from the RetroZilla Search Engine Collection to search (search_term + youtube). Right-click the desired Dogpile search result and select 'Copy link location' to get the YouTube URL to system clipboard. Open a Cygwin-Lite Bash prompt, run 'yt' (or whatever you named the script) and it will automagically fetch the itag 18 video to C:\WINDOWS\TEMP as a time stamped MP4 file. The DuckDuckGo-Lite search engine from the RetroZilla Search Engine Collection also works well. Just perform a search as 'search_term site:youtube.com'. Although DuckDuckGo obfuscates the search result URLs, opening the desired YouTube URL to a blank (broken in RetroZilla) YouTube page will convert the obfuscated URL to the proper YouTube URL where it can be copied to clipboard for the script to utilize. Add code if you want to extract the video title, autoplay the MP4, whatever. Substitute itag 22 if you want better quality video - too hard on my old system. Note works as of today, YouTube changes regularly, just maintain the code. yt
    1 point
  11. i have windows 7 x64 bit, and i really want to dual boot it with windows vista, but i keep getting a error, i tried different iso's different usb sticks no matter what i do i always get that error and i dont know how to fix it, i was using windows vista ultimate iso's, i would appreciate any help. Also i am very sorry for the blackness on the camera it is because the lens are cracked. https://ibb.co/b2tf2W4
    1 point
  12. this problem is solved, i installed windows vista and then 7 and also thanks for the info on dualbooting.
    1 point
  13. You are supposed to install the older OS first (vista) Make sure you install it on a MBR partitioned drive what are your pc specs?
    1 point
  14. 1 point
  15. From my testing, Firefox 53 Nightly build 2016-11-21 works perfectly fine in Windows Vista... how long this will continue, I don't know. I'm not sure why it isn't working for you, but here it is... Didn't need to copy over any DLLs or anything, as Windows Vista should already include AVRT.dll, according to MSDN: https://msdn.microsoft.com/en-us/library/windows/desktop/ms681975(v=vs.85).aspx (see minimum supported client and DLL in the chart at the bottom of the page)
    1 point
  16. Isn't it possible to copy AVRT.dll from Windows 7 to Windows Vista?
    1 point
  17. The latest Nightly version of Firefox 53, build 20161119xxxxxx+ will no longer start on Windows XP/Server 2003 or Vista since it now requires AVRT.dll from Windows 7. Apparently, without any unofficial fixes, the last good build 20161118030222 is the last to work on these OSes. Infact, Nightly builds of Firefox 53 through 20161118030222 will not work correctly, if not at all.
    1 point
  18. @smeezekitty Sorry to bother you about this yet again, but Adobe Reader DC will no longer run on Windows Vista as of somewhere around v.2015.007.20033, as it is looking for GetThreadErrorMode and SetThreadErrorMode, which obviously it can't find since these functions are exclusive to Windows 7. Would it be possible for you to stub these calls in your kernel32.dll wrapper? Thanks a ton for the work you've done so far for Vista, it's really appreciated.
    1 point
  19. I know this is late, but I couldn't get it to work, unfortunately. Even running the application as an admin, after setting it to the desired OS, it just simply did nothing on Vista. I guess it was intended solely for use on NT 5.x., hence the name. Also, I thought I should give this thread a bit of a bump, as I've updated it to include quite a bit more useful information that may be of some use to some users, and this thread is quickly getting buried due to inactivity. As more and more applications drop support for Windows Vista, a lot of system admins and IT pros that still have to service Vista systems or even just enthusiasts that are interested in using Vista may find this thread useful (and yes, believe it or not, they're still out there ). It is also worth noting that a lot of this information is also applicable to Windows XP, since a large number of developers dropped XP and Vista support simultaneously. Also, since Server 2008 is essentially the same OS as Vista, I've added that to the list, so anyone looking to run that OS should also find some use in this thread.
    1 point
  20. The tool changes the Windows Registry which fools software into thinking its running on the selected OS How to use: NNN4NT5.cab>NNN4NT5>Then select a destination for the file (I prefer desktop for convenience unless you prefer somewhere else)>Open the exe file and change registry! Warning: Set the registry back to Vista before turning off! Otherwise Windows won't boot properly!
    1 point
  21. GIMP 2.8.18 has been released. However, without any tweaks, the latest version of GIMP will not run on Windows Vista. To get GIMP 2.8.18 running on Windows Vista and overcome these restrictions. 1. Right click your mouse and click Properties. 2. Select Compatibility tab. 3. In the Compatibility mode, select Windows Server 2003 Service Pack 1 and press OK. I'm wondering which entry points for GIMP exist in Windows XP SP3 and Windows 7 SP1, but NOT in Windows Vista.
    1 point
  22. I have attempted this before by simply changing any reference to Windows NT 6.1 (Win7) to 6.0 (Vista) in the .inf file. With Ivy Bridge, this method usually works. But with Haswell, I get varying errors when attempting to install the driver. The one I recall the most was Code 39. Unless someone who has the knowledge is willing to find out what dependencies are missing and is willing to add them somehow, Haswell's Vista support will remain incomplete. It isn't worth the trouble of using Vista on haswell anyway due to the aforementioned bugs.
    1 point
  23. Is there a way to modify the file to work on Vista? The same thing can be done with Windows 2000 only wireless adapters to Windows 9x IF there are no missing dependencies! (And those two use different kernels!) According to Dibya there are 20 or so less files in Vista than in 7, there maybe a good chance it would work without the OS blocker
    1 point
  24. Ah yes, can't believe I forgot that one since I used it on Vista quite a bit myself. Added to the list.
    1 point
  25. Open Broadcaster Software: 0.657b -- ONG Requires Vista SP2
    1 point
  26. Agreed. I've never used SBS 2008, but I'm sure it shares the same kernel and version number with Windows Vista, and I doubt that the drivers would work on it. I might test it when I have time since Microsoft offers a trial version for download just in case, but I doubt I'll have luck.
    1 point
  27. I do not believe that you overlooked something. It rather appears that Intel failed to property write the driver to support Windows Small Business Server 2008.
    1 point
  28. I tested on both Windows Vista Ultimate 64-bit SP2 and Server 2008 Enterprise (v6.0.6002) and unfortunately, the driver refused to work on both OSes, so it's definitely geared towards Windows 7-based OSes, unless perhaps there are more differences between Windows SBS 2008 and Vista than we know about. Although, when I was studying the .inf file, I only saw a section for NTAMD.6.1, indicating that the driver is meant to work on Windows 7 only, unless I overlooked something.
    1 point
  29. I do note that the in somewhat, much earlier Intel USB 3.0 driver packages, Windows Small Business Server 2008 was not originally represented as supported, but Windows 7 and Windows Server 2008 R2 were. Later versions of the Intel USB 3.0 driver were documented by Intel to support Windows Small Business Server 2008. Thank you 2008WindowsVista for your report. Did you try your test on the x86-64 version of Windows Vista? It would seem that the driver's documentation might be erroneous with regards to Windows Small Business Server 2008 support or Windows Small Business Server 2008 may provide something different that allow it to be compatible. If Windows Small Business Server 2008 is truly compatible, perhaps the changes or differences between Windows Vista and Windows Small Business Server 2008 can be applied to Windows Vista (then I would think the driver should install).
    1 point
  30. The information regarding the AMD Catalyst 15.6 Beta Drivers package I was able to find is available: https://web.archive.org/web/20150629000845/http://support.amd.com/en-us/kb-articles/Pages/latest-catalyst-windows-beta.aspx The AMD Catalyst 15.6 Beta Drivers package downloads from AMD have apparently been made unavailable. I download what appear to be the AMD Catalyst 15.6 Beta Drivers package from the links referenced in: http://forums.videocardz.com/topic/1243-amd-catalyst-156-beta/ The AMD Catalyst 15.6 Beta driver package does not contain recent (since about year 2011) AMD motherboard chipset drivers. I was wondering I the latest Windows 7 AMD chipset drivers should be used on Windows Vista or another version or versions.
    1 point
  31. Apparently, Intel provides actual USB 3.0 drivers, but in USB driver specific packages. The drivers are supposedly available for (given information from the Read Me files): Windows 7 Windows Server 2008 R2 Operating System Windows Small Business Server 2008 Although, Windows Vista is not is officially supported, Windows Small Business Server 2008 (only available as x86-64 operating system) is given as supported. My understanding about Windows Small Business Server 2008 is that it is based on Windows Server 2008, which shares are code-base with Windows Vista. Perhaps the Intel USB 3.0 drivers may be installed on Windows Vista (at least the x84-64 version). I do not have Windows Vista installed, myself, and it would be difficult for me to test this. The latest Intel USB 3.0 driver package for Windows Small Business Server 2008 appears to be version 4.0.4.51: https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=22824
    1 point
  32. That´s not quite true. In fact, all chipsets later than Z68 and X79 have USB 3.0, and Intel never released USB 3.0 drivers for XP or Vista, so support for those chipsets is incomplete.
    1 point
  33. Intel chipsets through Z87 and Intel C226 are officially supported by Intel for Windows Vista and Windows XP. The last version of the Intel chipset driver installation utility for Windows XP is version 9.4.0.1027 which can be found: https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23061 (Disregard operating system list specified on the page; it is erroneous. View the Read Me file for correct operating system listing) The Intel chipset configuration utility of version 9.4.0.1027, officially supports the following operating systems: Microsoft Windows 2000 Microsoft Windows XP Microsoft Windows XP Professional x64 Microsoft Windows Vista Microsoft Windows Vista x64 Microsoft Windows 7 Microsoft Windows 7 x64 Microsoft Windows Server 2008 R2 Microsoft Windows Server 2008 R2 x64 Microsoft Windows 8 Microsoft Windows 8 x64 Microsoft Windows Server 2012 Microsoft Windows Server 2012 x64 Microsoft Windows 8.1 Microsoft Windows 8.1 x64 Microsoft Windows Server 2012 R2 Microsoft Windows Server 2012 R2 x64 The 9.4.0.1027 version of the Intel chipset configuration utility is supposed to also support Windows Vista. Later version of the Intel Chip Driver installation software do not support Windows XP and do not officially support Windows Vista, but they do Windows 7. Perhaps the Windows 7 chipset driver INFs are also applicable to Windows Vista? My understanding is that the Intel Chipset driver installation utilities do not actually install driver files on Windows; the driver files are included with the Windows or its updates. The Intel Driver installation utility selects and configures the drivers and defines their parameters.
    1 point
  34. As far as I know, Ivy Bridge-E supports Vista completely, as X79 boards have Vista drivers, due to them having to provide support for Sandy Bridge as well. Older Sandy chipsets for motherboards like H61 may have been updated to keep Ivy support, thus you will definitely get Vista drivers in them as well. But on newer chipsets released for both platforms like Z77, Windows 7 and above may be actually required (or XP too, but Vista can be out of the question).
    1 point
  35. I'm not sure about 15.6, I have looked all over Google and cannot find it. However, I did manage to find 15.4 here which also works in Vista: http://support.amd.com/en-us/kb-articles/Pages/amd-catalyst-15.4.1-beta.aspx I would also ask on smeezekitty's "omega on Vista" thread, as someone there may have it (15.6) archived.
    1 point
  36. I know. That would be amazing to have, but looking at Vista's poor reputation and low usage, I doubt anyone here would even care about doing it. Although I do have Windows 7 looking very much like Vista which is good, but it's not the same as the real deal.
    1 point
  37. We REALLY need a KernelEx for Vista... I mean, it's in the same predicament as Windows 2000! Heck, I bet it would be easier to develop than what we have for Windows 2000, because Vista has most of the components 7 has (with the Platform Update and all).
    1 point
  38. You'd think that in order to qualify for the "legacy" label, Vista would have to be unsupported by Microsoft completely first. But I guess considering how the third party support of Vista has fallen like it has, it doesn't really make much of a difference.
    1 point
  39. Well, I installed 7 again yesterday, but due to a mistake I did to the OS, I had to reinstall again and got Vista SP1 again. Seriously, it runs better than any other OS in here, even those it was supposed to run great on, like 7 and 8. Just, I'd like to get the Ivy USB 3 drivers working in NT 6.0, at least for now. Vista still wins. If only it would get lots of community support, this would help it stay on the top for a while.
    1 point
  40. Speaking of Vista's planned obsolescence, Vista's forum here, at MSFN, just got demoted to the Older Windows OS category... How the great have fallen :/
    1 point
  41. I will add X99 after I see someone testing it with Vista with no problems. The issue is also existent with Z97, not just H97: http://www.vistax64.com/general-discussion/304098-logon-process-initialization-failure-vista-ultimate-x64.html That's most probably affecting your own chipset (H97) though, not verified if it exists in other LGA 1150 boards too, but X99 isn't affected by the issue at all. You could just add X99 for now for the high end i7s and Xeons that are LGA 2011-v3, and search on other 1150 boards that have the issue existent in 7 at least. If they do, then those who want Haswell and Vista should go with X99. If they don't, then H97 is the only chipset that gets affected.
    1 point
  42. That's most probably affecting your own chipset (H97) though, not verified if it exists in other LGA 1150 boards too, but X99 isn't affected by the issue at all. You could just add X99 for now for the high end i7s and Xeons that are LGA 2011-v3, and search on other 1150 boards that have the issue existent in 7 at least. If they do, then those who want Haswell and Vista should go with X99. If they don't, then H97 is the only chipset that gets affected.
    1 point
  43. But there is a software timing issue with Windows Vista and haswell that causes it to not boot up half the time, and some services fail to start. Unless Microsoft or intel release a hotfix, I cannot guarantee that Vista will work properly with haswell. I will add EVGA as an exception for Vista, but again, whether or not that timing bug will appear I cannot tell. It could only affect H97 (which is what I tested Vista on), but I doubt it. Specific errors you'll see: Just before the Startup Orb animation appears, you'll get an error that says "Interactive Logon Process Initialization has failed. Consult the event log for more details". Upon clicking Ok, sometimes Windows will proceed with the boot up process, and sometimes it won't. Usually, when it does, after you logon, some services fail to start. The one I saw most often was Windows Defender, and sometimes Windows Audio. If you experience any of these problems, the only solution as of right now is to upgrade to Windows 7 SP1 or later, where the problem is non-existent.
    1 point
  44. I even found some Z97 motherboard drivers for Vista, by EVGA again: http://prntscr.com/aafrnt You can't say Haswell completely doesn't support it, since it's only some specific companies and chipsets (and mostly chipsets) that don't. Even so, probably unofficial support is in those 7 drivers for such boards from other companies like MSI too.
    1 point
  45. For some reason Chrome feels better when browsing websites, hence why I still use it in Vista, though Firefox is the one that will still support it... YouTube, for example, runs much better in Chrome in here than Firefox, but there won't be any other option than upgrade to 7/2008 R2, or stay with kinda "degraded in performance" software or unsupported ones.
    1 point
  46. Check X99 for Haswell processors though, there is still some Vista driver support for X99 chipsets and motherboards (at least EVGA does support it completely, maybe not USB 3.0/3.1 drivers).
    1 point
  47. I'll assume you meant to say CS6. Anyway, this is one of those weird instances where XP and Windows 7 are supported, but Vista is ignored. It isn't that big of a deal though, the only thing Vista users miss out on is technical support from Adobe if you have a problem with the software. The CS6 software itself will still install and run perfectly fine in Vista.
    1 point
  48. using Adobe photoshop CS8 in Xp so it should work in Vista
    1 point
  49. Hi everybody is there a way to build an unattended system with updates for all version of Windows vista please? thanks
    1 point
×
×
  • Create New...