Jump to content

WalksInSilence

Member
  • Content Count

    87
  • Joined

  • Last visited

  • Days Won

    1
  • Donations

    $0.00 

WalksInSilence last won the day on February 14 2020

WalksInSilence had the most liked content!

Community Reputation

18 Good

About WalksInSilence

Profile Information

  • OS
    Windows 7 x64

Recent Profile Visitors

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

  1. I do not like Win7's version of Spider Solitaire at all so I rarely use it. I installed WinXPs version and also the XP pinball game too. Easily found and copied from a XP installation. Personally I'd focus on the positives of Win7, the things I have come to appreciate which I did not think I would like or use initially. Too many to list but ones that immediately come to mind:- 1). The Show Desktop button on the far right edge of the taskbar taking you back to the desktop quickly. Hover to view the desktop or click to go and when done click to return to where you were. 2). The pr
  2. Not sure if this is relevant here as I'm using a much older version of VMWare Player but this week, for the first time in months, I had a Windows update prompt which was actually a new driver version for it. Worth checking your Windows updates to see if that driver is available to you.
  3. It isn't a dual boot set up in the usual way. Each OS was separately installed to their respective HDDs by which I mean entirely separately. The other OS's boot drive was physically disconnected during the install so in effect I had two separate PCs in one case. Win7 set as primary on a SSD and manually selecting the WinXP boot drive on the 160GB HDD (F12) when wanted. That was the theory at least; I had read that this method of setting up a dual boot might solve the issue of WinXP deleting Win7 Restore Points, It didn't. It also didn't work out quite as neatly as I hoped either due
  4. I've decided to use one of the more obvious solutions mentioned: delete the 320GB clone HDD 'Y' partition and convert the whole of the, now unallocated, free space to a simple volume and copy the contents from the Y partition of the original 160GB HDD. Whilst I don't like not understanding it and how to fix whatever the problem was either with the way it was cloned or the original partitioning I was hoping it would be relatively easy. I just want the new 320GB HDD to behave like the old one. It seems to me at this point it makes more sense to go for a simple solution which I can't think o
  5. Sorry but I'm not understanding the significance of the MBR? That, I thought, only applies to physical disks with an OS not other partitions. The WinXP OS on X is largely an irrelevance now. I've not booted it for at least a 18 months because it is a pain to do so. No working SATA Controller Driver so I have to use the BIOS to swap to legacy IDE then reboot, select the XP boot partition. Then do the reverse to get Win7 back again also incidentally losing any Win7 restore points in the process too. I now use Win7 XPMode on a VM instead if I need to run some legacy software - far simpl
  6. I tried to make that clear - at no time did I use WinXP to partition the HDD after the initial OS install. The later partitioning to X and Y were all done using Win7 64bit Windows Disk Management tools. Here's the current situation:- 1. Original 160GB HDD still currently installed. 2. Sector by sector clone on the 320GB HDD currently in external housing. S and T rather than X and Y. 3. Right clicking on the T drive I do get the Expand option but with this message:- 4. If I click 'Yes' I then get this:- I'll try another partitioning tool if
  7. Thanks: interesting thoughts. I've checked using Windows Disk Management and indeed the Y drive is shown as a Logical Volume. I'm on another PC at present so I'll have to check later the original, still installed 160GB HDD Y partition, to see what that is reported as being. Would the cloning/method (sector by sector) used for the 320GB have created this problem or the original partitioning of the 160GB HDD? As I recall I installed the WinXP OS on that previously virgin 160GB HDD and then later, once the PC was up and running with its primary Win7 64bit OS and using that I then r
  8. As a secondary HDD I installed a WD 160GB alongside the SSD (Win 7 64bit Primary) and Seagate 1TB main storage HDD. The 160GB HDD has a full Windows XP 32bit OS installation on the first partition (Drive X 40GB) mirroring my old XP laptop and set up for manual dual boot. The whole of the rest of the 160GB HDD, 120GB was partitioned as Drive Y and mainly used for data backup of the XP drive and a later installed XP VM on the SSD. Everything NTFS as you would expect. I've been running out of space on the Y drive so as I have a spare WD 320GB in an external USB housing I decided to clo
  9. With Windows 7 you can elect to receive notification of updates but choose when to install them yourself. I think that's a better solution. You still have to watch for telemetry gathering tools being sneaked onto your system which can cause the sort of high CPU/memory usage described. The "Trusted Modules Installer" running once, usually just at first reboot after the updates, often pushes the system use very high for several minutes too. High system usage problems can also be caused by some form of corruption and using a command prompt to stop the update service then restarting it m
  10. I'm not sure what the problem might be although it obviously concerns that igdumd64.dll. It is apparently an Intel Graphics Driver DLL - do you have problems launching any of the other MS Win7 games? If so it might be problem with that DLL or the driver itself which will have to be addressed. I can't give any advice on that. The games which come with WIn7 are located in C:\Program Files > Microsoft Games so I'd go to that folder and click on the Solitaire EXE to see if it works from there. If it does then its probably a shortcut/start menu (Games) shortcut issue and you just need to re
  11. The easiest solution is to run Win7 on a virtual machine. It should resolve most if not all of the driver or other problems.
  12. 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 w
  13. 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.
  14. 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 resto
  15. 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
×
×
  • Create New...