When I try to install on my new computer I just keep getting a dialogue box that says "You cannot install this product on the current operating system". I purchassed Autocad in about January 2011 and have a valid licence. The setup program gives me no other options. I just downloaded the program files rather than buy a hard copy.
inventor 2013 content center won't install in windows 7. Tried everything, used to work in winxp64.I work for Imaginary Menagerie Managers of Imaginary Menageries. You can't imagine how long I've been there.
We have 2011 installed have customized some of the .XSL reports in ProgramDataAutodeskC3D 2011enuDataReportsxsl
After installing 2013, the %ReportDir% variable for 2011 is pointing to the 2013 install, where the reports have NOT been customized. So when you run a report in 2011, it is using the XSL files in the 2013 location.
So the long and the short of it is the 2013 install broke our 2011 custom reporting ability.how to control the %ReportDir% variable in 2011?
i have atocad 2011 installed on my computer (64 bit), a HP Pavilion p6370nl desktop pc, and also have a new videocart: nvidea gt 640, but if start atocad, it starts, and close then. what to do? i already have reinstalled it and also repaired it so...
Just got my new work PC and I'm having issues drawing lines in AutoCAD LT 2011.
Much like other people, circles are fine, as is most everything else. It's just the lines (and who uses lines when drawing things?). So, as you can imagine, my frustration level is to the point where my head is about to explode.
Here are my PC Specs:
Windows 8 Intel Core i7-3770 3.40GHz - 8 CPUS Memory - 16GB Ram AMD Radeon HD 7770 2GB GDDR5 Memory
And this is coming from an old Dell that ran 2011 like a champ, the computer just got old and died.
I can't see any reason, component wise, why the CPU can't handle it, and, since it's just on lines, it leads me to believe it's a software issue where 2011 LT isn't playing nicely with Windows 8 or some other component.
Could it be that it's just time to get with the times and upgrade or is there some workaround?
I updated a working cad station with the lastest pathes. It loaded the new MS Dot Net framework 4. Now Acad crashes if you open it, see below. If you click on an existing drawing it opens and you can work with no problems.
My question is - Is Acad 2011 compatable with the new DotNet 4? The fault module below is DotNet. The old drawings were created using 3.51 DotNet so it looks to me it tries to use the dot net 4 on new drawing.
Problem signature: Problem Event Name: APPCRASH Application Name: acad.exe Application Version: 22.214.171.124 Application Timestamp: 4dbf9c16 [code]...
I have a serious problem when hatching in AutoCAD LT 2011, it's making my PC hang but only when I'm using the 'Add: Pick points' command. It's so bad that I can't even call up the task manager to stop the process and I have to switch it off and on again to get it working.
I've never encountered this before with earlier versions of AutoCAD, is there a way around this? It's driving me nuts!
I'm using AutoCAD LT 2011 on Windows Vista.
Since opening my most recent backup file I think I may have found the cause.
I had inserted a .jpg image (150 x 150 @ 8KB) that I was using to trace around it and it was these tracings that I tried to hatch. I have since deleted the image and now the hatching causes no problems.
I just recently upgraded from WinXP64 to Windows 7 Ultimate 64 and everything is good… aside from the fact that everytime I save the files, it is realy slow
I never had this issue before (although when I think about it, I used to work on another Win7 station a few months ago and I had the same issue)
I think the reason is OS related as everytime I click on save, it “re-creates” the file from scratch… This is not much of a problem on small files… but I have scenes that are over 500MB each and it takes forever to save everytime (not that the scene unreliability is not enough!!!)
I've read that there's a definite way to install CS2 (or any 32 bit version of PS) on Windows 7 64 bit successfully with some folder code "C:progra~2adobe" or C: program~2adobe...or the same code but with the backslashes in the opposite direction like /.
why does the first code say "program" and leave off the "m" and other say to spell out "program" entirely? WHICH is correct "program" or "program" and which way should the slashes go? I saw a member named Marian Driscoll post about this install but don't understand how to do it each step of the way.I need a new PC and was thinking I would be forced to get a used Windows XP machine to use CS2 but would prefer to get Windows 7 64 bit but won't unless I can install PS CS2 on it successfully.
I've read that there's a definite way to install CS2 (or any 32 bit version of PS) on Windows 7 64 bit successfully with some folder code "C:progra~2adobe" or... C:program~2adobe...or the same code but with the back slashes in the opposite direction like /.
I'm totally confused: why does the first code say "progra" and leave off the "m" and other say to spell out "program" entirely? WHICH is correct "progra" or "program" and which way should the slashes go?
How to do this at all so needd install procedure in specific clear steps from inserting the CD to the end?
Can I install and run CS4 products in Windows 8 Pro x64? Windows Upgrade Manager said there was an issue (when reviewing my apps) and sent me to the Adobe site where it seemed to want to point me to a $375 upgrade to CS6.
I had a HD crash recently and I am attempting to re-install PS 7.0 on a new HD with Windows XP Pro. The installation goes flawlessly, but afterwards, when I launch PS, I get an error message that PS cannot initialize because the scratch files are full.
I installed the 30-day trial version of VideoStudio Pro X5 (VSX5_Pro_TBYB.exe (1 431 816 336 bytes) from [URL] on my new Windows 8 laptop. Everything seemed to work fine until i started to experience problems with "hanging splash screen" during start-up. To solve this, I uninstalled VS Pro X5. Now, I am not able to re-install the software.
The installation seems to work OK until the EUL-screen. When checking "I accept the terms...", and pressing the Next-button, nothing happens.
I've tried (with no luck):
* Manually uninstalling/removing according to this
* Created a local new user and tried to install X5 on this
* Checking "zombie" security issues according to this
Don't bother checking the specs on my profile, as this post is about another computer.I just have two questions for now to try and minimize time to correct the problem.
Question 1: Can the VSPro X2 Windows 7 compatibility patch be installed before installing the program?
Question 2: Should compatibility mode be tried before installing a compatibility patch? Or should the compatibility patch be installed first?
Background: I have Service Pack 1 and have already downloaded the VS Pro X2 compatibility patch for Windows 7 (UVS125_Win7_Patch.exe [URL]
I bought VSP X2 a couple of years ago for daughter( living in another location) using Win XP at the time. Now she has Windows 7 notebook, and when she tries to install VSP X2 she gets an error something like this: "application incorrect...xstrace.exe" (I am in process of trying to get exact error message) Device information: Will get if needed.Program version: VSPro X2Patches/updates that have been installed. Daughter has SP1 but not installed yet because she cannot install the main program. As noted above I have downloaded and sent her the Windows 7 compatibility patch, but need to know if she can install it before installing the program.
it isn't possible to install 2.8 alongside 2.6 in Windows (7 x64 in my case) at least using the pre-built windows installer?
The installer for GIMP 2.8.0 will uninstall older versions first, but youcan simply reinstall GIMP 2.6.12 afterwards.
Reason for asking is that there are a number of 2.6 plug-ins I need, and looking at the GIMP plug-in repository few indicate 2.8 compatibility. So I would need to test them myself but if they don't work I would go back to 2.6, at least for some tasks.
Old plugins should keep working - if you find any that don't, report thatas a bug (this includes 32bit plugins running on 64bit GIMP).