Strange target mode behavior

I've found when moving large files back and forth that you have to be careful about how you delete them. I use the iBook as a DVR, feeding the signal through a Dazzle, and then transfer the iMovie file to my Power Mac.
However, if you then move the file off the desktop of the iBook and into the trash on the Power Mac, you have to empty the trash while the iBook is still connected in target mode or the iBook will think the disk space (~12gb for an hour of video) is still occupied, even though that iMovie file is gone from the iBook.
PowerMac G5 dual 2.5GHz, 1.5GB; iBook G4 1.33GHz, 1GB Mac OS X (10.4.9) 200GB&500GB LaCie FW HD, 16x LaCie LightScribe

When the iBook is in FireWire Target Disk mode, items on its hard disk that are moved to the Trash are stored in a folder with a path along the lines of /.Trashes/501/. In normal usage, the iBook hard disk's trash is considered to be inside the home folder of the logged in account unless that folder has been moved off the startup partition. Therefore, items moved to the Trash in one usage mode will not be seen in the Trash in the other, but they can be moved back and forth by using the Go to Folder command in the Finder's Go menu, providing the first path, and then dragging the items. The 501 in the path will always be a number, and is normally either 501 or slightly above 501.
(22719)

Similar Messages

Strange multiply blend mode behavior.

Hi,
i am working on a project and i am surprised to find a strange multiply blend mode behavior.
When i open a new blank document to try again the multiply behavior, all seems to work well.
Is it possible that the document i am working on became corrupted ?
I work on a 2012 Macbook Pro Retina 15", Mac OS X 10.8.5 and Photoshop CC 14.1.2.
This is what i see :
- Normal blen mode.
- Multiply blend mode.
Thank you for the help
Regards.

Ok, i found the solution by chance but it raises new questions.
I stayed on the same document (because i thought that it could be corrupted) but made all the layers invisibles.
I created a first Color Fill layer filled with 50% grey (as background) and just above an other Color Fill layer filled with white (as white paint).
So i masked all the white color fill layer and just made 2 stokes.
In normal mode, i got this which is normal.
So, i chose the multiply blend mode and got this (which is again normal).
P.S. : i am writing the end of the post in a second post because i am having problem to post screenshot...

Invalid record count - grey screen- Target Mode Cures

Hi there,
I have a common problem: I was doing nothing particular that I remember: No fancy file uploads, doanloads, creation, erasing - nothing special:
Anyway after a customary week, or few days of leaving the macbook permanently on, I think "let's give it a rest".
Then switch back on:
- Grey screen, spinning grey progress wheel fine.
- Takes a while. Strange. After say a minute - it just switches off wordlessly.
- Reset PRAM: No solution. Take a look with single-user startup in console: Files are all there, OK. Disk not dead.
- Start up from OS X 10.5 disk:
Permissions repair fine. Good.
Verify disk: FAIL! +*Invalid Record Count.Volume check failed.*+
Next: *Try target disk mode to back up essentials* - that works fine: I now have Time Machine AND a smaller important essentials backup.
But finally, here's the surprise: Just for kicks, I *shut the macbook down, try a reboot - and it works!*
But I note that root system files are unchanged since the problem occurred: ".hotfiles.btree" for example (I don't know what that is but suspect it's relevant).
Then: I tried restarting again - and back to square one, it won't boot.
Do the "Target disk" firewire mode trick again, and browse a few folders: And it boots (slowly).
If I just leave the Macbook on permanently - everything seems fine. Not even sluggish.
So:
- Why can connecting a disk with an incorrect file system in target disk make the system forget about these problems when booting?
- Why does the problem return on a successive reboot?
- Is it related to some system files being ignored if booting straight after a target mode session?
- What is ".hotfiles.btree", and should it not exist ?
And the big one:
- +Can extended Applecare, wot cost me loads of money, help me?+

Hi Cornelius:
Having been a faithful Apple-groupie for a while, and despite some problems over the years (hard drive failing, screen going, etc.) this is the first time I'm disappointed with them, because theor Micromat Applecare deal is a ripoff:
You fork out for Applecare extension: All you get is something that say "Yep, you've got a problem. Now go and buy techtoolpro".
That is, the TechTool Deluxe is practically useless. Argh.
Worse: They keep that rather quiet. If you run TechTool deluxe, and it fails: It points you to the Techtool site to
"download the TechTool Deluxe software with diagnostic and repair capabilities".
You think "Aha, right, I need an update, or a DMG rather than just the executable".
Download another 1.25Gb.
So you try again: Same thing.
The chiselling little crooks, to quote Ken Livingstone, won't even come out and say "Buy TechTool Pro to fix it". The website as reported above is wrong.
Result: I'm not happy with them. And I'll never buy anything off Micromat.
In the meantime, I've got a bootable backup thanks to CC-Cloner (excellent, I'll send him some money), and I'm waiting until I don't have any critical deadlines to allow myself time to restore a daily bootable backup.
The dodgy files seem to be the Sun Developper Java suite according to CC Cloner.

Disk not mounting in Target mode. Other options?

I had a disastrous snow leopard upgrade that has thrashed my hard drive on my MBP. It is strange because my iMac upgraded with no issues and is a more 'complicated' system to upgrade.
I get an invalid node error message when verifying the disk. I cannot boot the OS from the hard drive anymore. Attempting to do an OS install gives me an error message that the contents of the disk cannot be changed.
When I launch the OS from the snow leopard CD, I am able to get to the file system via a Terminal window. There are a few files that I would like to salvage if possible before doing a reinstall of the OS. I tried setting the MBP to Target mode to access from the iMac, but the drive does not mount (only the DVD drive mounts).
Are there any other options? I can also get to these files in single user mode. I would like to physically get them copied somewhere outside of the system if possible (instead of moving them to a different location on the drive and doing an install).
Any thoughts would be greatly appreciated.

Hi Andy Manson;
The invalid node error message indicates serious problems with the directory for that disk. This could be the reason that you are unable to boot.
You might try a demo copy of Data Rescue II to see what it salvage in the way of files from the disk.
Since AFAIK DiskWarrior is not ready for Snow Leopard yet that only leaves you a reformat of the drive to repair this problem.
Allan

Is it possible to start intel mac in target mode from ppc mac ?

Hello all,
Is it possible to start intel mac in target mode from ppc mac ? If so does using target mode make ANY change at all to the target disk if user doesn't voluntariliy write stuff to target disk ?
Thanks in advance !

Yes, you can, but with some notes. Braby sent some data, I add some other.
Target Mode has two basic roles:
1. to turn a mac into an external drive and/or external optical drive (if it has one, until Air era, all had); you may use this way if your internal optical drive is damaged and you wish to use the optical unit of the other mac; or use it as a simple external disk for backup purposes or else.
2. to boot from a such-booted mac.
#1 is usable with any two macs disregarding whether they are both PPC, both intel, or combination PPC-intel, as the behavior is like any external disk drive or external optical drive.
#2 is impossible if you want to boot the other mac, they must be both intel or PPC, as you cannot use an intel-based mac as a boot mac for the other ppc-mac, and vice-versa.
So said and clarified, you may use, but not if you intend to boot the other one if you wish to use it for various purposes implying boot.

Target Mode Slow?

Hi out there!
I want to delete the 250GB hard drive of my iMac G5 because I want to sell him. My idea was to use him in target mode (connected to the new Mac) and delete the drive by writing 'zeros' to it so nobody can read the data any more.
So far so good, BUT: why does it take 10hours to write zeros to a hard disk of 250GB?! I did the same to my external 250GB HD, and it took 'just' 1.5 hours.
Also strange is the fact that the fans go to maximum when the Mac starts in target mode.
Any ideas?
Cheers,
Scaramuccia

It would be easier for you to boot from your install disc or from your Leopard disc, and use Disk Utility:
1. Insert the Mac OS X Install disc or your Leopard disc that came with your computer, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume.
6. Click erase seven pass, and your hard drive will be erased. It should only take a few minutes.

Gray screen (no verbose mode, na target mode, no nothing)

My late 2007 Macbook Pro just freezed on the spinning ball while browsing Internet.
After forced shutdown, I now have the gray screen (without the Apple logo or the spinner) and it won't go past it, while maxing out RPMs on the fans.
Strange thing is that it won't go into verbose mode, safe mode or FW target mode (no reaction on the keys combination).
If I try to force startup drive selection (ALT while booting) it ends up in showing just the mouse pointer (no drives list or even the question mark).
Can't fire up the repair utility from the install CD as my Superdrive has been dead for months now.
Tried reseting the PRAM and nothing changed.
Tried replacing the RAM with the exact 2x512MB factory chips and nothing changed.
Any suggestions?
Thanks in advance.

Try Resetting the System Management Controller (SMC)

How did Target mode fix my video problem?

On my 2006 MacBook Pro 15 the video had gone wrong with coloured diagonal lines appearing on startup making the computer unusable. However after putting it into Target mode to get some files and try to install a USB to HMDi adaptor driver, the computer came back up with a normal screen. This worked for several hours before it went bad again, however a few minutes in Target mode and all way well again after rebooking, very strange.
Any thoughts why this could fix what seemed like a logic board replacement, as the graphics were intergrated.

Since Target mode works straight out of the firmware without depending on HDD content, it is probably resetting the video infrastructure, which later gets corrupted by software. At least I think the GPU/VRAM/etc. thing seems ok. Few ideas:
Try starting up in Safe Mode (press down Shift before the chime). Takes a LONG while, but clears many caches that may be corrupted.
Purge any and all caches for good. Use OnyX or similar utility.
Disable the integrated Intel GPU by unchecking Automatic graphics switching in System Preferences/Energy Saver and see if that helps. You'll be running exclusively on the Radeon GPU, which is a battery gobbler, beware.

Broken firewire ports - boot problems - target mode help needed

HI there,
I have a 15" macbook pro from 2008 with core 2 duo cpu etc.
It has recently developed the problem of hanging during the boot process with a blue screen, taking around 5 minutes to get to the login screen.
Much research has led me to the solution of removing two files from the SYSTEM > LIBRARY > EXTENSIONS folder relating to the firewire bus (?) and this has solved the issues about booting. (IOFirewireIP.kext and IOFirewireFamily.kext)
(I put on a clean install of 10.6.3 and the screen stayed blue. Removing these two files in target mode fixed this problem.)
There is still a sleep problem though - i.e. the machine does not wake from manual sleep (Apple menu) or if the system sleeps after the time allocated in the energy saving preferences.
There are so many suggestions on the web, it's almost impossible to know what the correct course of action is.
Another strange thing is, is that I can boot into target mode and access the drive via the firewire (400) port from another mac.
If the port were truly broken, how come it still works in target mode?
Is it possible that the firewire interface is not broken, but disabling these two files above could eliminate another associated problem?
Also, is there an online resource, or walkthrough, to eliminate what could be causing the sleep problems?
I would appreciate someone's suggestions on this and thank you for your help in advance!
Best wishes,
Torbz

Strangely, after installing a clean 10.6.3 - I've updated to 10.6.8 and the firewire ports are suddenly back and being reported in system profiler (whereby they were not before).
The two files I deleted above have been re-instated through the updates - and all seems well.
I've yet to check the sleep mode problem - but the firewire has at least sorted itself out...
That's a bonus!
Torbz

Can't copy files in Target Mode

I'm trying to move applications from my Titanium PowerBook G4 (OS X 10.4.7) to my MacBook by booting the G4 in Target Disk Mode. I can get the icon representing the G4's HDD to appear on the MacBook's desktop, but sometimes when I double-click to open it, I get the beach ball and no window opens for the HDD. Most of the time the window opens, but then I get the beach ball when I try to open the Applications folder. So back on the G4 I tried moving the application's (Photoshop Elements) folder icon out of the Applications folder and into the HDD window. Now in Target Mode, when I drag the Photoshop folder icon out of the G4's window and onto the MacBook desktop, the copying process seems to initiate normally, but then stops. It always stops at the same number of MB copied, and then I get the interminable beach ball.
What's happening and how do I fix it?
--howard

Hard to say. Boot the PB with its Tiger install disk and run Disk Utility, repairing the disk and its permissions. Boot the PB with its Apple Hardware Test disk and run the extended tests. If the PB passes all of those, then repeat the same steps with the MB. Once both pass the tests, retry the TDM hookup, and copying stuff.

Can't Put G4 in TARGET MODE

I sure hope someone can help me. I have a 5-year-old G5. It was the biggest system at the time. I just got a gigantic Mac Pro and I'm trying to EASILY use the Migration Assistant to transfer my data. I started by trying to restart the G4 and holding the T key. The G4 shuts down. I tried resetting the PRAM 3 times and then selecting the Startup Disk in System Preferences and restarting using that as the Target Mode. The G4 shut down. I've switched the firewire cables to different connections...no luck. I've tried to restart the G4 with Option-Apple O + F and typing in target-mode and no luck. The G4 simply WILL NOT go into Target Mode. Has this happened to anyone else? If so, what was the problem and how did you get it to work? Help please!!!

Hi...thanks for the link and info but the computer is set up exactly as it came from Apple computer. Where do I look to find out how it was configured and then, if it's not like you mentioned, what do I do? Will I need to bring it in to an Apple repair place to reconfigure it? It states, below, that all later Macintosh computers come with an ATA hard drive at ATA Bus 0 in their default configurations. What do they mean by "later?" This is a G4, 5 years old.
FireWire Target Disk Mode: Target Computer Shuts Down at Startup
FireWire target disk mode requires the target computer to have an ATA hard drive at ATA bus 0.
Symptom
When you try to start up the target computer, it makes its startup sound, but then shuts down. No video appears on the screen, nor does the FireWire icon. The computer starts up normally without the T key held down.
Products affected
* Macintosh computer with built-in FireWire port
Solution
Make sure the target computer has an ATA hard drive on ATA bus 0. It is normal for a target computer to shut down if it does not detect an ATA hard drive on ATA bus 0.
All later Macintosh computers come with an ATA hard drive at ATA Bus 0 in their default configurations. However, it is possible to custom order (CTO) a Macintosh that does not.

Wrong drive appears in Target mode

Hey guys. I know this is probably something very simple, but I'm trying to restore the drive on my G4. I've previously carbon copied my drive to an extra drive in my G5, as I regularly get weird cache problems on my G4. Now that it's happened again, I want to Carbon copy back from the G5 to the G4, but when I connect in target mode with firewire, I cannot find the primary drive on the G4, only some secondary drive which helps me nothing
Is it as simple as switching the actual harddrives around/changing the jumpers on the actual harddrives; or is there some setting somewhere that I'm missing?

Welcome to the Discussions.
"I regularly get weird cache problems on my G4"
That might be a failing processor. There are Apple Hardware Test disk images here. http://www.info.apple.com/support/aht.html

Booting from firewire target mode on a mac pro with kernel panic?

hello
i am wondering if it is possible to use firewire target mode to boot a mac pro that has never got past a multi language kernel panic on boot?
basically i have tried all the other options and cant get it to open the superdrive to insert my installation disk, as to repair the drivers with my snow leopard disk.
i've tried holding my mouse key down, the paperclip option on the drive itself and the firmware keycombo, so my idea is that the only way to fix it is with target mode. can this be done - and if so - could someone direct me towards a tutorial that will help me do this.
please advise if this is possible or if there is another method i should use? apart from taking it to the applestore (extreme last ditch option) i am quite low on ideas here.
many thanks!
p.s heres the message i wrote for the original problem which caused all the kernel panics;
"i recently bought a mac pro and upon starting it for the first time opted to transfer the all the data i could over via firewire from my macbook pro.
i used the standard 't' command with the firewire symbol.
Somewhere towards the end of the transfer (I am not sure at what pont - I wasnt there for all of it) - , the monitor went blank and the whole thing was unresponsive. my macbook's firewire sign continued to move around the screen.
after leaving it for some time i decided to turn off the macbook and then the mac pro.
i restarted the macbook and got some pretty crazy stuff happening to my calender - but so far everything seems to be fine.
i am more concerned about the "you need to restart your computer" message; this is the dreaded 'kernel panic' right?. i have never actually done anything with this computer yet, and it was purchased new."

"i recently bought a mac pro and upon starting it for the first time opted to transfer the all the data i could over via firewire from my macbook pro.
Never opt to transfer until you have insured it works fine for a couple days, I would never use Setup or Migration Assistant until such time, and I would have a bootable backup clone.
Try pulling all the hard drives from inside your Mac Pro and boot from OS X DVD - latest OS build.

MacBook Pro mid 2010 - iMac late 2012 in target mode?

Can I connect a MacBook Pro mid 2010 with Mini Display Port with a late 1012 iMac in target mode? Thanks.

A 2010 MBP does not support Thunderbolt technology so that is not an avenue for you. A Fire wire with one of these adapters should enable you to connect the two devices:
store.apple.com/us/product/MD464ZM/A/apple-thunderbolt-to-firewire-adapter
Ciao.

New iMac Not Recognizing iBook Running In Target Mode

Help!! I am helping a friend transfer all of her files and settings from her old iBook to a new iMac. I have repeatedly followed the instructions for using the Migration Assistant but the new iMac does not recognize the iBook after it is started in Target Mode. I have switched cables, zapped the pram, used the startup disk to repair disks and permissions. I can plug in an external firewire drive and it recognizes it immediately. I was called Apple Support, talked with first layer technician, was put on hold for next level of technician, put phone on speaker, person came back, said they couldn't hear me and hung up. Called back and low and behold it was quitting time. Very, Very frustrated.

bookwiz wrote:
the new iMac does not recognize the iBook after it is started in Target Mode.
Several posters have reported this. A solution that has worked for some is to place a powered firewire hub between the two machines (if you external FW disk is self powered and has two FW ports, that might work).

Strange target mode behavior

Similar Messages

Maybe you are looking for