Buggy Bugs

Just when I think I'm beginnining to like Lightroom (aside from its performance), another bug. I was printing 5 or 6 images today, using appplication managed color using the SAME profile for all prints. I'm using an HP designjet 90 using their canned profiles (for satin premium plus paper). On the last print, when I select 'print' Lightroom says the profile is invalid and the print may not print properly. I tried deselectng the profile, and reselecting and I didn't get the message again. However, I decided to select 'show print preview' in my driver, and the preview was solid blue, printed anyway and obviously the profile was not used cause the print was muddy/flat. The profile WAS selected in Lightroom and was displayed, and it worked for the previous 4 prints. I've also had problems in the past with Lightroom recognizing my profiles for this printer with a .icc suffix. I used to get muddy prints till I changes to .icm.
Any ideas. It seems like not only are there bugs, but Lightroom isn't consistant at times.
Kevin

I think I'm giving up on Lightroom for now, for printing and even for developing. Aside from the consistency of its performance being lousy on my machine, the Print module is way too inconsistant and buggy in my experience.
For the library module, there are too many work-arounds just getting files into my folders, and I've had to make way to many concessions to work flow for it to be valuable at this time. Actually, I can't believe some of the work-arounds and 'jumping through hoops' some folks on the forum are making to 'force' LR to work.
All published data on Lightroom emphasizes that it was designed for photographers, and is intuitive to use. There are so many things with LR that are NOT obvious or intuitive, or even consistent with PS (and I'm not talking folder/library differences either).
It's a shame cause there's hints of greatness in it, but if you're charging good money for something bad, you'll just leave a bad taste in many people's mouths.
Kevin

Similar Messages

Thanks to iOS 6 ! Now my phone get slower n buggy ,bugs everywhere !!

After open Genius in AppStore, it crash !!!

Try This...
Close All Open Apps... Perform a Reset... Try again...
Reset ( No Data will be Lost )
Press and hold the Sleep/Wake button and the Home button at the same time for at least ten seconds, until the Apple logo appears. Release the Buttons.
http://support.apple.com/kb/ht1430

Captivate Buggy Bugs in Bugland

Captivate reorders layers, discards backgrounds, refuses to
save changes, and generally fights me every step of the way. Is
there a more mature release of this product on the way?

Hi jbarker3887
Keep in mind that we have no clue as to what the code has
been through. As fellow Adobe Community Expert Steve said, it's
logically version 6 I believe. It began life (to my knowledge) as a
product called FlashCam and was sold by Nexus Concepts. Then eHelp
corporation bought the technology and rebranded it as RoboDemo.
They had the reigns from version 2 to version 5. Then Macromedia
bought the technology from eHelp corporation and rebranded it as
Macromedia RoboDemo. After this, they soon created Captivate. So
who knows how much of the original code exists? This could account
for the issues. Additionally, as this seemed to be a product with a
niche Macromedia felt they needed to purchase as opposed to create
from scratch, this could account for why it doesn't quite "fit"
with any product Macromedia ever produced.
Cheers... Rick

How can I designate the primary monitor?

I have a three monitor setup. The center monitor has always been designated as the main monitor (has the Finder bar on it). Since I've upgraded to Mavericks, the left monitor seems to be the primary, despite the settings in the Display control panel remaining the same.
Yes, the Finder bar is now on all screens (which is great!), but when I Command-Tab to cycle through open applications, those icons appear on the left hand screen. Or when I open system preferences, even if the center monitor has focus, the pref open on the left hand screen.
Any ideas?
Thanks!
/david

Oddly this is a buggy bug (as I see it) with Mavs.
a work around, at this point, is to get the dock to appear in the monitor you wish to be the "main" one.
In reality, there is no main one anymore, unless you count login screen.
I digress.
anyway, you need to get the dock to appear in the monitor you wish to be the main one. I get the dock to appear by moving my cursor to the bottom of the screen and then moving it down once it's at the bottom of the display.

Functions from Module Scoping Question

Hello,
I have the following case:
I`m using module that contains several functions, some of them are executing commends in remote sessions. These functions are used from Powershell Script.
The issue is that when function refers to variable from the local computer using the “$Using:var” syntax, it does not tries to access the variables that is defined in Script scope.
The exception is:
“Invoke-Command : The value of the using variable ‘$using:var’ cannot be retrieved because it has not been set in the local session.”
This behavior is not reproduced when the functions are defined in the Script. I`m aware that Modules have their own “Scope”(or Context or whatever…), so I suppose the behavior is by design
I`m able to workaround it in two ways:
Using the “$Using:global:var” syntax in the script block or dot source the script.
However it`s not so appropriate for my purpose.
My Question is:
Can I force the Functions that comes from Module to behave the same way as if they are defined in the Script.
Any other suggestions are welcome.
Some examples:
Module content:
function Main
param
$sb2
$ses = New-PSSession -ComputerName sof-srv01
Execute -ses $ses -sb $sb2
function Execute
param (
$sb,
$ses
Invoke-Command -Session $ses -ScriptBlock $sb
Export-ModuleMember Execute,Main
Script content:
$var = ‘winrm’
$scr = {Get-Service $using:var}
Main -sb2 $scr

You're wrong as always: there's such a thing as DOT SOURCING MODE when using Import-Module.
Finally, you must know by now, that your post above is plain RUBBISH.
In other words, you are a complete PowerShell ignorant ( probably, you are a good rubbishellian ).
Surely, you re-read your BUGGY bug report https://connect.microsoft.com/PowerShell/feedback/details/828782/functions-in-script-modules-do-not-inherit-variables-from-the-scope-of-their-caller.
Now, someone posted how-to-do-it ...
I have no idea WHERE and WHY you got these three letters: m, v and p...
P.S.: How do you dare to post your rubbishell concepts in my reports? Leave my posts
clean!
Well, at least you finally had the guts to post what you meant by "Import-Module in DOT SOURCING MODE". As expected, it's garbage.
As you've pointed out, when you pass a path to a .ps1 file to Import-Module, it recognizes that a .ps1 file is not a module, and just dot-sources the script to load its contents instead. (And as you pointed out in your report on connect, this behavior
is buggy. Microsoft probably shouldn't have included it at all, and just had Import-Module produce an error if you try to point it as a non-module file, but whatever. The functionality is there now.)
Any discussion of Script Modules has nothing do with dot-sourcing a ps1 file, regardless of whether you did it yourself, or called Import-Module. Script Modules are psm1 files, and when they are imported, it happens in a very different way than when
a script is dot-sourced. Modules get their own session state which is separate from the main PowerShell session (except for the Global scope, which is shared by everything). That separation of session state is what leads to the types
of problems the OP posted here.
Now that you've finally owned up to what you were talking about, it would appear that your proposed solution is to stop using Script Modules, and just dot-source ps1 files instead. Have fun with that.

Installing Netweaver and mySap

Hello Everybody,
I need to install mySap, but the problem is that after installing SolMan 4.0 and using many features to configure the MaxDB database.
=> I can't configure Solman(do I need FrontEnd)
I don't really knows how I could install Netweaver 2004s and mySap ECC 6.0.
I checked the huge quantity of ínformation(seeing all the Guides that Sap could offer)
The problem is that every Guide links you to another.
It's like every road goes to Rom but which one is the short one?
Please Guys help me,
I have spend three Months installing Solman4.0 because of many buggy Bugs.
And I really don't want to spend this Summer doing that.
I used Vmware and the only version that works Java 1.4.2_09.
Database is MaxDB.
The Installation is on Central Server.
I'll be greatfull if you have a good tutorial for the first Step of Installation.
Please tell me how should I start.
Best Regards,
Kais
Message was edited by:
Kais El Kara

Hi
Use the below link, there are only 2 guides max you should closely follow -
<a href="https://websmp209.sap-ag.de/~sapidb/011000358700003114792005E">for Planning & Inst. docs</a>
1. Planning - This First Steps document helps you get started when you install or upgrade to mySAP ERP 2005.
2. The Master Guide - mySAP ERP 2005 provides important information about the installation sequence and the components to be installed.
Now go to this link
<a href="https://websmp209.sap-ag.de/sapidb/011000358700003114792005E">SAP ERP 2005 - Installation Documentation</a><a href="https://websmp209.sap-ag.de/sapidb/011000358700003114792005E">SAP ERP 2005 Inst docs.</a>[
for docs, choose the o/s (AIX/ Windows/ Linux) you want to use and just follow the guide.
Btw, if you are using VMWare you must have sufficiently large RAM in order to be sucessfull installation.
Hopefully SOlMan 4.0 will have no issues with recent SR 2, revert for queries
Hope this helps, good luck
Cheers
Senthil

Why does CC keep on breaking?

Couldn't install CC Desktop.........one and a half hour remote desktop with support! CC desktop won't sign in........"You've been signed out" buggy bug (delete folders, register again). Photoshop CC opens then closes with PS CC has stopped working dialog..................20 minute chat with support, didn't fix it, please call back when our Product experts will be able to fix it (delete folders, register again)....................Already installed CS6 suite has been hijacked by CC and keeps telling me my trials ended (I've got a serial key ansd I used it when I installed it last year!!!!) No time or tools to be creative as it needs fixing all the time. Delete the 3 same prog folders over and over results in some small time in getting up and running, until it probably occurs again? What's going on Adobe, I was looking forward to it all and am now soooo disappointed.

Try the solutions, here:
http://helpx.adobe.com/creative-cloud/kb/unable-login-creative-cloud-248.html

Okay, i have 2 bugs with maverick. First, when I delete a file within a window, the files deletes but the preview doesn't delete until I close the window and reopen it. Second, I work on a network of computers and the search feature is now buggy...

Okay, i have 2 bugs with maverick. First, when I delete a file within a window, the files deletes but the preview doesn't delete until I close the window and reopen it. Second, I work on a network of computers and the search feature is now buggy... When I search for a file, A) it asks me if it's a name, or it wont produce anything, and B), its slower than in prior OS versions and in some instances I have to toggle to a different directory and go back to my original directory in the search: menu bar or the search wont produce anything... Very buggy.

It appears to me that network file access is buggy in Maverick.
In my case I have a USB Drive attached to airport extreme (new model) and when I open folders on that drive they all appear empty. If I right click and I select get info after a few minutes! I get a list of the content.
It makes impossible navigate a directory tree.
File access has been trashed in Maverick.
They have improved (read broken) Finder. I need to manage a way to downgrade to Lion again.

[solved] powertop bug or buggy user?

When I run powertop, it complains that it cannot load /var/cache/powertop/saved_results.powertop. Initially, I thought this was a permissions problem. The default permissions on /var/cache/powertop seemed to be 600. I added execute permission for root (700). However, I still get the same complaint.
Searching the forums, I found one post which mentioned this in passing but the comment was not the main topic and received no follow-up.
I would think this was a powertop bug except that I've looked through the mailing list archives for Aug, Sep and Oct (i.e. since the release of 2.1) and can't see any reports of it which would seem a bit odd since I'd expect this sort of bug to be recognised rather quickly. So I'm thinking that it is probably a buggy user rather than a buggy application but I can't think what I'm missing.
[Note: powertop's bug reporting mechanism appears to be reporting to the mailing list and there doesn't seem to be a separate bug tracker so the mailing list seemed to be the place to look although it is not possible to search as far as I can tell.]
Last edited by cfr (2012-10-31 01:02:42)

So what else could be different? When I use powertop, I get:
Loaded 77 prior measurements
Cannot load from file /var/cache/powertop/saved_parameters.powertop
Cannot load from file /var/cache/powertop/saved_parameters.powertop
And I also have 600 and 644 as the respective permissions:
ls -al /var/cache/powertop/
total 120
drw------- 2 root root 4096 Gor 5 23:20 .
drwxr-xr-x 10 root root 4096 Hyd 27 02:01 ..
-rw-r--r-- 1 root root 111460 Hyd 29 22:43 saved_results.powertop
Er... OK. So how did you create a /var/cache/powertop/saved_parameters.powertop?

BUGS: Multiple Undos with Single CMD-Z (and other buggy tales)

BUG #1:
In the SIDs thread (now locked) I said in response to Logic Pro Help, "Hey, after all, Logic ain't that bad". Today I've changed my mind.
In full view of my writing partner, we witnessed numerous times that Logic would undo multiple edits after hitting CMD-Z just once. I've reported this in numerous other threads I've started here on the Apple Forum. I've posted Feedback about it. Naturally, there's been no response from the company.
BUG#2a: we tried to troubleshoot why certain SMPTE-locked regions would unlock (using a key command) and other locked regions on the same MIDI track would unlock.
BUG#2b: while checking to see whether my key command for Unlock SMPTE Position was still intact or not, I went to the key command window and hit cntrl-opt-cmd-U (custom assignment) expecting that the assigned command would scroll into view in the KC window. But I should have known better --- this is one of those key combinations which will NOT cause the assigned command to scroll into view. Sure enough, entering the word "SMPTE" in the search window caused the display to show the Unlock SMPTE Postion command. So why does pressing some keys/key combinations in the KC window show the assigned command while some do not?
And we're supposed to be OK with this kind of behavior?

Hey Cozmicone,
Yes I have done that - I mapped CMD + Z but that kind of gets in the way of years of habit and is a bit frustrating and confusing when you're working quick etc...
It does work fine doing that (I have just uninstalled 3 versions of Photoshop and reinstalled CC 2014 and still no multiple undos on OPT + CMD + Z?! It's like it won't accept the key combination because if you go into map back to OPT + CMD + Z after changing it to CMD + Z it won't let you. You have to revert to default to even get that option back. C'est bizarre...non?

Bug Bug Buggy....LE7.2.3

I'm having some weird issues lately with LE7.2.3, I want to try and describe them here to see if anyone else is having similar issues...
1.While recording a track, LE7 stops drawing the track as I go, it draws it for about 5-10 measures and then looks as if I'm not even recording, just playing back. I've had to stop in mid-take a couple of times to make sure that it's still recording (thus ruining the take), then the rest of the event finally shows up... weird.
2. Random vertical white lines are appearing around the environment window, like little graphic glitches.
3. On certain projects I can't change the name of the track/channel, when I go to edit the track name, I can type in the blue popup box but it doesn't save in the track itself, it just retains the default "track 5" name or whichever.. When I try it again, the name I typed earlier is still in the popup field, but it won't change the name.
Could this be a memory issue? I've never had these issues before the recent update...

Hi dreamsareweird, Questions 1 and 2 are known issues with Logics graphics engine. Do a search on these forums and you'll find many posts talking about it.
As far as question 3 goes, try holding down Option and double clicking the track name to rename it. That's how I do it and it works fine for me. Good luck.
Stootka

Bridge buggy opening file in photoshop CS3

I have totally uninstalled (removing every bit!), re-installed, deleted prefs ad nauseum. If I start CS3 from the application icon (yes it is still in the default folder where I installed it *again* yesterday) all is well. If I try to open a photo from Bridge by right clicking I get two choices: open in Photoshop 10.0.1, or open in Photoshop 10.0.1 (default)
Why does the right click on either choice open a buggy problem? First I'm told the application moved (it didn't and deleting the prefs didn't help) then, whether I chose repair or not, it opens but tells me that all my filters didn't load and it lines my menu bar with at least a half dozen "onOne" menus. Then when I close I get the message that it quit unexpectedly.
I just had to go through a long process (thank you Adobe for the knowledge base!) getting my license to work again. Now I find there is some kind of communication problem between Bridge and CS3.
Maybe that's why Adobe stopped supporting older versions. The program has gotten too big and buggy?
If I drag the file from Bridge to the opened Photoshop (from the application folder) it opens perfectly. Since I have a work around, this isn't crucial, but I really wonder if anyone can explain the communication bug? Not much chance I'll spend the money for an upgrade to CS4. Especially since support will stop as soon as CS5 comes out. CS3 is buggy enough for me.

Anne, with all respect, I differ with you. It's easy to blame the user when problems happen. I happen to be paranoid about maintaining my computer and so far, after switching to my Mac, it is mainly Adobe programs that cause problems, no matter how careful I am. Of course I might avoid problems by never installing useful plugins (and sometimes it is the plugin that causes a problem). Possibly my installation of the OnOne plugins (I really love these) caused this problem with Bridge.
Computers are almost essential; for me one main enjoyment in life is working with my photos. I usually can figure out my problems on my own --learned to do that when I was running Windose :-) but in all fairness there are quirks and bugs that are NOT the user's doing. I figure if I'm not having problems it's luck as well as being careful.
Hoping you won't take offense. The few times I have visited the forums you have been kind and helpful.
Ramón, I will be checking out the Bridge forums from now on. This discussion has probably run it's course. Thank you again.

Screen Mirroring does not work, full of bugs.

Hi,
I've had a Sony Z1 for well over six months now and have got a Sony Bravia TV that supports mircast screen mirroring. When I purchased the Z1 it was on android 4.2 and the screen mirroring worked a treat, it was lag free, always responsive etc.
But when I upgraded to 4.3, the mirroring was buggy as **bleep**, the device always disconnected, when it did connect after several attempts it would lag, black out, then disconnect again. I've tried fiddling with wifi settings as well as wifi direct etc. but no joy and I left it as that.
When I knew 4.4 kitkat was coming to the z1 I waited as I would assume the issue would be fixed, but I upgraded to 4.4 (build: 14.3.A.0.757) today and is still full of these disconnecting and unresponsive bugs. I'm not sure what the problem is, I mirrored a samsung s4 mini and works absolutely fine (4.2) and I can mirror my sony xperia tablet z (4.3) with no issues either. I know a relative who also owns the z1 and has exactly the same issue, what also seems to happen now and then, is that half way through a mirrored session, the wifi would disable and will switch to the mobile network, then after some time, back to wifi again; yet this never happened on 4.2?
Is there a fix or a way to solve these issues? It's rather annoying having such a great feature that doesn't want to work on a flagship.
Thanks.

I had some issues with Miracast on my Z1 but with 4.2 and 4.3 firmware. It was loosing connection or kept saying that I don't have HDCP. I was connecting using Netgear Push2TV.
On 4.4 (.757) it works quite stable. On Z1C with 4.3 I wasn't able to miracast at all.
The same goes with screen mirroring to Z2 tablet. Works fine from Z1 to Z2 (both KitKat, altough one touch pairing is a disaster and not working at all), but you can forget about it using Z1C and Android 4.3.
Best regards,
Sergio PL
Xperia Z1 / Nexus 7 (2012)

Ongoing fatal crash and security bug related to connecting external display

The infrastructures in OS X to resume from sleep, to authenticate, and to change displays is fundamentally not working.
The security bug I have encountered has to do with connecting a cinema display exclusively to a MacBook Pro. This is a specific situation, but please note that I have experienced the same problem on no fewer than three independent laptop. Plus, the Genius in the Apple Retail Store was convinced of the general instability of this infrastructure. The security problem is that hot corners no longer function if I transition between two states in the same reboot. The first state is where I have the laptop powered on and using its own internal display exclusively (when I'm on the road). The second state is when I have the laptop displaying its output exclusively on an external display (when I'm at home). What happens is that an attempt to use hot corners fails. There is no response. I even added configuration on all four corners (whereas I originally had settings only for the rightmost corners), and even then, the hot corner action (of sleeping the display or entering locked screen saver mode) does not commence. This prevents the user from being able to secure the display on demand using standard methods that are supposed to work.
The instability level related to connecting the external display exclusively is high. Again, I've experienced this on no fewer than three independent laptops, and the Apple Genius at the Retail Store confirmed that this aspect of OS X did not work consistently. When I want to connect the cinema display to the laptop in such a way that the laptop's own display is not part of the active screen, the process I use succeeds about half the time. Supposing I have been on the road, where I am using the laptop display exclusively. I then put the laptop to sleep. When I return home with the lid open, I connect first the USB (power) from the cinema display to the laptop, and then I connect the Mini DisplayPort. When that step works, what happens is that the login screen shows on the cinema display despite the fact that my laptop lid is closed. This is good, and is what I want. At that point, I open the laptop lid and quickly log in.
With Apple being a mobile device company, I rely on the laptop for tasks that one traditionally may use a desktop for. This simply points to the versatility of the laptop. But I'd like the bugs resolved, so that I do not have to hesitate to make use of the inherent flexibility possible with the MacBook Pro.
Here's what happens when the process (of connecting the external display in a way that establishes itself as the only screen in use by OS X) fails. Firstly, when I connect the external display via Mini DisplayPort, the laptop doesn't even respond. Instead, it remains asleep. So to work around it I have to repeatedly disconnect and reconnect the Mini DisplayPort so that the asleep MacBook Pro will see that there is a display connected to it. Also, sometimes that isn't even enough and I have to open the laptop lid, and put it to sleep again so as to trigger whatever actions are necessary to recognise the external display (presumably by having the laptop recently awake). Around half the time, I have to play this game of disconnecting and reconnecting until it actually works. This high level of reproducibility (confirmed by the Apple Genius representative's confidence that this part of the system doesn't actually work) should make it easy for an engineer to look into the problem.
Fatally, and recently, OS X has completely crashed when I have attempted to connect the external display. The external display has gone completely blue, and after a half a minute, it blanked out and my entire laptop became unresponsive. I called Apple Support and was given a case number. I also took the laptop into the retail store to see if I could recover my current session without rebooting. There was no process suggested to make that happen and I was told to reboot the machine. I've had this happen before on other laptops, and it is frustrating that the kernel reaches such a state that it cannot be used. As I see it, this problem is not too unrelated to the way that I need to play a game in order to get the external display connected exclusively. Here are some workarounds that could be added:
Firstly, whenever I connect an external display, I'd like the laptop to see that this has happened, and to take action accordingly (such as resuming from sleep). Secondly, If I connect an external keyboard, and press a key on it, I'd like this to wake the laptop too (in the event that the first method fails for some unforeseen reason). I'd also like the connection of the cinema display's USB power not to cause the laptop to enter into a confused state between asleep and awake. Sometimes I need to disconnect and reconnect USB power in order to trigger the laptop into waking, but that's only because it's not doing it on its own properly. On the other hand, I also ensure that the laptop doesn't have the Mini DisplayPort connected without also having the cinema display USB power connected, because that also is an unsupported configuration.
I've also gotten the laptop to become confused about whether it is asleep or awake. When I open the lid, it seems to enter into sleep mode, but closing it seems to bring it into an active state.
Also, I've successfully logged on and authenticated with the screen showing exclusively on the external display. But just ten seconds after I start using the system, the laptop falls asleep--with the lid open! Whatever triggers that action doesn't seem to be on track. The laptop is open, there are incoming events such as mouse movements and key presses, and the external display is on and is in use. And then the laptop falls asleep! This has happened numerous times. Not only should this not happen; the instances where it does happen can cause further instability and put my system at risk of fatally crashing.
Also, the authentication system itself is highly buggy--far more than it should be. At times I have opened the laptop lid and caught a glimpse of a window before I have begun the login process. Also, an external authentication application that asks for Kerberos/AFS login credentials has been able to overlay itself on top of the primary authentication (whereas I should only see a single login dialog when I need to authenticate to the system). Also, I've had several of these authentication screens overlay on top of one another, although it's been months since I've experienced that one (so it may have been fixed). Also, around a third of the time, the window that authenticates me (on the black background) somehow transfers itself into the background (even though there's only one window!). What that means is what I begin to type my password, and now the laptop starts beeping at me and I need to manually click on the password field and begin entering my password again. This really shouldn't happen, and indicates too much complexity in this authentication process (such as, more OS X code is involved than is strictly necessary, which is likely to make the authentication system more difficult to test). Also, at times, I have been using too much CPU, such that the authentication screen takes too long to emerge. That also means that I'm not able to logon until I uncleanly shutdown the laptop. If the laptop has been asleep, and is revived in preparation for login, then that login screen should be given highest priority, even if there are other heavy CPU or I/O intensive tasks running in the background. And maybe the login dialog shouldn't disappear when the user is legitimately attempting to log in. So even if there is a possibility that the system is under heavy resource use (or there is a stall or minor deadlock), it shouldn't prevent the user from logging in altogether.
At the moment, the very fact that the system shut down uncleanly means that the full disk encryption suite that I used has entered into an undetermined state, suggesting I may lose access to all my data. It's my hope that I can rely on Apple's products to interoperate in a way that won't cause me to be fearful and restrictive in my use, so that I can freely connect an external display at times, and at other times carry the laptop on the road.

Ive got the same problem with Samsung UE225010 monitor too, its full hd but it looks terrible, could it be Displayport adapter issue, because couple month ago Ive tryed with some IPS display, and it looked same bad.

Bug - Lightroom 3 - CD/DVD drive corrupted

I have an issue that has been tested and proven to be Lightroom related whereas installing Lightroom, and updating to v 3.3 has caused my cd/DVD RW drive to be lost and corrupted.
The following notes and timeline are a little long, but they fully explain the situation. If anyone has had this issue or knows about a fix I would appreciate a reply:
I will also add that I am a little peeved at the tech for Adobe customer support because he tried to brush me off after a few basic steps and told me the problem was a Windows issue. He said that Lightroom was installed on thousands of PC’s, and if the problem was Adobe’s there would be other people with the same issue… That was a presumptuous statement; as there is always the first case of a bug, and just because I was the first one to either have or report this problem, it did not justify Adobe leaving me cold. There is now a case number on this issue after further testing and my insistence that he escalate the case because I had already determined that it occurred at the precise moment I installed Lightroom. the Adobe Case # is 0181989673
Problem Timeline:
After installing Lightroom 3, I discovered that CD/DVD Re-Writer drive was not working for Lightroom exports, I was seeing the notice at the bottom of theexport window stating “Disc Burning is not supported by lightroom on this computer” (The same as in the V 2.2 Bug)… As well, I looked in Windows > MyComputer, and the CD/DVD RW drive was missing. I looked to the device manager. The CD/DVD Writer was listed in the tree but had a yellow exclamation notice. I Confirmed Error Code (I beleive it was code 31) for Driver not loading properly or corrupted.
I did some research and found the following information at http://support.microsoft.com/kb/982116
I followed the instructions as listed below (inset)... Timeline continued after.
Your CD drive or DVD drive is missing or is not recognized by Windows or other programs:
Problem description;
Your CD drive or DVD drive is missing or not recognized by Windows or other programs, so you cannot play or access a CD or DVD. This issue might have occurred after you installed, uninstalled, or updated a program or Windows Vista.
Windows XP
   1. Click Start, and then click Run.
   2. In the Open box, type regedit, and then click OK.
   3. In the navigation pane, locate and then click the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE 10318}
   4. In the right pane, click Upper Filters.
      Note You may also see an Upper Filters.bakregistry entry. You do not have to remove that entry. Click UpperFilters only.If you do not see the Upper Filters registry entry, you still might have to remove the Lower Filters registry entry. To do this, go to step 7.
   5. On the Edit menu, click Delete.
   6. When you are prompted to confirm the deletion, click Yes.
   7. In the right pane, click Lower Filters.
      Note If you do not see the LowerFilters registry entry, unfortunately this content cannot help you any further. Go to the "Next Steps" section for information about how you can find more solutions or more help on the Microsoft Web site.
   8. On the Edit menu, click Delete.
   9. When you are prompted to confirm the deletion, click Yes.
10. Exit Registry Editor.
11. Restart the computer.
Now go to the "Did this fix the problem?" section.
Did this fix the problem?
Is the drive listed?Windows 7 Click Start , click Computer, and then see wheth...
Is the drive listed?
Windows 7
Click Start
Collapse this imageExpand this image
Start button
, click Computer, and then see whether the drive is listed.
Windows Vista
Click Start
Collapse this imageExpand this image
Start button
, click Computer, and then see whether the drive is listed.
Windows XP
Click Start, click My Computer, and then see whether the drive is listed.
If the drive is listed, try to play or access a CD or DVD.
If you can play or access a CD or DVD, you are finished with this article.
If you cannot play or access a CD or DVD, you may have to reinstall some programs. Some programs might not be able to use your CD or DVD drive until you reinstall those programs. If the problem occurs again when you install or uninstall those programs, contact the manufacturer of the program to see if an update is available that solves the problem. Some examples of programs that might be affected are:
    * iTunes software by Apple
    * Nero software by Nero Inc
    * Roxio Creator software by Sonic Solutions
    * Zune software by Microsoft
After reinstalling your programs, if you can play or access a CD or DVD, you are finished with this article.
After performing above procedures the CD/DVD drive loaded (Plug and Play) successfully and was recognized at a basic level. I re-installed the authoring software (Ashampoo Burning Studio 6). At this time I could read and write to DVD via Ashampoo; but still, I could no longer write to either CD or DVD via Windows XP.
Also at this time; I could still no longer write to CD or DVD via Lightroom 3.3 using export and choosing CD/DVD… Lighroom was still listing at the bottom of the export window “Disc Burning is not supported by lightroom on this computer”.
This brings me to the point at which I called Adobe Support; Case # 0181989673
Adobe tech had me perform the following:
Pull     the preferences folder out of Lightroom 3.3 folder and re-start Lightroom…     Problem still present
Open     Lightroom from the Administrators User account; import a photo and try to     export and burn to CD/DVD… Problem      still present
At this time the tech told me it was a Windows issue; NOT an Adobe issue; and that I would need to take it up with Microsoft, or just export to hard drive and burn to CD/DVD afterward using authoring software.
I immediately told the tech that was NOT acceptable because this issuewas caused by installing Lightroom 3.3; and although the problem now existed in Windows; that did not wash Adobes hands of it. I requested that the case been escalated to a senior tech… I did not at all appreciate the idea of being left in the middle and I also did not appreciate the notion of having a CD/DVD writer that was buggy and not performing as it should.
He told me "Lightroom was installed on thousands of PC’s, and if the problem was Adobe’s there would be other peoplewith the same issue"… To me, that was a STUPID statement; as there is always the first case of a bug, and just because I was the first one to either have or report this problem, did not justify Adobe leaving me cold.
The     tech decided to try creating a new Windows XP user account as     administrator and re-test Lightroom for burning to CD/DVD… Problem still present
Tech     instructed me to un-install and Re-install Lightroom. I un-installed     Lightroom. After taking screen shots of my preference settings (since I     would need to re-set all settings again). I uninstalled Lightroom.
At     this time; though the tech did not think of doing it; I decided to try and     burn to CD/DVD via Windows to see if the problem was gone after removal of     Lightroom. Now, with Lightroom removed, I can write to CD/DVD in the     conventional way using drag and drop via Windows.
I      told the tech what I had done; proving that this was in fact related to      Lightroom. He stated the case would be escalated and gave me the case      number.
I hope this taught the tech a lesson in troubleshooting and hope he will not be so quick to assume “Not an Adobe issue” as the exact cause of this anomaly has not been determined yet... Now I have not re-installed Lightroom yet. I would like for the senior tech who takes this case to contact me to give me further instruction because I have no reason to believe re-installation will not cause me problems again and want the tech to witness the result.

This problem has been resolved. I haven't heard from anyone else who has had the same issue, but in the event anyone does I can say what corrected it and I have a theory of what might have happened. Originally I installed Lightroom from the disk and after installation chose to update. After this is when the problem with the CD/DVD drive showed up. The tech at Adobe said they did not know what could have caused it, but recommended re-installing Lightroom to see if it happened again.
I did some research and found information at Peachpit: Having trouble burning CD/DVDs in Lightroom 2.2?
about a bug that was present in version 2.2 where the installation executable was accidentally installing the 64 bit drivers on the 32 bit system... The 64 bit drivers were corrupting the installation... On a hunch that it could be a similar issue, I downloaded Lightroom version 3.3 from Adobe and installed it rather than installing from the original CD. I did the install following the same instructions on the Peachpit post which was to double-click the Adobe Photoshop Lightroom 2 folder, then double-click the setup32.exe file rather than double clicking the default installation executable.
I did not prove the above theory of the version 2.2 bug to be the cause, but the problem I had with the CD drive appeared after the original installation and went away after I uninstalled that installation of Lightroom. Now after re-installing as explained; the problem is gone.

Buggy Bugs

Similar Messages

Maybe you are looking for