Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


WalksInSilence

Member
  • Content Count

    77
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    1

WalksInSilence last won the day on February 14

WalksInSilence had the most liked content!

Community Reputation

18 Good

About WalksInSilence

Profile Information

  • OS
    Windows 7 x64
  • Country

Flags

  • Country Flag

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The easiest solution is to run Win7 on a virtual machine. It should resolve most if not all of the driver or other problems.
  2. You definitely do need to check your RAM. A loss of speed like that sounds like a module may have failed or something is hogging the memory as others here have suggested. An anti-virus program perhaps (AVAST?). When we were forced to dump the ideal for this purpose MSE with XP installations I had to find a suitable working alternative for XP on a VM. I settled for a claimed lightweight one but I immediately noticed XP on the VM was much slower to boot and things like browsers and even some system tools would launch, initially, with a significant delay. Shutdown was also delayed. I would not use a recent FF version with XP anyway but as somebody who had a Dell XP laptop with limited RAM support (max 1GB in two 516MB modules but would sometimes work with 2x1GB ones) I know just how much how much of an effect losing one stick can have. With XP on the VM with 1GB of allocated RAM it works well with a pre-v57 FF version although I very rarely use it online now anyway. However the VM is on a SSD so that probably helps. Anything running off a HDD is going to be slower initially but 10 minutes to launch FF - there's something unnatural going on.
  3. My suggestion would be to install XP on a virtual machine. If the laptop has plenty of RAM and decent enough CPU it should be doable.
  4. Creating a backup image was what I meant and programs like EaseUS Todo allow you to do that for individual folders without having to go through all the permissions hoops required just to be able to copy the SVI file folder. But, as said, I've never had the guts to try importing that back in full or just adding the backed up restore points from it. But if it did work you could create a scheduled task for backing up the SVI to run at boot or every three days. But I really do not know if any of this is possible or practical - just floating the possibility. For me manually creating restore points seems like the best solution but I agree it should be possible to automate that to do as you want.
  5. I was going to say something about the frequency too but that does depended on how much space you've allocated to restore points. Having a smallish 120GB SSD primary drive I reserve about 8% which in practice means about 10GB of space and 7 or 8 restore points. I put in a manual restore point every week and delete those if more than a month old but only if I've had no problem. That saved me recently; I had this weird issue I won't bore you with but I couldn't find a solution and the web site of the program involved is now just an archive with no mention of similar issues. I worked my way back through the 6 restore points I had and it was only using the last one, six weeks old, that fixed whatever the problem was. If I'd been creating restore points every three days I'd have nothing but month old restore points and how I would have fixed the problem I've no idea as I'd tried every other method I could think of to no effect. What I really wish was that there was a restore point save option either provided or as a third party tool. Whilst you can backup the Windows System Volume Information folder which contains, amongst other things, the restore points, I've never had the confidence to risk testing if they actually work months later. Instead I content myself backing up the registry once a month and hope I never have to use it. So far so good.
  6. Just looked into this a bit more and I found this :- "Windows controls the creation of automatic restore points based on a frequency setting to help limit the number of restore points that get saved. By default, Windows won’t create an automatic restore point if another restore point has been created in the last 24 hours." That I did not know. Could it be the explanation? Apparently changing the Registry's Restore Point frequency setting to off may allow you to do what you want. The quote is from 'The How To Geek' web site which also details how to do that. I've always found it a good source of advice on a lot of niche subjects like this:- https://www.howtogeek.com/278388/how-to-make-windows-automatically-create-a-system-restore-point-at-startup/
  7. I use the 'Check for updates but let me choose...............etc" and do have that recommended updates box ticked too. Consequently I can't blame anything other than my own casualness for downloading and installing it on the PC concerned.
  8. Unusually today there was a notification in my system tray about an important Windows update. It turned out to be Edge, absentmindedly I forgot I don't have Edge installed on the particular PC I was using and clicked to install the 'update'. All I can say is I'm very thankful for System Restore. The bloody arrogant thing installed Edge and actually launched on top of my desktop after boot and with, initially, no way out, I used Task Manager to kill it. With System Restore and other tools I've since removed as much evidence that it was on the machine as I've been able to find and hidden the update when it was 'offered' again. The 'update' is still shown as successfully installed under Updates but if you go to installed updates it is not there so, presumably, that just means it was successfully installed at the time and that's all. In short - when offered an 'important' update check before you install it.
  9. My advice is do not rely on Windows to make restore points. Do it yourself before installing new software and/or on a weekly basis. I do that as part of my regular PC maintenance schedule. The system created ones seem to be made rather randomly whatever settings you use but I think that if you check there are by default multiple triggers. On my PC, which I do not remember changing from default, it is set to create new ones on start up and at 0.00 daily but only if this criteria applies:- "By default, Windows will automatically create system restore point when new software is installed*, when new Windows updates installed, and when a driver is installed. Besides, Windows 7 will create a system restore point automatically if no other restore points exist in 7 days." Task Scheduler checks at those specified times but other conditions apply too so check under the Conditions tab what those are. My guess is that this is the 'problem' - if the PC is not idle at those times a restore point won't be create then either. The one that does seem to apply irrespective of the other triggers is the >7 day one. There is also the possibility you have not assigned enough space for the restore points. Key restore points can be 2+GB and most are around 1GB so if you've only allocated say 6GB you're only going to have 3 or 4 restore points available at any time before they're deleted. The default Windows 7 allocated space is 5% so if you're using a relative small primary drive SSD (120GB or less) that 5% so it could easily be you just have 6GB for restore points. I use 10% and currently have 5 restore points, none of them system created. * I do not think that includes portable software and it does not include updates to already installed programs. That's why I put in a manual restore point before updating anything.
  10. So it is possible to update Win7 itself using the MS catalogue - I did not realise that could still be done. I've never used automatic updates with Win7 and I'd assumed all I'd get from now on was notifications about non-system updates like MS Net Framework etc.
  11. Yes but we're past Win7 EOL and MS Support. That was supposed to end on 14th January with the final rollup. The black wallpaper problem some people have experienced, apparently caused by something in that final rollup forced MS to issue a patch, post support cut off date. You could get the patch as an optional download but at some point they started offering a new rollup Preview instead with the support pages stating:- "This non-security update includes improvements and fixes that were a part of KB4534310* (released January 14, 2020) and also includes these new quality improvements as a preview of the next Monthly Rollup update." What next Monthly Rollup update? I'm not signed up for the Win7 ESR so why am I being offered a Preview of something I'm not going to get? * I installed that almost a month ago, and it had issues for me but not the black wallpaper one so I did not install the later patch when it was first offered as an optional update. The Preview makes it appear they may actually be going to issue a post EOL Monthly Rollup for (all?) WIn7 machines.
  12. Yes, that is one of my pet general forum use dislikes: when somebody asks a question, gets help and then later posts some variation on:- without actually explaining exactly how they resolved the problem. So many times you look for answer to a particular question online and find a thread in some long dead or now barely used forum which is about just what you wanted to know and the thread is abruptly ended by a post like that. Frustrating and a wee bit selfish.
  13. I think driver support on more recent systems won't be an issue at present but if somebody comes here in the not too distant future wanting to do the same thing on a then contemporary PC it could be. I had problems with Windows XP in 2016 which I originally wanted to work in dual boot with Win7. It was actually the lack of a specific MB driver required to use XP with SATA HDDs, the SATA Controller driver, that caused the biggest trouble. When I bought the MB the listing said it was XP compatible. However when I finally started building the PC I discovered too late the version I had only supported Win7 and 8. By luck I guess all the other important drivers did still work with XP, it was just that SATA Controller one that did not. I eventually found a generic XP SATA Controller driver for the MB and managed to install it without a full XP re-install. Under XP the Device Manager says it is working but it is not. I still have to swap to legacy IDE mode in the BIOS/UEFI then reboot and choose the XP OS boot drive to get it to launch and go through the reverse process to get back to Win7. Utter pain and why I now use XP on a VM instead. That sort of thing and the undoubted inexorable increase in the ending of important software support for Win7 will, slowly, reduce its use as a primary OS and its overall viability.
  14. Interestingly there is an "Optional" MS provided update for Win7 users this month: apparently the final Monthly Rollup introduced an annoying bug on some systems which renders the wallpaper you're using as all black. Hasn't affected either of my two Win7 PCs; one uses a custom wallpaper and the other a MS wallpaper that came included with Win7 so no point in installing the update. Anyone here experienced this bug? EDIT A bit weird, I'm now being offered as an optional update:- 2020-01 Preview of Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4539601) Download size: 314.4 MB You may need to restart your computer for this update to take effect. Update type: Optional This apparently includes the stuff that was in the 14th January KB4534310 'final' Win7 monthly rollup which I do have installed but also includes the black wallpaper fix too. Whether MS are going to release the whole Preview content as an additional post EOL update or revert back to just providing the optional wallpaper fix will be interesting to see. But why offer the full Preview to those without the extended licence who have KB4534310 installed if they are only going to get the wall paper fix?
  15. Google and you'll find find plenty of advice for such circumstances. Apparently if you have not set an Administrator password you can start in Safe Mode and try logging on with the Administration password field blank. Safe Mode with Command Prompt offers another route too.
×
×
  • Create New...