Shane and Clam
Thank you for taking the time to read and comment on my problem. I thought I'd update you on what has transpired since.
What a weekend.
Despite the comment in my last post I was not discouraged but I did some more calculations and came to the conclusion that at 16 hours a day SP1 would take 3 to 4 weeks to finish. It wasn't a difficult decision to abort and try running it again. I started it on Saturday afternoon just before a thunder storm started and it seemed to be running faster; an hour in, we had a power cut. Result: 49922 didn't know what build it was, so I had to re-install 46957 and patch back to 49922 before restarting SP1. Again it seemed faster but by the time it got to the .ja files I realised if it was faster, it wasn't by much and I aborted again.
On Sunday morning, taking on board Clam's comment that it might be a slow hard-drive, I put 49922_to_61388.exe on a memory stick and tried again. By the time I had to leave to see the final Monty Python show it was struggling to complete the first .ja file and I gave up.
Monday, I installed 46957 on another drive, patched and started SP1 from a high speed SD card. Better again, but when it got to the .ja files it was putting them on the drive I had used originally!?!
End of story, soon.
Tuesday: last try before ordering TS12 with SP1 pre-installed. Another new install (I don't know how many TS12s I have now), this time on C: drive, and run SP1 from SD card. Eureka!! The progress bar really does move. First .ja file completed in 22 minutes - more than had been accomplished previously in 24 hours. Total update time 2 hours and 29 minutes.
I don't know if this was a world record, but it feels like the sort of elation you would get when it was!
I've had a short trial run and it seems to be OK, so now for SEN City.
Phew.
Thank you for taking the time to read and comment on my problem. I thought I'd update you on what has transpired since.
What a weekend.
Despite the comment in my last post I was not discouraged but I did some more calculations and came to the conclusion that at 16 hours a day SP1 would take 3 to 4 weeks to finish. It wasn't a difficult decision to abort and try running it again. I started it on Saturday afternoon just before a thunder storm started and it seemed to be running faster; an hour in, we had a power cut. Result: 49922 didn't know what build it was, so I had to re-install 46957 and patch back to 49922 before restarting SP1. Again it seemed faster but by the time it got to the .ja files I realised if it was faster, it wasn't by much and I aborted again.
On Sunday morning, taking on board Clam's comment that it might be a slow hard-drive, I put 49922_to_61388.exe on a memory stick and tried again. By the time I had to leave to see the final Monty Python show it was struggling to complete the first .ja file and I gave up.
Monday, I installed 46957 on another drive, patched and started SP1 from a high speed SD card. Better again, but when it got to the .ja files it was putting them on the drive I had used originally!?!
End of story, soon.
Tuesday: last try before ordering TS12 with SP1 pre-installed. Another new install (I don't know how many TS12s I have now), this time on C: drive, and run SP1 from SD card. Eureka!! The progress bar really does move. First .ja file completed in 22 minutes - more than had been accomplished previously in 24 hours. Total update time 2 hours and 29 minutes.
I don't know if this was a world record, but it feels like the sort of elation you would get when it was!
I've had a short trial run and it seems to be OK, so now for SEN City.
Phew.