beginner question ...
Hi,
when I try to run the application (even if there is only an empty loop, compile/build are ok) i get the following error:
Unable to connect, Failed to open: MPLABCOMM_INVALID_HANDLE
Same thing this morning on another computer worked without problems.
Any ideas about the problem?
Hardware:
There is a atxmega128a1- based minicomputer with some buttons, display, clock ...
On the programmer is written: JTAGICE mkII
Software:
I use Win7 Professional (both times).
At home I installed Atmel Studio 7, at the other computer was installed AS 6.2 (this is the only difference I recognize)
Thanks for your help
I solved this problem by restarting Atmel Studio 7.
Related
Weird issue here. I have Visual Studio for Mac. My mac is fully upto date on the mac sidel. I have updated to Xcode 12.5. I have selected the check for updates option in VSMac. I see that there are a bunch of updates for xamarin on my mac. I selected for it to update and restart, and then nothing happens. VSMac just closes. I'm assuming I have something on my system that VSMac doesn't like. Is there a way to just get the downloads and manually install them?
Here was the way that I solved the problem. I went and downloaded the various pieces that I knew I had specific problems with. This was VSMac, Xamarin.iOS, and Xamarin.Mac. I downloaded those, and then installed the iOS and Mac versions. Everything was still good. Then I installed the most up to date VSMac. It detected the old versions of Mono, Android, and some other stuff, and downloaded and installed them. Now, my current problem is solved. There may still be others, but this got my immediate problem resolved.
Hopefully, this helps someone else in the future.
I've got the printer driver, P-touch Editor, b-PAC 3.1 and client tools, all 64-bit, downloaded from the Brother website and installed on my 64-bit Windows 7 laptop. The P-touch Editor works/prints fine.
However, b-PAC failed, and none of the samples worked. I debugged the code:
bool b = doc.PrintOut(1, bpac.PrintOptionConstants.bpoDefault);
where b is false. What could be wrong?
I was hitting the same problem, everything appears to work right up to the point where I called "PrintOut", which fails with error 11, "The currently specified printer is not supported".
It turns out the problem I had was with the driver. I had installed the printer driver from the CDROM that came with the label printer. Windows 7 also comes with an "in-box" driver for the printer and in fact this is the one you should install (it's marked with an "LE" at the end).
To fix the problem, all you need to do is go to the "Devices and Printers" dialog, select the printer, right click on it and select "Printer properties", select the "Advanced" tab and click "New Driver". Find the printer in the list that matches yours but with an "LE" at the end and click OK.
Printing is possible with either of the drivers using the P-Touch editor. Odd thing is, "LE" appears to stand for "Light Edition", but the "Heavy" version doesn't work!... strange.
On my Windows 10 x64 machine, I've had a similar issue using Ruby to print through the bPAC SDK (using win32ole). My code worked on another machine, but not mine.
After fighting with this for a long time, I figured out that all was fine and dandy when using the 32 bit version of the bPAC SDK (and Ruby). Don't know exactly what went wrong here, but it might be that the 64bit SDK is just broken.
I had a similar problem, so I added this after the printOut to see which code I was getting.
string sError = doc.ErrorCode
It returned Error 11, which corresponds to "Device is not supported", but the device was a QL-570 which IS supported.
To get it working, I used the following steps:
Side-install the 32bits sdk.
Open your 64bit sample.
Change target configuration platform from "any cpu" to "x86"
Compile
See also: Label printing development using b-pac SDK in a C# application
The important thing is the application that you uses.
If your app is a 32bitapp (inclusive excel) you need the bPAC SDK for 32bit even when they are running on 64-bit Windows OS.
Some printers only support 32-bit b-PAC SDK ver.
(even if you use windows 10 64-bit with Excel 64-bit)
please check:
https://support.brother.com/g/s/es/dev/en/bpac/environment/index.html
I had the same problem (printOut gave me the error code 11).
The error appeared after switching from the printer PT-9800 to PT-P950.
Trying 32 and 64bit did not work for me.
What fixed it was uninstalling the driver of the PT-9800. I found a hint in the b-PAC 3.4 SDK Help in the section Troubleshooting: "if the old label printer will no longer be used, we recommend deleting the printer driver."
Quite a strange problem I have here, I am trying to run the DXUT DirectX 10/11 tutorials from DirectX sample browser. They build fine, but cannot be run in Debug mode, as this triggers the error warning "Failed to create the Direct3D device". This is strange as I can run them in release mode. The strangest thing however is that they use to run in Debug mode, and I swear I changed nothing in the day it ran, and the next day that it didn't. A friend also has the same exact problem, which happened around the same time.
Has anyone ran into this problem and know of a solution, or perhaps know why its happening beyond the obvious, I have a DirectX 11 capable card if you didn't pick that up.
Thanks.
I literally just spent all day trying to fix this exact same problem. Here is the solution which should hopefully fix yours too...
I managed to find this article explaining that a recent update, (26th February 2013 to be exact), caused the older version to mess up:
http://blogs.msdn.com/b/chuckw/archive/2013/02/26/directx-11-1-and-windows-7-update.aspx
That explains why it was working fine a few weeks ago, and now it just suddenly stopped working I guess!
Following their advice, I downloaded a trial version of Visual Studio 2012, and after an hour and a half of installation time, and a system restart, you should have all the new DirectX SDK files that you need.
NOTE: You don't even have to use Visual Studio 2012. The new files should fix your issues for Visual Studio 2010 and older versions I presume!
(Before doing this I also installed all the latest drivers, but I don't think that did anything to help, but it's worth upgrading drivers whenever you can, as that has fixed a similar issue I had before).
Hope this helps!!! :)
Somewhere in your code you probably have something along the line of this
#if defined(DEBUG) || defined(_DEBUG)
createDeviceFlags |= D3D10_CREATE_DEVICE_DEBUG;
#endif
If you do take a look at the D3D10_CREATE_DEVICE_DEBUG; on the msdn you will see this
To use this flag, you must have D3D11_1SDKLayers.dll installed;
otherwise, device creation fails.
You should check that you do have that dll in your system or you should reinstall the DirectX SDK.
The automatic IE10 update is what caused my issue of automatic non support of directx development. Simplest solution is downloading standalone win8 sdk at...
http://msdn.microsoft.com/en-us/windows/desktop/hh852363
The directx debug layer dll has to be updated.
I posted a question on the apple site but someone suggested that I might get a better response on stackoverflow directly since its a visual studio related issue.
I installed parallels on my macbook pro and i installed windows 7 iso via a DVD. at first everything looked fine exception now I am now trying to compile an asp.net-mvc app in visual studio and i get this error over and over
No matter what i click it will eventually progress but this is quite annoying. The same question was asked here but no good answer was given. It almost seems like it think it needs to depend on something from the DVD drive (which it shouldn't)
Can someone please explain why devenv.exe would need the ISO dvd to be connected to my laptop at this point?
after rebooting this problem seems to go away
We bought Delphi XE to slowly upgrade from Delphi 6.
Delphi 6 is well working in Win7/X64.
I installed two virtual machines to test it (I planned three of them, but Virtual PC is not supports X64 guest OS).
1.) Sun VirtualBox 4.x
2.) VMWARE player latest
The guest OS is Win7/X64. Latest SP's, packs are installed.
I set local "area" settings to "english-usa".
I started the installer as admin.
The phenomenon is:
The InstallAware is starting, the progress bar is access the 100%.
After this a new InstallAware Window is starting, but later it disappeared.
Then nothing happens. Sometimes the Windows say (dialog) that setup is not working, will I reinstall it?
The event log is not containing information about the problem.
I tried to starting "setup.exe" directly with "as admin", but the result is same.
I tried to find the real setup files in "Local Settings/Temp", and starting it directly as admin, but I got same result.
So I'm very disappointment, and puzzled... We bought something that is not installable.
May I can install the XE into VPC/XP Mode; but I'm sure the somebody CAN install this software in Win7/X64... :-(
Can anybody help me, how to continue the installation?
How to "debug"?
Thanks for your help:
dd
It might be a problem with your virtual machine, i have myself issues with VirtualBox.
You also should double check if you dont have a corrupted Iso. Try to download it again to see it works.
I work in a software house that have at least 30 people working with Delphi XE on their Windows 7 machines. None of them ever reported a installation crash.
Another good question: are you executing the setup.exe as administrator?
The solution was if I copy the zip file directly into VM (not download it), and I must set ALL AREA FLAGS to USA.
The language, the area, the format settings - all things!
Then the installer simply working...
Thank you for your help!
Regards:
dd