Re: OT: some questions for our Apple + Parallels Users

[Harry Binswanger hb@xxxxxxxx]

Jordan,


Sorry to be so long in replying. It's entirely self-contained. Takes 1 to
2 min to run. Probably won't fix things, but nothing to lose. the
/scannow switch tells it to replace any corrupted files (I think from its
.cab files, or whatever way it now stores system file originals).



You just go to the Run command (Winkey-R) type in sfc /scannow and hit
enter. No biggie.


Regards,

Harry


Harry,


Regarding that scan you suggested: is it entirely self-contained, or do
you need to be connected to the internet for it to function ?  Does
it take a fairly long time to run ?  (Say, on a middling Core-2 Duo,
1 GB. hard drive, 4 megs of RAM -- of which XP will only see 3.2) 



I would be trying that on my next visit . . .  presuming that it
would not tie up the machine for hours.  If that was the case, this
may have to wait for some more opportune timing.




   Jordan




From: Harry Binswanger


To: xywrite@xxxxxxxx

Sent: Thursday, November 16, 2017 6:54 AM

Subject: Re: OT: some questions for our Apple + Parallels
Users



Certainly OS X vs. Win is endlessly debatable. I agree with Carl that,


unless she's already acclimated to the Apple environment, there's less of
a

learning curve in going from XP to Win 7 (probably even to Win 10) than
in

going to OS X.


But here's a new thought: why not fix her XP software? If all the ports


have failed (yet work as hardware, proven by your test) there must be
some

one point of failure. Some Googling would probably turn up the
problem.


In fact, have you tried running:


sfc /scannow


-- that alone could completely solve the port problem (ever the optimist,
I

am).


Regards,

Harry





https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon Virus-free.
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link