Bad "Device Removal" notice

All I did was wake from sleep, and I got:
"! Device Removal
"The device you removed was not properly put away. Data might have been lost or damaged. Before you unplug your device, you must first select its icon in the Finder and choose Eject from the File menu."
But I didn't remove any device. The volumes mentioned in the system log following were connected (firewire 800) throughout and test ok. I do have Spotless on and the volumes mentioned are (like several others) therein marked "indexing disabled" with auto off and no existing index. Note in particular that the messages "media not present" refer to volumes which are physically connected and function perfectly before and after the sleep.
I hope somebody can tell me what's going on. (This has suddenly cropped up.)
Sep 7 18:29:08 Emily kernel[0]: System Sleep
Sep 7 18:29:08 Emily kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Sep 7 18:29:08 Emily kernel[0]: Started CPU 01
Sep 7 18:29:08 Emily kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Sep 7 18:29:08 Emily kernel[0]: Started CPU 02
Sep 7 18:29:08 Emily kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Sep 7 18:29:08 Emily kernel[0]: Started CPU 03
Sep 7 18:29:08 Emily kernel[0]: System Wake
Sep 7 18:29:08 Emily kernel[0]: USB caused wake event (EHCI)
Sep 7 18:29:08 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:08 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:09 Emily kernel[0]: M-FW: M-Audio FireWire device found.
Sep 7 18:29:09 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:09 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:09 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:09 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:09 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:09 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:09 Emily kernel[0]: M-FW: metanub 0x76A1E00 GUID:d6c0110384013
Sep 7 18:29:10 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:10 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:10 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:10 Emily kernel[0]: Intel8254x -- Link Up -- 00:17:f2:0c:29:73 -- called by interruptOccurred() --
Sep 7 18:29:10 Emily kernel[0]: -- Auto-Negotiation Advertisement Register (04d) = 0xde1
Sep 7 18:29:10 Emily kernel[0]: -- Auto-Negotiation Link Partner Ability Register (05d) = 0x41e1
Sep 7 18:29:10 Emily kernel[0]: -- Auto-Negotiation Gigabit Advertisement Register (09d) = 0xe00
Sep 7 18:29:10 Emily kernel[0]: -- Auto-Negotiation Gigabit Link Partner Ability Register (10d) = 0x4000
Sep 7 18:29:10 Emily kernel[0]: -- PHY Specific Status Register (17d) = 0x6c48
Sep 7 18:29:10 Emily kernel[0]: Intel8254X -- Negotiated Speed: 100 Mb/s, Duplex: Full, Flow Control: Receive Pause Disabled, Transmit Pause Disabled
Sep 7 18:29:10 Emily kernel[0]: M-FW: FireWire bus reset completed.
Sep 7 18:29:12 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:12 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:12 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:12 Emily kernel[0]: M-FW: FireWire bus reset completed.
Sep 7 18:29:14 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:14 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:14 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:14 Emily kernel[0]: M-FW: FireWire bus reset completed.
Sep 7 18:29:15 Emily configd[40]: posting notification com.apple.system.config.network_change
Sep 7 18:29:15 Emily lookupd[838]: lookupd (version 369.8) starting - Mon Sep 7 18:29:15 2009
Sep 7 18:29:16 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:16 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:16 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:16 Emily kernel[0]: M-FW: FireWire bus reset completed.
Sep 7 18:29:16 Emily kernel[0]: M-FW: Firnware active and we already started matching..
Sep 7 18:29:16 Emily kernel[0]: M-FW: Bootloader active: starting firmware.
Sep 7 18:29:18 Emily kernel[0]: Write for 0x6ef6600 done, status e00002d7
Sep 7 18:29:19 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:19 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:19 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:20 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:20 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:20 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:20 Emily kernel[0]: M-FW: FireWire bus reset completed.
Sep 7 18:29:20 Emily kernel[0]: M-FW: FireWire bus reset completed.
Sep 7 18:29:20 Emily kernel[0]: M-FW: Trying to resend mixer settings too often (within 1 second of previous resend)
Sep 7 18:29:37 Emily kernel[0]: M-FW: Reregister: device node vanished.
Sep 7 18:29:37 Emily kernel[0]: disk1s3: media is not present.
Sep 7 18:29:37 Emily kernel[0]: jnl: dojnlio: strategy err 0x6
Sep 7 18:29:37 Emily kernel[0]: jnl: end_transaction: only wrote 0 of 16896 bytes to the journal!
Sep 7 18:29:37 Emily kernel[0]: jnl: close: journal 0x6c23bb4, is invalid. aborting outstanding transactions
Sep 7 18:29:37 Emily kernel[0]: disk1s5: media is not present.
Sep 7 18:29:37 Emily kernel[0]: jnl: dojnlio: strategy err 0x6
Sep 7 18:29:37 Emily kernel[0]: jnl: end_transaction: only wrote 0 of 16896 bytes to the journal!
Sep 7 18:29:37 Emily kernel[0]: jnl: close: journal 0x6c23908, is invalid. aborting outstanding transactions
Sep 7 18:29:46 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:46 Emily kernel[0]: M-FW: FireWire bus reset started.
Sep 7 18:29:46 Emily kernel[0]: M-FW: FireWire bus reset completed.
Sep 7 18:29:46 Emily kernel[0]: M-FW: FireWire bus reset completed.
Sep 7 18:29:48 Emily kernel[0]: jnl: replay_journal: from: 2102272 to: 2143744 (joffset 0x4a0000)
Sep 7 18:29:48 Emily diskarbitrationd[43]: disk1s5 hfs 99D63266-6DAC-340C-8DF5-78500F105CA9 Odd External /Volumes/Odd External
Sep 7 18:29:48 Emily kernel[0]: jnl: replay_journal: from: 4165632 to: 4215296 (joffset 0x2aa000)
Sep 7 18:29:48 Emily diskarbitrationd[43]: disk1s3 hfs 35148003-8ED6-3AB0-8E9F-9058F72A6CB7 Odd External Boot /Volumes/Odd External Boot
Sep 7 18:29:48 Emily authexec: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
Sep 7 18:29:48 Emily authexec: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
Sep 7 18:29:48 Emily authexec: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
Sep 7 18:29:48 Emily authexec: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
Sep 7 18:29:48 Emily authexec: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
Sep 7 18:29:48 Emily authexec: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
Sep 7 18:29:48 Emily authexec: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
Sep 7 18:29:48 Emily authexec: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
Sep 7 18:29:48 Emily authexec: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
Sep 7 18:29:49 Emily authexec: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
Sep 7 18:29:49 Emily authexec: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
Sep 7 18:29:49 Emily authexec: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
Sep 7 18:29:49 Emily authexec: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
Sep 7 18:29:49 Emily authexec: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
"Emily" is of course my Mac Pro's name, in honour of Emily Dickinson.

Hi Dawn,
Are any of these devices Bus powered?
Seems this is the problem area...
Sep 7 18:29:37 Emily kernel[0]: M-FW: Reregister: device node vanished.
Sep 7 18:29:37 Emily kernel[0]: disk1s3: media is not present.
Sep 7 18:29:37 Emily kernel[0]: jnl: dojnlio: strategy err 0x6
Sep 7 18:29:37 Emily kernel[0]: jnl: end_transaction: only wrote 0 of 16896 bytes to the journal!
Sep 7 18:29:37 Emily kernel[0]: jnl: close: journal 0x6c23bb4, is invalid. aborting outstanding transactions
Sep 7 18:29:37 Emily kernel[0]: disk1s5: media is not present.
Sep 7 18:29:37 Emily kernel[0]: jnl: dojnlio: strategy err 0x6
Sep 7 18:29:37 Emily kernel[0]: jnl: end_transaction: only wrote 0 of 16896 bytes to the journal!
Sep 7 18:29:37 Emily kernel[0]: jnl: close: journal 0x6c23908, is invalid. aborting outstanding transactions
Might be a bad Journal file, which is hard to overcome.

Similar Messages

Get error message e auth bad device key or pkcs12

windows 8 os did a system restore then when I tried to download a book from my library I get error message
e auth bad device key or pkcs12
It was working fine before the restore

How To Change the Authorized Adobe ID
http://www.adobe.com/go/digital-editions-createID
What do you do if your copy of Adobe Digital Editions is authorized with the wrong Adobe ID? This can happen if you’ve started using a different Adobe ID or you somehow messed up the authorization in the past.
If you’re trying to open an ebook when Adobe Digital Editions is authorized with the wrong Adobe ID, you’ll get an error message like: “License fulfilled by a different user” or something similar referencing licensing or authorization.
Important note: If you have some ebooks that do require your current authorization, those will become unreadable if you authorize with a different Adobe ID.
deauthorize
The first thing to do is deauthorize Adobe Digital Editions. This will remove your current authorization.
1. Open Adobe Digital Editions
2. On your keyboard, simultaneously press the Ctrl, Shift, and D buttons (if on Windows) or the Cmd, Shift, and D buttons (if on a Mac)
3. Click the “Deauthorize” button
After this you should close Adobe Digital Editions, and then open it again.
re-authorize
If you’ve followed the steps above, your copy of Adobe Digital Editions is no longer authorized.
Open Adobe Digital Editions
Adobe Digital Editions will behave as if you’ve just installed it, and will prompt you to enter your login information for your Adobe ID. Use the Adobe ID account information that you want to use to authorize Adobe Digital Editions.

"Device Removal" warning when trying to mount 2 Ext HDs

I'm trying to copy some files from one external HD to another. When I connect these to my G5 and power up, one of them will mount and then the second one knocks the other other one off the desktop and I get the "Device Removal" warning. It happens regardless of which order I do this. HD 1 is about 3 years old, HD 2 is about 1 month old. I've tried disconnecting them both and reconnecting them, I've switched firewire cables and ports. They are both Western Digital firewire 7200 rpm. This has happened before with other ext HDs that I use. Some of them can all be connected to the G5 without any problems at times. There have been a couple of power failures due to some stormy weather lately but I disconnected everything from the power strip prior to bad weather. Don't know if this has any bearing on the problem, just thought I'd mention it.
Any advice would be greatly appreciated. Steve L.

Hello! Try them separately on one of the motherboard ports. Were they daisy chained together? This sometimes causes problems. Also when you connect them one at a time to different ports listed the them as they spin up as weak (or failing) power supplies on some externals have caused porblems. Tom

N580GTX - d3d11 appwindow::do_swap(): device removed

I just received my N580GTXoc from Newegg and I've been getting random freezes, display driver crashes (display driver has crashed and recovered) and the error dialog box "d3d11 appwindow::do_swap(): device removed" when running Unigine Heaven 2.1
My stats are:
XFXForce 780i
Intel Q9550 @ 2.85 ghz
4gig ram
Ultra X3 1,000w psu
MSI N580GTXoc at "stock speed" of 823/1069/1645 (see image)
Video Driver 266.58
Any help would be appreciated!
Brew

Quote from: Brewskie on 13-February-11, 05:49:44
I applied the voltage to 1038v and all the tests that were freezing can now run. Although there is a little artifacting and tearing in some places. But it's not very bad really.
The bench scores aren't really very high for a GTX580 but that's because of the mainboard, cpu and memory. Sandy Bridge 2600k would really help
Do I stick with this voltage? Or are there other things to do also?
Will I have to load up AB every time windows starts now?
Thanks again for your great help
Quote
Will I have to load up AB every time windows starts now?
nope, not necessary
Quote
I applied the voltage to 1038v and all the tests that were freezing can now run. Although there is a little artifacting and tearing in some places. But it's not very bad really.
Test it with OCCT Test:
http://www.ocbase.com/perestroika_en/index.php?Download
Select GPU:OCCT , checkmark "Error Check", then click on "On"
And leave it to test for few hours, see if arficats will comes there.[if such are appear they will be counted]

X6 Camera - Do I have a bad device?

I'm having issues with the camera application. When I press the camera button, the app initializes fine, the graphic overlays come up (touch buttons, focus box etc) but most of the time it stops there - no image is presented on the screen from the sensor. Sometimes the image displays fine - but most of the time nothing but a black screen (with the graphic overlays).
If I sit at the black screen for a while - I get the 'Camera on standby' message. Pressing 'Continue' and I still have a black screen. Switching to the secondary camera and I get the same result.
Click to take an image. I get the camera sound and 'Processing image' followed by 'Unexpected error occurred. Restart phone'. I restart the phone - but still (most of the time) - the camera simply fails to work.
I've thought that maybe this is something to do with accessing the mass memory - but I still get the issue when I tell the application to save to phone memory.
I've tried a back-to-defaults reset - and the issue persists. I'm thinking about fully erasing the mass memory - but it's a real pain getting everything setup again.
Any suggestions? Anyone else seen anything like this? Is it simply a bad device?
Thanks.
X6-00 RM-551
V12.2.091

One more thing I just noticed this morning.
I re-installed Qik (the video capture application).
A fresh reboot of the device and I can use Qik to capture video all day. No issues at all.
I close Qik and open the Camera application. Black screen. I close the camera application. I restart Qik. It tells me that the camera is in use by another application and exits. Nothing else is running.... Seems the camera app is holding some kind of lock on the camera hardware and not properly exiting (or not cleaning up after exiting).
Either way - the implication here is that the camera is just fine (I can use Qik all day without issue) but as soon as I open the camera application all heck breaks use until I reboot. This seems to indicate a software issue.
I re-erased and re-flashed to be sure - and the issue remains. So - I'm still confused. Nobody else seems to be having this issue with the X6 and a full erase and reflash seems to cause the issue to remain (seemingly indicating a hardware issue) - but a third party camera application after a reboot seems to never have any issues at all - until the native app is launched when the native app seems to mess something up such that the third party app now reports a sharing violation on the camera hardware - seemingly indicating a software issue...

Won't show CF card, yet it gives me device removal warning when I pull it.

This happens occasionally and I don't know why. I put in a disc and it does not show in the finder under devices or anywhere else I can find. I pull the disc, and it gives the the device removal warning. It it's reading it, then where the heck am I supposed to find it?? Thanks.

A multi card reader that has always worked in the past (almost always). Plugged the same reader into my Macbook and worked just fine. Tried it directs as well as through hub.

How do I fix the error getting bad device-uri

I am trying to add a domain printer to my new Mac running Mavericks all but one network printer get the same error bad device-uri "smb..... Can anyone tell me a way around this error.

Hey KLCTech,
Try using the information in the following articles to help you resolve this issue:
OS X: Connecting a Wi-Fi printer to your Wi-Fi network
http://support.apple.com/kb/ht3500
Troubleshooting printer issues in OS X
http://support.apple.com/kb/ts3147
Thanks for using the Apple Support Communities. Have a good one!
-Braden

Device removal error..... The card reader ejects itself

Hello, I'm new to macs and purchased a Mac Mini a week ago. Things were going well until I needed to move pictures from a digital camera to my mac.
I purchased a GE 19 in 1 card reader which is built for mac os x. I hook it up to a usb port and try and look at some pictures. After a few seconds, the card reader ejects itself and I get the "device removal" error. The error will then continue to appear over and over again. When I try to eject the reader using by clicking eject, the reader ejects and only reappears a minute later and ejects itself again. I've tried using another usb port and I know for sure that its not the cable.
If I can't get any prompt answer here, I'm going to call the Genius bar tomorrow morning and ask about the problem. <Edited by Moderator>

More often than not, when a card reader or other similar device disconnects from the USB bus because it is drawing too much power. In a card reader, that would not unusually be triggered not by the card reader itself, but by the insertion of a card causing it to read the content and mount the volume on the Mac's desktop. Part of the problem is that while everything is invariably quoted as USB compatible, many such devices don't entirely comply with the USB standard, resulting in conflicts or load demands which may be borderline, or worse.
You may be able to get more reliable performance from your reader by disconnecting other USB devices when you are trying to use it, or by using it with a powered USB hub. Occasionally, borderline problems can be temporarily resolved by connecting the device to a different port, if necessary switching devices around. Alternatively, it may be that in an attempt to produce a device with the greatest flexibility in terms of media compatibility, they have compromised on components.
I would generally recommend a card reader designed for the specific card type you need. These are typically far more reliable. If you need to use different types of card media, then be prepared to spent on a well established brand with a reputation in this sector of the market, such as SanDisk.

Sudden device removal via Firewire 800

I just purchased a MacBook Pro. I have a LaCie rugged drive that is a clone of my old iBook running Panther. I connected the LaCie via Firewire to the MBP to transfer some files. (Migration Assistant didn't get everything???) The LaCie kept suddenly disconnecting, resulting in a device removal error. I have two different cables; tried them both. It connected to the old iBook last night with no removal error.
Any ideas??

Here's what LaCie had to say:
Thank you for contacting LaCie Technical Support. As the issue you describe is an intermittent issue, it is difficult to pin point the exact issue and an exact resolution.
Mobile drives are commonly referred to as "Bus Powered" devices. They don't typically require an external power supply, and are powered by the ports on the computer. Ordinarily this is an acceptable amount of power, however, not all machines are capable of running these devices.
Most mobile drives require approximately 4 watts of energy to run. Most computers produce this, so it isn't a problem. There are exceptions, however. The physical symptom of insufficient power is a soft "clicking" sound. OS behavior can vary.
* On Mac OS X, the mobile drive can appear as an "Unknown Device" in Apple System Profiler (ASP), appear in an unusual way in Disk Utility, refuse to format with error -36, or have no reaction at all
* On Windows, the drive can appear with a Code 10 error in Device Manager, appear in an unusual way in Disk Management, refuse to format, or have no reaction at all.
All mobile drives have a "USB Power Sharing" cable included in the box. If a power problem is suspected, connect this cable to a second USB port on the computer. This will allow the drive to take more power, and can possibly make the difference in allowing it to work. Also, ensure the drive is not connected to a USB Hub of any kind. Connect all bus-powered devices directly to the computer USB ports.
Let us know the results.
Thoughts? Anyone?

Bogus "Device Removal" Alert for SDcard Reader

Using the same SDcards, same reader, same USB hub as I did before the 10.5.8 update, I now get a "Device Removal" alert after a period of time once an SDcard is inserted. It varies from just a minute or two to around an hour or more. When I click off the alert window the card remounts right away but the alert always comes back after a while.
Something tells me a PRAM zap might fix it, but is anyone else seeing this with 10.5.8?

More Info: After resetting PRAM and a reboot, still the same symptoms except this time, after the "Device Removal" message came up. the lights on the reader flashed for a while and then the following alert window appeared: "Disk Repair The disk "NO NAME" was not repairable by this computer. It is being made available to you with limited functionality. You must back up your data and reformat the disk as soon as possible." Never saw that one before. This alert finally went away by itself, another "Device Removal" alert appeared, and now it's continually mounting the card then showing the removal alert, every few minutes.

Device removal error?

I picked up a new 500 gig Hitachi hard drive to put into a vantex hd enclosure. Now every time I try and use it, i get a device removal error and the hard drive icon on the desktop disappears. I can't use Time machine or verify my hard drive in disk utilities because it always seems to eject itself. I tried a couple different USB cables and tried rebooting my computer. Both products are new, I'm wondering if it is a hardware problem and if it is, which one, the enclosure or the hard drive?
Any suggestions?

Thanks for the suggestion but..
Tried that this morning and it still doesn't work:( I turn it on, start up Time Machine and it starts backing up the files and then some times it will start backing up 20-30 gigs and then give me the device removal error, or sometimes it only backs up 10-20 mb before giving me that error, but even after it ejects itself the hard drive is still on, but i have to turn it off and then back on again for the disk to remount. I'm leaning towards a hardware problem, just not sure if its hard drive or enclosure. I bought both online and having to send them back is always a pain because they usually just send them back saying they work and tack on another fee. Im hoping to resolve this some other way, but running out of ideas.
Any other thoughts?

Xserve Raid - Devicer Removal Error ?!

Hi !
Can anybody help me ?
Whenever I copy some files from my Macintosh HD on my G5
to Xserve Raid 30 seconds after start copy process stops and I
get an Device Removal error.
I have traid everything and I can't get it right.
BTW
is my setup ok ?
Apple Fibre Channel Card
Port speed: 2 Gb/s
Port topology: Arbitrated loop
Xserve Raid
Port speed: 2 Gb/s
Port topology: Arbitrated loop
Read prefetch: 128 stripes - 8 MB/disk
Controller cache: on
Drive cache: on
Host flushing: off
Steady Streaming: off
Raid slices:
2x250 GB left controller
2x250 gb right controller
Disc Utility software raid:
Striped raid 0
left + right
Raid block size (default: 32 K): 256K
Please help!
Thx!
Crowebster

Hey Kel,
I've only seen a error -36 on a raid volume twice.. both times were days before a controller failed. I'd try swapping controllers and see if the problem follows the controller...

Getting following error when trying to download ebooks: E-AUTH-BAD-DEVICE-KEY-OR-PKCS12

I AM TRYING TO USE A GLOWLIGHT I JUST PURCHASED, BUT KEEP GETTING ERROR: E-AUTH-BAD-DEVICE-KEY-OR-PKCS12. Can you tell me what I need to do to correct this problem?

Some ebook sellers use the Adobe DRM mechanism, but rather than relying on the Adobe ID for authorization have their own Vendor ID (their own user/password).
You could be able to read your old books but not the new one if all the old books used the Adobe ID, but the new one used a separate Vendor ID.
Check with the ebook seller if you should be using a separate Vendor ID.
ADE1.7.2 does not support different vendor IDs. V2.0 does, but I am not sure exactly how to get it to do so.
The user guide says ' The best way to do this is to supply an Adobe ID or Vendor ID, associating the book with your ID.',
but doesn't say how to do this.

Device Removal Schedule not happening

Not sure where to post this, I'm happy for someone to tell me which sub would have been better.
I've recently discovered a few issues with our managed devices, the first is the Device Removal Schedule, it's not happening. I have it set to remove after 90 days but there are devices still in there that are much older. Any tips on how to fix it would be much appreciated.
In the meantime, is there a way to run it manually?

manng228,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

When waking from sleep getting "Device Removal" error on Lacie external

When waking from sleep getting "Device Removal" error on Lacie external drive. This drive is my Time Machine back-up and I don't want to lose it. I don't know if anyone else has seen this error. Let me know.

Getting this same error since switching from Firewire to USB. I have a Maxtor drive in an Adaptec enclosure. It has it's own power supply and both USB and Firewire 400 connections. Just upgraded to a new Mini from old Powerbook, so no more Firewire 400!
The big difference between USB and FW:
With the old PB G4 and Firewire, when I put it to sleep, I could hear the external drive actually spin down. On wake up, It would spin up and mount properly. Now with the Mini and USB, when I sleep the Mini, the external drive NEVER SPINS DOWN. I did some research and found that many drives have built-in power management that basically powers them down after some idle time. So the Mini is going to sleep with mounted drives, at some point later the drive sleeps itself, then when the Mini wakes, the drive's not there.
Obviously, Firewire is doing a better job of talking to my external than USB. I'm ordering a FW400-to-800 cable and will test this. I also think it has something to do with the chipset/firmware in the external enclosure, as many people are reporting their external USBs behave properly during sleep.

Bad "Device Removal" notice

Similar Messages

Maybe you are looking for