Installation problem w/Vista

Boot Camp/Vista installation problem
MacBook 2GHz Intel Core 2 Duo, 2GB RAM, Snow Leopard 10.6.2.
Trying to install Windows Vista Home Premium using Boot Camp.
Started Boot Camp Installer and created 32GB partition. Inserted Vista disk as instructed and clicked on Start Installation.
Black screen appeared looking like this:
1.
2.
Select CD-ROM Boot Type: _
That last underline was flashing, waiting for input.
First off, I don't know what to type in, but . . .
The keyboard appears to be disabled because no keystroke registers, nor Return/Enter. Even pressing caps lock or num lock fails to register a light on those keys.
The only way out is to hold down the power key until shutdown, then restart with Eject key depressed to eject Vista disk.
Any suggestions would be appreciated.

Hi RebelGood,
have a look here http://forums.macrumors.com/showthread.php?t=467704 for instructions/solution.
Basically you have to make yourself a copy of your Vista disc using the files of that disc and a programm called oscdimg.exe plus a burning program.
And it had to be done on a Windows PC or in virtualized Windows (using Parallels/Fusion/VirtualBox) on your Mac.
Regards
Stefan

Similar Messages

Post installation problems in vista 32bit

Sir
i am newbie.i installed 10gr2 in my vista,but sometimes its starting perfectly and sometimes not.Then i need to restart my machine and then only i am getting access in sql*plus.i have posted it here but the problem is still the same.[post installation problem its not solved yet|http://forums.oracle.com/forums/thread.jspa?threadID=930824&tstart=0] .
when the command maintained bellow is leaving no output at all.
emctl start dbconsoleIN the service panel is showing dbconsole status as server starting only.
what to do?
regards
Sayantan

Hans F wrote:
1) Vista is not an operating system. It is a family of operating systems. Which operating system within that family are you using?windows 7.
>
2) Oracle Database is designed to work on a server. It should have a static IP address and host name, or at least use a loopback adapter as a workaround. How is the IP address and host name on your Vista-xyz assigned?
using it for local machine in laptop.
HOST = FAXCOOLWAREZ037)(PORT = 1521)
>
Hopefully you are not using DHCP to assign the IP address, or you were sharp enough to install the loopback adapter first.

Installation problem on Vista

I'm unable to successfully get the SOA server up and running on Vista using Oracle database 10.2.0.4.
When starting the SOA or BAM server, the system responds after a while that the server started ok, but the deployments apparently fail.
I have the following questions:
1. I followed the document "Oracle Fusion Middleware Quick Installation Guide for Oracle SOA Suite" 11g Release 1 (11.1.1). The version is Beta Draft: 2009-03-27. Is this the version to use for the April 10 release?
2. When installing, the only problem I saw was during the creation of the ESS schema with RCU. In the installation manual it is not listed as a required schema for BPEL or BAM. Is it ok to ignore this schema?
Below you can find traces of warnings I get in the admin server log.
When the admin server starts up I get
oracle.bali.xml.grammar.GrammarException: Problem loading model for tag file /WEB-INF/tags/TVViewIview.tagx from file:/C:/oracle11
g/user_projects/domains2/soadomain2/servers/AdminServer/tmp/_WL_user/em/jmb4hf/war/WEB-INF/tlds/tv.tld
at oracle.jdevimpl.webapp.taglib.grammar.TldTagFileElement.preReadDocument(TldTagFileElement.java:470)
at oracle.jdevimpl.webapp.taglib.grammar.TldTagFileElement._load(TldTagFileElement.java:328)
at oracle.jdevimpl.webapp.taglib.grammar.TldTagFileElement.<init>(TldTagFileElement.java:80)
at oracle.jdevimpl.webapp.taglib.grammar.TldGrammarFactory.createElement(TldGrammarFactory.java:89)
at oracle.jdevimpl.webapp.taglib.grammar.TldGrammar._getElementMap(TldGrammar.java:377)
at oracle.jdevimpl.webapp.taglib.grammar.TldGrammar._populateElementMap(TldGrammar.java:346)
at oracle.jdevimpl.webapp.taglib.grammar.TldGrammar.<init>(TldGrammar.java:76)
at oracle.jdevimpl.webapp.taglib.grammar.TldGrammarFactory$1._createGrammar(TldGrammarFactory.java:178)
at oracle.jdevimpl.webapp.taglib.grammar.TldGrammarFactory$1.createGrammar(TldGrammarFactory.java:168)
at oracle.jdevimpl.webapp.taglib.grammar.TldGrammarFactory.createGrammar(TldGrammarFactory.java:70)
at oracle.jdeveloper.webapp.taglib.grammar.TaglibGrammarProvider.createTldGrammar(TaglibGrammarProvider.java:74)
at oracle.jdeveloper.webapp.taglib.grammar.TaglibGrammarProvider.addTaglibGrammars(TaglibGrammarProvider.java:51)
at oracle.jdeveloper.webapp.taglib.grammar.TaglibGrammarProvider.addTaglibGrammar(TaglibGrammarProvider.java:42)
at oracle.jdeveloper.webapp.runtime.WebAppDesignContextFactory._createContext(WebAppDesignContextFactory.java:460)
at oracle.jdeveloper.webapp.runtime.WebAppDesignContextFactory.createWebAppDesignContext(WebAppDesignContextFactory.java:1
63)
at oracle.jdeveloper.webapp.runtime.WebAppDesignContextFactory.createWebAppDesignContext(WebAppDesignContextFactory.java:1
28)
at oracle.jdeveloper.webapp.runtime.WebAppDesignContextFactory.createWebAppDesignContext(WebAppDesignContextFactory.java:9
6)
at oracle.adf.share.web.mds.ServletMetadataProvider.init(ServletMetadataProvider.java:33)
at oracle.adf.share.http.ServletADFContext.registerServletContextMDSGrammar(ServletADFContext.java:516)
at oracle.adf.share.http.ServletADFContext.initialize(ServletADFContext.java:401)
at oracle.adf.share.http.ServletADFContext.initThreadContext(ServletADFContext.java:315)
at oracle.adf.model.servlet.HttpBindingRequestHandler.initADFContext(HttpBindingRequestHandler.java:53)
at oracle.adf.model.BindingRequestHandler.beginRequest(BindingRequestHandler.java:102)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:187)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.wls.filter.SSOSessionSynchronizationFilter.doFilter(SSOSessionSynchronizationFilter.java:224)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:139)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:527)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3588)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.IllegalArgumentException: Tag file "/WEB-INF/tags/TVViewIview.tagx" path not starting with /WEB-INF/tags.
at oracle.jdevimpl.webapp.taglib.TaglibUtils.resolveTagFileLocation(TaglibUtils.java:37)
at oracle.jdevimpl.webapp.taglib.grammar.TldGrammarFactory.resolveTagFileLocation(TldGrammarFactory.java:129)
at oracle.jdevimpl.webapp.taglib.grammar.TldTagFileElement.preReadDocument(TldTagFileElement.java:449)
... 51 more
22-apr-2009 9:43:40 oracle.jbo.uicli.mom.CpxUtils$Visitor logMainApplicationCpx
After login in Enterprise Manager I see:
WARNING: Unserializable value:oracle.sysman.core.view.tgtctls.common.DefaultTreeModel@1e054ce for key:UINodePropertyKey[value,17]
PerfFilter: Time taken to render /em/faces/as/as/wlFarmHome: 28432
After login I get repeatedly:
21-apr-2009 9:09:32 org.apache.myfaces.trinidad.bean.PropertyKey saveValue
WARNING: Unserializable value:oracle.sysman.core.view.tgtctls.common.DefaultTreeModel@2a80b2 for key:UINodePropertyKey[value,17]
21-apr-2009 9:09:47 org.apache.myfaces.trinidadinternal.context.RequestContextImpl addPartialTriggerListeners
WARNING: Kan gedeeltelijke trigger pmc_refresh van UIGraph[UIXFacesBeanImpl, id=performance_graph] niet vinden met de ondersteunde
partialTriggers-syntaxis. De gedeeltelijke trigger is gevonden met de afgekeurde syntaxis. Gebruik de ondersteunde syntaxis.
21-apr-2009 9:09:47 org.apache.myfaces.trinidadinternal.context.RequestContextImpl addPartialTriggerListeners
WARNING: Kan gedeeltelijke trigger pmc_refresh van UIGraph[UIXFacesBeanImpl, id=performance_graph] niet vinden met de ondersteunde
partialTriggers-syntaxis. De gedeeltelijke trigger is gevonden met de afgekeurde syntaxis. Gebruik de ondersteunde syntaxis.
JSP Filter: JSP = /as/as/serverHome.jspx
JSP Filter: JSP = /graph/region/performanceMetricChart.jsff
JSP Filter: JSP = /as/as/serverHomeAppDeployments.jspx
JSP Filter: JSP = /ai/sca/soainfra/core/serverComposites.jspx
JSP Filter: JSP = /as/mostRequested/mostRequested.jsff
JSP Filter: JSP = /sdk/templateDefNoForm.jspx
JSP Filter: JSP = /as/sdk/progress/progressRegion.jsff
JSP Filter: JSP = /sdk/globalNavigation.jspx
JSP Filter: JSP = /sdk/topologyNavigation.jspx
JSP Filter: JSP = /service/createService.jspx
JSP Filter: JSP = /events/console/region/blank.jsff
JSP Filter: JSP = /events/console/region/blank.jsff

I also get an error with ESS schema - though a different one than you emailed to me. I'm using XE database and Windows XP.
The document you have for installation is the right one and I agree that you don't need the ESS schema for SOA/BAM.
I don't recognize the error you see in the Admin Server log. Would you confirm this is after the Admin Server is in the RUNNING state and while you are starting the managed server? Are there any errors in the managed server log?
We did have one PM install on Vista and he had to disable ipv6 which is the default on Vista. Here is a forum discussion on it:
SOA Suite for windows vista
You may also encounter the network issue described in the known issues doc (eventually - you don't see the problem until you are deploying your project from jdev).
Let me know if the ipv6 change helps.
Heidi.

Photoshop CS2 Upgrade Installation Problems w/ Vista Problems

I recently purchased a new laptop w/ Windows Vista which I'm trying to install my copy of Photoshop CS2 onto. My Photoshop license is an upgrade license ... originally upgraded from Photoshop v4.0.
When installing an upgrade copy of PS CS2, it requires proof of your previous version in order to verify you're a legitimate upgrader. This works fine if you're upgrading from a version of Photoshop after 5.x ...you simply insert your CD and the installation continues. The installation process is less straight-forward for users like myself ... installing from an upgraded version prior to 5. I'm required to call Adobe ... and conduct a phone verification procedure where I give them a code displayed on the screen during installation and they give me a response code to type into the installation form.
I deauthorized my old laptop ... start the installation routine on my new laptop ... call Adobe w/ my verification code ... enter the response code (which is accepted) and complete the installation without any problems. My problem occurs when I go to run the software. The startup screen indicates that the software is still in "Tryout Mode", and the first window I'm presented with is the "Adobe Activation" window requesting my serial number. If I try to enter my CS2 serial number it is rejected with the message:
"You must enter a valid serial number before activating online or viewing activation options. Please check your serial number and re-enter it, or click the Purchase button to buy a copy of this product"
The thing is ... this IS a valid serial number. I've confirmed this with Adobe. (It's probably an upgrade serial number, which is why the software is rejecting it). I called Adobe and they're now telling me that I must enter a paid-support agreement in order to receive help installing my software. They claim their software is working correctly, and it must be a problem with my computer.
Has anybody experienced a problem like this? I refuse to pay more for something that worked fine on XP just to use it on Vista due to bugs in their installation and activation routine.

function(){return A.apply(null,[this].concat($A(arguments)))}
mthight wrote:
Have the bugs of using with Vista been fixed, or still not working? thanks,
I know this is an old problem, but surely there is an answer to fix the problem by now...
What problems? I used Photoshop CS2 with Vista with no problems (I still have it installed on a Vista system if you'd like me to check anything in particular). CS3 and CS4 worked well as well. Haven't tried CS5 on Vista as I have moved up to Windows 7, but I suspect it works just fine.
-Noel

CS4 MASTER COLLECTION installation problem on VISTA SP1

whenever i try to install CS$ MASTER COLLECTION on VISTA it shows me the following message. . .
http://img132.imageshack.us/my.php?image=83377733oh8.jpg
any solutions? plz help me...........

I get the same problem - any solution yet?
CS4 programs crash at Startup so I unistalled it plus CS4Clease and MS Clean Installer as advised in forums.
only to find the problem is still not fixed
when installing a
Warning message at install stating cs4 minimum system requirements are not met (this did not appear the first time I installed the program)
http://img132.imageshack.us/my.php?image=83377733oh8.jpg
where as CS4 worked for several months, before the error occured
this is the only warning
it then installs CS4 no problem.
after install
Photoshop and Dreamweaver run but the rest of the packages including inDesign do not - they all crash on startup - continously
I have searched the forums endlessly with no avail.
Would a vista update have stopped CS4 from recognising or identifing the OS, thus causing the program to initially crash?
Vista Home Premium SP1, 32bit, Toshiba Qosmio F50, Intel Core 2 Duo P8400 2.26GHZ
please advise

10g and 11g installation problem on Vista Business version

Hi Everyone
I could not get either 10g or 11g database install in my vista business version.
11g Oracle universal installer was running, but many button does not work, like the folder browser and at some stage the program just terminate itself.
10g gave me a total green screen during the universal installer, the window taskbar showed the installer was running.
someone said it is the jre problem but i dont know how to fix it anyway. I tried to remove or update jre in my computer, but nothing get better.
My window has the newest updates. below are the database files i was using from oracle.
11g - win32_11gR1_database_1013.zip
10g - 10203_vista_w2k8_x86_production_db.zip
Could someone help me please, thank you.
Bryan

Please consider opening this as a completely separate question rather than a continuation of an existing, but not quite related, question.
The reasons include:
- each user sees a summary page which reveals the topic of the first question asked - yours is now buried;
- others may wish to contribuite to the original and you have now side-tracked (if not completely derailed) it
- you are able to assign helpfulness points of your own which encourages some to participate in YOUR issue
- it is consideredd normal courtesy in forums

Cap 4 Installation Problem On Vista Machine

I'm having difficulty with a particular Windows Vista
machine. I have two machines that are almost identical - both
Gateways with Windows Vista Enterprise 32-bit OS, both 2 GB of
memory. One has only one hard drive while the other has 2 physical
dirves --- C: and D:. Cap 4 installs and runs OK on the machine
with only one drive. It installs with no fuss on the machine with 2
drives. (I installed both using an account with Admin rights.) But
when I launch the program, it will not open any .cp files. I select
one of the built-in demos, like demonstration.cp, it acts like it
is loading it, the progress bar scrolls across the status bar, the
status bar shows the path of the project, the name of the project
appears in the title bar of the window, but it never opens the
project.
I can create a blank project, then import slides from any
project into the blank one.
When I attempt to record a new project, it sounds like it is
capturing the screens, but when I press the END key, I get an audio
failure. I'm not recording any audio.
When I do attempt to record audio for a slide, when I click
the Settings button, then the Calibrate button, I get nothing.
I compared the install log from one machine to the other. The
only difference I could see was on the machine with two hard drives
I found property settings for D:\, even though I installed to C:\.
The references were:
System64Folder = D:\
ProgramFiles64Folder = D:\
GlobalAssemblyCache = D:\
TARGETDIR = D:\
CommonFiles64Folder = D:\
ALLUSERSPROFILE = D:\
ROOTDRIVE = D:\
All these pointed to C:\ on the machine with only one disk
drive. I have no idea if this makes any difference or not.
And we don't have an Adobe support contract, so I can't ask
them.
Does anyboy have any clues?
Thanks in advance.

Hi Sukalyan,
Greetings from Adobe.
You can go either for Adobe Captivate 7 or Adobe Presenter 9 (which is an addin to powerpoint) which are Flash based interactive elearning tool.
You can download 30 days trial for both the softwares and check if it is what you need.
Captivate 7 :
https://www.adobe.com/cfusion/tdrc/index.cfm?product=captivate
Presenter 9 :
https://www.adobe.com/cfusion/tdrc/index.cfm?product=presenter
Regards,
Mayank

Solution for PS CS3 installation problem on Vista does not work.

I encountered the much discussed 2739 error when trying to install PS CS3 on Vista Ultimate. I followed the proposed solution. But instead of a dialog box I received the message: not recognized. I have the latest update of Java installed and I have IE as my default browser.
What now? Return CS3?

I did and got a friendly guy who apparently had never heard of the 2739 error. I was hoping to get some support here. In another thread I read something about holding the installation window until installation starts. I can try it, but I doubt I am quick enough before the error window opens.

Presenter 8 Installation Problem on Vista Machine

I am installing e-Learning Suite on Vista 32 bit machine, all the software of the suite got installed successfully except the Presenter 8.0. It said some problem with OS version, happenned while installing Presenter. Please help to install this important software.
Kamal K Gupta, PGT Comp. Sc.
Kendriya Vidyalaya Sangathan, India

Hi Sukalyan,
Greetings from Adobe.
You can go either for Adobe Captivate 7 or Adobe Presenter 9 (which is an addin to powerpoint) which are Flash based interactive elearning tool.
You can download 30 days trial for both the softwares and check if it is what you need.
Captivate 7 :
https://www.adobe.com/cfusion/tdrc/index.cfm?product=captivate
Presenter 9 :
https://www.adobe.com/cfusion/tdrc/index.cfm?product=presenter
Regards,
Mayank

Oracle 9i Installation problem on Vista

Hi,
I tried to install oracle 9i in VISTA(as I have only VISTA).But,it is getting errored out on jrewx.exe.I tried many things to overcome this problem and i downloaded many Java and jre files and installed in VISTA and again tried installing 9i on VISTA,but i am not able to install Oracle 9i.
I heard from few of my friends that "VISTA might not support Oracle 9i".
is it true?if VISTA wont support 9i,will it support 10g or 11g??
Also,will VISTA support Oracle Applications 11i??
Thanks,
Ganesh Shankar

Ganesh,
9i is not supported and certified on vista, please see following link for platform certification.
http://www.oracle.com/technology/support/metalink/index.html
Regards

Troubleshoot installation problems in Photoshop Lightroom on Windows Vista

This document can help you to resolve system errors that occur while you use Adobe Photoshop Lightroom on Windows Vista. System errors can manifest in many different ways, including (but not limited to) the following:
A blank or flickering dialog box
A frozen cursor or screen
A blue screen
An unexpected restart
An error message such as:
"Setup is unable to load the installation script file."
"Unable to create a directory under C:\Windows\System. Please check write-access to the directory."
"Uninstalling: C:\Program Files\Adobe\Adobe Photoshop Lightroom refers to a location that is unavailable. It could be on a hard drive on this computer, or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the Internet or your network, and then try again. If it still cannot be located, the information might have been moved to a different location."
Note: If you attempt to install Photoshop Lightroom to a drive that doesn't have the minimum required space available, the installation will fail. You must then completely reinstall to another location that has sufficient free space.
Many different factors can cause system errors, including conflicts among device drivers, applications, operating system settings, hardware, and corrupt elements in specific files. Although a system error may occur only when you work with Photoshop Lightroom, Photoshop Lightroom may not necessarily be the cause; it may be the only application that uses enough memory or processor cycles to expose the problem.
To benefit most from this document, perform the tasks in order. Keep track of the tasks that you perform and the results of each, including errors and other problems. Adobe Technical Support can use this information to better assist you if you need to call.
You must be logged on as an administrator to perform some of the procedures in this document.
Important: Some of the procedures in this document may initiate a User Access Control dialog that asks for your permission to continue. Read the details in the dialog to determine if you want to continue. If you choose to cancel the dialog, then you will not be able to continue with that troubleshooting step.
The steps in this document that refer to the Control Panel are in reference to the Classic view. For information on switching the Control Panel to the Classic view and many other common OS procedures, see Common Microsoft Windows Vista procedures (TechNote kb401275)
Some of these procedures require you to locate hidden files and hidden folders. Some procedures require you to locate files by their full file names, which include extensions (for example, example_filename.ini). By default, Windows Explorer doesn't show hidden files, hidden folders, and file name extensions that it recognizes.
To show hidden files, hidden folders, and all file name extensions in Windows Explorer:
In Windows Explorer, choose Organize > Folder And Search Options.
Click the View tab in the Folder Options dialog box.
In Advanced Settings, select Show Hidden Files And Folders.
Deselect Hide Extensions For Known File Types.
Click OK.
Note: The procedures in this document are based on the default interface of Windows Vista. If the interface is customized, some procedures may vary. For example, a commonly encountered difference is the navigation to Control Panel from the Start menu: You may navigate Start > Settings > Control Panel instead of Start > Control Panel. Additionally, the procedures in this document assume you are using the Classic View of the Control Panel: To view the Control Panel in the Classic View, click Switch To Classic View on the Control Panel navigation bar on the left side of the window.
Beginning troubleshooting
The tasks in this section can help you resolve the most common system errors. Before performing any of these tasks, back up all personal files (for example, Photoshop Lightroom files you created). Always restart the computer after a system error occurs to refresh system memory. Continuing to work without restarting the computer may compound the problem.
1.Make sure that the system meets the minimum requirements for PhotoshopLightroom.
Photoshop Lightroom may not run correctly on a system that doesn't meet the following requirements:
Intel Pentium 4 or equivalent processor
Microsoft Windows XP, Windows Vista, Windows 7
768 MB of RAM (1 GB recommended)
1 GB of available hard-disk space
CD-ROM drive
In addition to these requirements, a video card that supports 24-bit (16 million) or more colors, and a resolution of 1024 x 768 or higher, is recommended.
* Photoshop Lightroom 1.0 will install and run on Windows Vista but Adobe cannot guarantee the quality of the software experience until Adobe fully certifies Photoshop Lightroom for use on Windows Vista.
To check basic system information, such as processor speed and how much RAM is installed, choose Start > Control Panel > System.
2. Delete previously installed application files, especially if you had the public beta version of Photoshop Lightroom installed.
To delete files from a previous Adobe Photoshop Lightroom installation attempt:
Choose Start > Control Panels > Add or Remove Programs.
Select Adobe Photoshop Lightroom and choose to remove it.
Close the Add Or Remove Programs window and the Control Panel.
Open Windows Explorer.
If the Lightroom.exe file is still in the Program Files\Adobe\Adobe Photoshop Lightroom folder, delete it.
If the Lightroom Preferences.agprefs file is still in the Documents and Settings/[username]/Application Data/Adobe/Lightroom/Preferences folder, delete it.
Empty the Recycle Bin.
Try to reinstall. If you cannot, continue with the next two sections in this step:
Move all the folders under the Users/[username]/AppData/Roaming/Adobe/Lightroom folder into a new folder on the desktop; name the folder Lightroom Presets. These are the presets that were installed with the application and that you created.
Move all the folders under the Users/[username]/Pictures/Lightroom/Lightroom Previews.lrdata folder into a new folder on the desktop; name the folder Lightroom Previews. If you have a large number of images, you can move this folder back to its original location before you open Photoshop Lightroom, once it's installed. Or you can delete this folders to re-create it when Photoshop Lightroom opens. If there are further problems with Photoshop Lightroom after it's installed, it might be due to corruption in the previews, in which case you need to delete this folder and re-create it.
Try to reinstall.Important: Do not delete the Lightroom Database.lrdb file!
If there are further problems with Photoshop Lightroom after it's installed, these issues may be due to corruption in the preset files you created, in which case you need to remove them and re-create them, or test each preset individually.
Note: If you can reinstall, and if this is not the first time you opened Photoshop Lightroom, then Photoshop Lightroom will look for a library database file. If it does not find a library in the expected location, it will prompt you to create a new library, locate the library, or exit. Exit will close the dialog box, and Photoshop Lightroom will not open. Although you can tell Photoshop Lightroom to locate your library, it's best to put it back in the default location and then open the application.
If you can reinstall, close Photoshop Lightroom and then copy any presets you created from the Lightroom presets on the desktop back into the Users/[username]/AppData/Roaming/Adobe/Lightroom folder.
If you cannot reinstall, then move the Lightroom Database.lrdb file from the Users/[username]/Pictures/Lightroom folder into a new folder called Lightroom Database File and save this file on the desktop. This is your database, if you previously had Photoshop Lightroom installed.
Reinstall Photoshop Lightroom. If you cannot reinstall, continue with the next task in this document.
3. Log in as Administrator before installingPhotoshopLightroom.
In Windows Vista, you must be logged in with local (that is, machine) Administrator rights to install Photoshop Lightroom. If you don't have administrator rights, contact your system administrator for assistance.
4. Check the CD and CD-ROM drive.
Dust or dirt on a CD can interfere with an installation and prevent the CD-ROM drive from recognizing the CD. Examine the Photoshop Lightroom CD for dirt, dust, or fingerprints. Gently wipe the bottom of the CD from the center outward with a soft, lint-free cloth.
Verify that the CD-ROM drive can read other CDs. If it can't, examine the CD caddy or loading tray for dirt, and clean it with a lint-free cloth. If it still can't read other CDs, contact the CD-ROM drive manufacturer or the computer manufacturer.
5. Install current Windows service packs and other updates.
Updates to the Windows operating system improve its performance and compatibility with applications. You can obtain Windows service packs and other updates from the Microsoft website at www.windowsupdate.com. For assistance installing service packs and other updates, contact Microsoft technical support.
Important: Before you install a system update, check the system requirements for Photoshop Lightroom (and any third-party software or hardware you may use with Photoshop Lightroom ) to ensure compatibility. If the update isn't listed, then contact Adobe or the manufacturer of your third-party software or hardware.
6. InstallPhotoshopLightroomfrom the desktop and use the default installation folder.
Some system components such as device drivers and virus protection utilities can conflict with the Photoshop Lightroom installer and result in an incomplete or failed installation, or they can cause problems when you install to a folder or when you use a path to the default installation folder that contains a special character, such as #. To prevent these conflicts, install Photoshop Lightroom from the desktop, and use the default folder name and path.
If Photoshop Lightroom autoplay displays, click Cancel when you are requested to Select the Language.
Copy the Adobe Photoshop Lightroom folder from the Photoshop Lightroom CD-ROM to the desktop.
Open the Adobe Photoshop Lightroom folder on the desktop.
Double-click the Adobe Photoshop Lightroom.msi file, and follow the on-screen instructions.
7.Re-create thePhotoshopLightroompreferences file.
Re-create the Photoshop Lightroom preferences file to eliminate problems that a damaged preferences file might cause:
Quit Photoshop Lightroom.
Rename the Lightroom Preferences.agprefs file (for example, to Lightroom Preferences.old) in the Users/[username]/AppData/Roaming/Adobe/Lightroom/Preferences folder.
Start Photoshop Lightroom. Photoshop Lightroom creates a new preferences file.
If the problem continues, the preferences file isn't the cause. To restore custom settings, delete the new preferences file and restore the original name of the previous preferences file.
8.Install and run Photoshop Lightroom while no other applications are running.
Some applications may interfere with installing or running Photoshop Lightroom. Virus protection programs are meant to stop viruses from installing on your computer. Before installing or starting Photoshop Lightroom, disable other applications, including virus protection programs and startup items (items that start automatically with Windows).
To disable startup items and non Microsoft services:
Quit all applications.
Choose Start, type msconfig in the Search text box, and press Enter.
Write down all unselected items under the Startup and Services tabs.
Click the General tab, and choose Selective Startup.
Click the Startup tab and select Disable All.
Click the Services tab and select Hide All Microsoft Services.
Select Disable All then re-select FLEXnet Licensing Service. If you are unsure whether an item is essential, then leave it deselected (disabled).
Click Apply, and restart Windows for the changes to take effect.
Note: Upon restart, you'll be notified that the System Configuration utility has made changes to the way that Windows starts up. Click OK. When the System Configuration utility appears, click Cancel.
Right-click icons in the Notification Area and close or disable any startup items that are still active.
9. Install Photoshop Lightroom to a different hard disk after disabling startup items and installing from the hard disk.
Hard disk problems can prevent Photoshop Lightroom from installing correctly. By installing Photoshop Lightroom to a different physical hard disk, you can verify if the original hard disk is preventing installation. First, completely remove Photoshop Lightroom from the hard disk.
To install Photoshop Lightroom to a different hard disk after disabling startup items:
Follow the steps in task 8 above to disable startup items.
If Photoshop Lightroom autoplay displays, click Cancel when you are requested to Select the Language.
Copy the Adobe Photoshop Lightroom folder from the Photoshop Lightroom CD-ROM to the desktop.
Open the Adobe Photoshop Lightroom folder on the desktop.
Double-click the Adobe Photoshop Lightroom.msi file, and follow the on-screen instructions.
Click Change and select a different hard disk in the Change Current Destination Folder window. Click OK, and then follow the on-screen instructions.
Intermediate troubleshooting
If the tasks in the previous section don't solve the problem, try the following intermediate troubleshooting tasks.
10. Install and run Photoshop Lightroom in a new user account.
Create a new user account that has the same permissions as the account that you use when the problem occurs. If the problem doesn't recur, the original user account may be damaged. For instructions on creating a new user account, see To add a new user to the computer in Windows Help or contact your system administrator.
11. Optimize handling of temporary files by Windows Vista.
Windows and applications store working data in temporary (.tmp) files that they create on the hard disk. Excessive or outdated temporary files can interfere with performance of Windows or applications.
Delete temporary files by using the Disk Cleanup utility included with Windows or by using the following instructions. Make sure that at least 1 GB of free space is available on the hard disk to which temporary files are written. To start Disk Cleanup, choose Start > All Programs > Accessories > System Tools > Disk Cleanup. For information about Disk Cleanup, see Windows Help.
To manually delete temporary files:
Note: Windows deletes temporary files when Windows and applications close normally. However, when Windows or an application crashes, temporary files can accumulate on the hard disk. Windows may prevent you from deleting some temporary files as they may be in use. Delete as many temporary files as you possibly can, without deleting the files that are in use.
Quit all applications.
Choose Start and type %tmp% in the Search text box and press Enter.
Delete the contents of this folder.
Note the drive letter where this directory is located.
To ensure that at least 1 GB of free space is available on the hard disk to which temporary files are written:
Choose Start > My Computer.
Select the drive noted in step 4. Right click and select Properties.
Confirm the drive has at least 1 GB of free space.
12. Repair and defragment hard disks.
System errors can occur if hard disks contain damaged sectors or fragmented files. Repair and defragment hard disks, either by using the Error-checking tool and Disk Defragmenter utility included with Windows or by using a third-party disk utility. You should run such utilities on each hard disk or partition. More information about the Error-checking tool and Disk Defragmenter appears below; for more information about a third-party disk utility, refer to the documentation for the utility.
The Error-checking tool repairs bad sectors, lost allocation units and file fragments, cross-linked files, and invalid file names. To access the Error-checking tool, choose Start > Computer, right-click the desired hard disk, and choose Properties from the menu. In the Local Disk Properties dialog box, click the Tools tab, and then click Check Now in the Error-checking area.
Note: To prevent Disk Defragmenter from moving files to bad sectors of a disk, run the Error-checking tool before running Disk Defragmenter.
Disk Defragmenter rearranges the files and free space on your computer so that files are stored in contiguous units and free space is consolidated in one contiguous block. To access the Disk Defragmenter utility, choose Start > All Programs > Accessories > System Tools > Disk Defragmenter.
13. Scan the system for viruses.
Use current anti-virus software to check the system for viruses. Virus infections can damage software and cause system errors. For more information, see the documentation for the anti-virus software.
14. Try to install Photoshop Lightroomon a different computer.
Try to install Photoshop Lightroom on a different computer to determine if the problem is unique to your computer. If the problem is unique to your computer, contact the computer manufacturer; if the problem occurs on multiple computers, contact Adobe Technical Support.
Advanced Troubleshooting
If the tasks in the previous section don't resolve the problem, you may be able to resolve the problem by reinstalling Windows Vista and Photoshop Lightroom, reformatting your hard disk and reinstalling Windows Vista and Photoshop Lightroom, or by determining if hardware is conflicting with Photoshop Lightroom.
Disclaimer: Adobe doesn't support hardware and provides these procedures as a courtesy only. For further assistance, contact the hardware manufacturer or an authorized reseller. If you troubleshoot hardware problems yourself, you may void the warranty for your computer.
Note: Before you remove or rearrange hardware, turn off and disconnect power to the computer and any peripheral devices.
15. Log in using the built-in Administrator account.
The built-in Administrator account has a higher access level to the system than a normal local administrator account. By default the built-in Administrator account is disabled. For information about enabling and logging in to the built-in Administrator account, contact your system administrator. You can also refer to this support document on the Microsoft support website: http://support.microsoft.com/kb/926183/en-us?spid=11737&sid=73.
16. Reformat the hard disk, and reinstall only Windows Vista and Photoshop Lightroom.
Reformat the hard disk, and then install only Windows Vista and Photoshop Lightroom from the original installation media. Reformatting a disk erases all files it contains, so be sure to back up all personal files first. Also make sure that you have all application and system disks.
For instructions on performing a clean installation of Windows Vista, see document 918884, "How to install Windows Vista" on the Microsoft website at http://support.microsoft.com.
Note: Don't install additional software or hardware until you're sure that the problem is resolved. Don't back up the hard disk and restore Windows and Photoshop Lightroom instead of reinstalling them. If the problem is caused by an application or Windows, and either one is restored instead of reinstalled, the problem may recur.
After you reformat the hard disk and reinstall Windows and Photoshop Lightroom, try to re-create the problem:
If the problem no longer occurs, then install other applications one at a time and try to re-create the problem after each installation. If the problem occurs after an installation, then the recently installed application may be the cause.
If the problem occurs when only Windows and Photoshop Lightroom are installed, then the cause may be hardware-related, and you should contact the hardware manufacturer or an authorized reseller for assistance.
17. Check for problems with RAM modules.
Ensure that the RAM modules are installed properly and are not the cause of your problem. Do one or both of the following:
Change the order of the installed modules.
Remove all but the minimum number of modules needed to run Windows and [product], and test to see if the problem persists. If it does, replace the modules you removed and remove the others, testing again to see if the problem recurs. If it doesn't, then one or more of the removed modules are the cause. For assistance, contact the RAM manufacturer.

You've tried Help>Updates from within photoshop cs6?
Or this 8.3 updater
http://swupdl.adobe.com/updates/oobe/aam20/win/PhotoshopCameraRaw7-7.0/8.3.52/setup.zip
If that doesn't work, you can install camera raw 8.3 by following the directions on the following page
Adobe Camera Raw Help | Camera Raw/DNG Converter 8.4 on Mac OS 10.6, Windows XP, and Vista

MSI 975X PROBLEM WITH INSTALLATION ON WINDOWS VISTA

I have MB MSI-975X PLATINUM v.1 withbios ver 1.3,processor Pentium D940 (3,2GHz/800/2x2MB),2X512MB DDR-2 667MHz,in the beginning when I start the installation on WINDOWS VISTA the computer is bloked od it is restart.This problem I solved when I put another processor INTEL 541(3,2GHz/800/1MB) whit this processor everthing is ok,but with INTEL 940 it can not be install WINDOWS VISTA .
I’m asking you for a new superstructure on bios update .

Beta 2 or RC1 candidate???? RC1 should support..........
Beta 2 is real, slow and you have alot of updates to DL, but both are pre-release products and will not work 100%.
Even when Vista is released, they will still be alot of hardware that will not work 100% and this is purely because software is always playing catch up to hardware.
It was only September, when Nvidia released some Beta2/RC1 drivers that worked properly........

SAP WAS J2EE server installation on Windows Vista

Hi Experts,
Is there anything latest on SAP WAS J2EE server installation on Windows Vista. In SDN download section I see SAP NetWeaver 7.01 ABAP Trial Version available with Vista compatibility.
Is there SAP J2EE server also available with Vista compatibility ?
Regards,
Yomesh

> Is there anything latest on SAP WAS J2EE server installation on Windows Vista. In SDN download section I see SAP NetWeaver 7.01 ABAP Trial Version available with Vista compatibility.
>
> Is there SAP J2EE server also available with Vista compatibility ?
The problem with J2EE is the support status of the used JDK. Sun does not support 1.4.2 under Vista/Windows 2008, technically it works.
Markus

What u hear problems in vista 32bit

#What u hear problems in vista 32bit2 I just installed the newer variety of the x-fi notebook card with the wireless broadcast function, and for whatever reason installing the drivers failed the first time, I tried a clean install after that, and the microphone is displayed as not available and what u hear isn't present either, so is there a problem in the driver installation or are those features just non existent in the newer software I also noticed that line in works and the microphone input doesn't, gah, windows fixta is irritating,
EDIT: I found out how to get what u hear to work, I kind of felt stupid but all you have to do is right click in the recording device manager and hit show disabled devices and boom what u hear and the microphone input are there, for what reason I don't know why they were disabled in the first place, but hope this helps anyone with the same problem

+Re: "What U Hear" Missing in Win7G ?
Agreed! I have an X-FI Extreme, upgraded to win 7, installed the latest audio drivers, and have just spent the last 2 hours trying to get my "what u hear" back without any luck at all.
I'll also mention that "disabled devices" are shown in the recording options, so that is not the issue.
I was using vista before with the exact same hardware and "what u hear" was available. The driver version was 5.2..200 dated 4/02/07 ... The current driver for windows-7 is 5.2..208 dated 3/08/2009. Maybe installing an older driver would do the trick? I don't know if that would work as I haven't been able to find the old driver I was using for download (just been bombarded with broken links). I'm also guessing that you'll be held hostage to the latest drivers in windows 7.
Get the latest drivers to lose functionality? Sounds like something apple would pull on you!
If anyone has a solution for this, please let us know, otherwise I'll be rolling all the way back to good old XP again.

CS4 64-bit Installation Problems

I'm installing PS CS4 on Visat 64-bit. The first time I tried installing it the setup stopped when it was loading the Language pack for Device Central. I started the installation over again and removed Device central from the install and then started it again. This time it got almost to the end of install but it then stopped again when it was trying to install the Photoshop CS4 English Language Pack_x64.
Has anyone else loading CS4 had this problem in Vista 64-bit?

Ryan: I feel your pain, after just purchasing CS4 and attempting to install it on my perfectly set up XP x64 system only to find that CS4 was not supported on XP 64bit *sigh* I was reluctantly forced to reformat and switch to Vista (x64)..only to have the exact same problem you are having.
The installer somewhat works as when you install programs individually...eventually you can get what you need installed. However, this is only after running the installer 6 different times to install one app at a time (the installer crashes each time).
The installer crashes at installing "CS4 English Language Pack_x64".
I am installing on a fresh Vista x64 installation on a Mac Pro, all drivers installed properly.

Installation problem w/Vista

Similar Messages

Maybe you are looking for