What does error code 4SNS/1/40000001: TN1D- -1.000 mean???

Thanks, Kappy!!

I need to have a computer while my MBP-13" is being repaired - and I can't imagine this taking less than 1 week - maybe a month.

So I'm wondering if I can use migration assistant to move all my "stuff" from my MPB-13" (May 2010) to my PowerBook G4-12" (Spring 2005-running 10.5.8 Leopard - PowerPC)???

If so, any special instructions?

If not - then what about transferring from a BackUp hard drive to the PBG4-12" - can SuperDuper! just transfer the files and not the OS?

Thanks for any comments on the best way to do this. BTW-- For the past 11 hours my MBP has been running perfectly via an Iomega HD "SuperDuper!" Backup from prior to the Security UpDate-2010-006. Perfectly - maybe faster than before!! - no freezes, no problems.

Looking forward to your reply,

Steve
Sunday 10 October 2010

OK I understand - and am moving now to my PBG4. But would this "heat sensor" be causing my MBP-13" to have the cursor freeze every 1 to 25 minutes? Or to suddenly stop working at night and when I wake in the morning--- only way to restart in each case is with the POWER BUTTON.

And if so, then why did my MBP just run nearly 12 hours perfectly via a cloned system (but prior to Security UpDate 2010-006) located on an Iomega 500 gb external FW800 HD? I'm wondering if this is a software problem - because even when I tried to run on another full BackUP - (it was a backup AFTER the security update 2010-006) and it froze up too. (So if it was the internal HD then why did the external cause a problem?? - And why is the other, current Iomega pre-security update 2010-006 working GREAT?!?!)

I can imagine that there are 2 problems here - one the sensor (which may even have been defective prior to my FREEZE problem); and the other being another problem (maybe software and just maybe due to this Security Update 2010-006). These problems may be independent of one another and having different effects on things. In the past 12 hours - I don't think the sensor problem has caused any problems - so is it the cause of the freezes???

Any and all comments really, truly appreciated and will be put into effect. Glad I kept that PBG4 (I'm keeping my 2002 Volvo S60, too - even if I get a new one - that 2002 is staying in a big plastic bag...

Thanks!

Best regards,

Steve Schulte
Sunday 10 October 2010

Kappy - I truly appreciate your feedback! Here's the latest:

1. I ran my MacBook from an external drive which had been saved prior to Apple Security Update 2010-006 and it ran nearly 24 hours without a single problem.

2. I then booted into the internal drive with the security update and in 2 minutes a FREEZE - restarted and within 5 minutes a FREEZE.

3. I'm now back with the external - trying to transfer things over etc.

4. I re-ran the hardware test 6 times: The first time it said NO PROBLEMS, then the second time that same alert 4SNS/1/40000001: TNID- -1.000 (which you indicated was a temperature sensor problem). The third time "No Problems" and the 4th, 5th and 6th times again the Alert 4SNS/1/40000001: TNID- -1.000. So it seems something is at best a marginal problem; at worse a potential overheat situation.

But I still do not think the FREEZE problem is related to the sensor. I have a telcon apt with APPLE in about 12 hours and will certainly go with their recommendations - but would like to hear anything more from you (or others) concerning this issue - and especially the reason why a "security update" might cause this freezing-up. (Especially since the MBP-13" ran at least a week with this security update installed without a problem!)

Thanks again--

Steve
Monday 11 October 2010

I called Apple (well scheduled and they called right on time!)-- basically a very nice guy, but all he did was have me start from the Install Disk and verify the disk (OK) and repair permissions. (I'd done this earlier).

The fix here was going back to a copy of my system (full SuperDuper! clone) that was prior to Security Update 2010-006. Somehow that conflicts with something I have - and I have everything known to man on this Mac- from DragThing (very good programing) to Haxies to menubar items and much much more. (How can anyone use a Mac without ASM and DT???)

By copying the pre-security update 2010-006 to my MBP I've run 2 hours without a problem (24 hours yesterday via the external copy).

As to the Hardware check - after the telcon with Apple (I gave him that number but it didn't mean anything to him - I don't think these first call guys are engineers, just running you thru the basics and when that checked-out, they check-out). OK so I re-ran the hardware check FIVE TIMES and each time the report is: No Trouble Found. So the security update 2010-006 caused a bunch of BIG problems.

Now if I am back on these discussions in 24 hours saying I've got problems then it is egg on my face - but hopefully not- since I don't know what else to do other than a full erase of the HD and install everything by hand - that would take me 60 hours if I didn't sleep.......

Thanks so much and how to get the word out there NOT TO DOWNLOAD SECURITY UPDATE 2010-006???

Regards,

Steve - time for dinner!

Just so you know - the Apple Guy didn't even broach the issue of that error code number - frankly I don't think he had a clue about it--

It was your post that indicated to me what the code meant - I've had zero telephone Apple contact in the past 21 years other than sales guys and the guy yesterday. (Been to a number of Apple stores around the world - neat! Good help generally- can't believe they haven't made DragThing a part of the OS-- most don't know it!)

ANYway - I really appreciate all the assistance here (I had to google IMHO - living in Belgium I've not come across that- neat!). I am getting a backup Mac organized before sending the MBP to repair.

Thanks again,

Steve
Tuesday 12 October 2010

I am reactivating here because I now think I have a HARDWARE PROBLEM!!

Kappy - I remember in about 1994 I was in Cornwall at had to have my Hard Drive on my PB180 recovered - cost me about $100 and likely it was an 80 -- but that would have been 80 mb, not gb!!

ANYway- I think my MacBook Pro-13" problem is definitely Hardware- because after running for 24+ hours via an external 500 gb Iomega HD (FW800)- I then copy that full system to my internal 500 GB MBP-13" drive and although it works for 16 hours - it now is freezing every 5 minutes. I'm back to the Iomega now - and it is doing great! If I'd been on the internal - it would have frozen well before this...

So I will ask for a repair authorization when Apple calls me Wednesday at 1pm EST - I guess I could install a new HD myself - it is likely the problem because if it were anything else, then why doesn't the boot via the iomega 500 gb HD freeze?

More soon - and thanks again for your "RIGHT ON" comments --

Best regards,

Steve Schulte
Tuesday 12 October 2010
________________________________________________________________

I did and after 3 weeks it is back - not freezing-up like it did before, but the menu drop-downs are NOT highlighting and the DOCK magnification is not sliding just freezes at one point...

...so not sure if replacing the motherboard did the trick or not!

Best regards,

Steve Schulte
Wednesday 10 November 2010
________________________________________________________________