So I got it back to my place and restored the machine with an Acronis backup
to the way it was when I sold it to them, then created a new partition and
put the backup file on it and gave them an Acronis boot CD... also put the
machines driver files on this partition as the disc I gave them did not
work, something to do with the burning process I think ;(
Anyhow I download the latest 64bit drivers for the webcam and that installed
successfully, gave them a ring for them to pick it up. They turned up on a
motorbike! My instincts said that is not a good idea when travelling home
with a PC attached, so now I am praying it makes in home in one piece what
with the bumps in the road and all.
Fingers crossed, otherwise I will have to refund them.
You mean to say that you didn't point out to them (the bleedin'
obvious) that (whatever) the warranty (is that you've provided) doesn't
cover transit damage?
Provided the pillion rests the box across his knees (rather than strap
it directly to the bike) and the rider takes it easy and avoids any
major potholes, a PC can be safely transported this way. The trouble is,
you'll never know if they succeeded in this mission (but fingers crossed
that they do ;-).
--
Regards, John.
Please remove the "ohggcyht" before replying.
The address has been munged to reject Spam-bots.
Well I have not heard from them since they collected it at around 15:00 so
it looks like its made it home safely.
Well I had a call today whilst I was on a day trip in France the original
problem has happened again, from what I saw of it - it suddenly fails to
boot with a winload error. On Saturday I was able to get the machine up and
running again by restoring an Acronis image, so from what little I know of
the problem it now seems like a hardware problem. It does not seem to have
anything to do with a webcam drivers as first thought.
I wonder now if a failing piece of hardware like the hard drive could
exhibit this sort of behaviour, machine works fine from an image restore but
then fails to boot after a day or two... anyways I have arranged for him to
bring the machine back alongwith everything I gave him for a refund.
Then I will get a chance to use the machine for a couple of days to see if
the problem occurs again and figure out whether its software or hardware
problem. I hope the former obviously.
I have been searching google for an answer to this problem and I believe
it has something to do with the fact I used Acronis True Image to
restore the drive... apparently you have to run BCedit before imaging
the drive otherwise you will end up getting the winload error.
So what I am going to do now when I get the machine back is a fresh
install that should fix the problem.
I just had the machine back, this time it has not crashed with a winload
error they were just having problems after Vista Service Pack 2. They
were not happy with the machine and could not get along with it so they
have had their money back. I use it with Windows 7 and have had no
problems... oh well its one of those times when its easier just to keep
the machine then to have the � 300
>harikeo wrote:
>>>
>>> So what I am going to do now when I get the machine back is a fresh
>>> install that should fix the problem.
>> I've restored Vista and Win7 using Acronis and haven't had this issue.
>> What editing in BCedit is supposed to be done?
Dredging from memory, this is only an issue with machines that have
been cloned and will be on the same Active Directory service. Not a
worry for home boxes, really.
>I just had the machine back, this time it has not crashed with a winload
>error they were just having problems after Vista Service Pack 2. They
>were not happy with the machine and could not get along with it so they
>have had their money back. I use it with Windows 7 and have had no
>problems... oh well its one of those times when its easier just to keep
>the machine then to have the � 300
Or flog it to a non-numpty! Better luck next time.
Cheers - Jaimie
--
"The only way to comprehend what mathematicians mean by infinity is
to contemplate the extent of human stupidity." -- Voltaire
I re-sold it to the same people with Windows 7 (and charged them extra for
Windows 7) hopefully now there will be no further problems as it seemed the
problems started after Vista Service Pack 2 which is unusual and I never ran
the machine with SP2 nor even SP1 and I only recently upgraded it to Windows
7.