We have encountered a cut-off print issue with DYMO LabelWriter 450 Turbo after we have upgraded to Windows 10. After some investigation we found out that the same issue can occur on some of Windows 8.1 machines as well. We use DYMO.Label.Framework in our program.
We have the following investigation results for now:
Labels are printed correct via DYMO App v8.5.1.1816
Labels with long barcodes or long lines are cut-off, there’s just a half of them is printed
It works if we build the app with .NET framework 3.5
It doesn’t work if we build the app with .NET framework 4.0-4.6
We found some related questions like https://social.technet.microsoft.com/Forums/ie/en-US/4370e2c1-21ad-4b65-a505-8c7696f909b9/dymo-label-barcode-cutoff-on-windows-81?forum=w8itproappcompat or http://developers.dymo.com/2014/01/02/windows-8-1-barcodes/#comment-82838 but no solution has been found yet.
Guys from DYMO confirmed that there is a bug in the .NET Framework that effects the way Microsoft handles printers with “non-square” resolutions (ex.600×300). When graphics are drawn on a label, DYMO prints at this higher resolution instead of the normal 300×300 to help with barcode quality/scanning. They had logged the issue with Microsoft and Microsoft claim to have fixed the problem in .NET 4.6, but we tried it, and it didn't work. DYMO guys are continuing to look into this issue and trying to find workarounds.
Workaround:
As a temporary solution, we've built .NET Framework 3.5 app that prints labels with DYMO.Label.Framework and we use this exe from our main app.
I got my barcodes to print correctly on Windows 10 by redesigning my label with a portrait orientation.
See information here: http://developers.dymo.com/2015/09/30/barcode-printing-issues/
I had the same problem, and found the solution was to install this file DLS8Setup.8.7.2.exe 166,417Kb on all the affected machines, and it worked flawlessly after that. I'm not sure what Dymo has been doing with its drivers as of late, but they are getting worse.
http://download.dymo.com/dymo/Software/Win/DLS8Setup.8.7.2.exe
Related
Pretty much title.
Cursor constantly changes from standby to loading, but other then that the screen stays white.
I have tested it on windows server 2019 and it worked, same goes for my local computer which is windows 10.
I tried building a x32 bit version and it crashed.
There is barely any information on the internet regarding older versions, and the one thread I saw mentioned what Ive tried already.
Can anybody point me to the right direction? I'm kinda clueless right now and trying to compare things like .NET Framework and such (although I'm pretty sure it's not related at all?)
Thanks!
EDIT:
I'm getting an error in the event viewer that theres a faulting modoule, and it is ntdll.dll
going to continue research for now!
Just incase anyone sees this and have a similar issue:
1.The desktop on our citrix server was programmed to be located on a network share and not on a physical hard drive, so I had to move it to the proper folder.
2.The application worked only when I placed it on the local drive, and only as a 32 bit application.
I spent two days basically trying everything on a 64 bit application, because when I tested the 32bit one it just crashed, but it turns out they were two seperate issues which are finnaly resolved!
I'm trying to capture the desktop screen using Windows Magnification APIs based on code sample given in https://www.codeproject.com/Articles/607288/Screenshot-using-the-Magnification-library?msg=5570528#xx5570528xx.
The program (32bit executable) works pretty good on Windows8 and Windows10 but fails on Windows7 OS. I compiled the program into 64bit and the behavior is same even for the sample program mentioned in the above codeproject thread.
After debugging I figured out that the MagImageScalingCallback function returns image width and height as 4*4 instead of my monitor's size and that causes the program to crash or capture a blank screen on Windows7 machines (reference: https://learn.microsoft.com/en-us/windows/desktop/api/magnification/ns-magnification-tagmagimageheader).
All the API calls (MagInitialize, CreateWindow, MagSetWindowFilterList & MagSetWindowSource) are successful. There are no API call failures or mistakes in the code flow in terms of Initializing creating, setting desktop area & assigning filter list.
DWM (Aero theme) is turned off (as per reference: https://learn.microsoft.com/en-us/windows/desktop/api/magnification/nf-magnification-magsetimagescalingcallback)
I couldn't find any resources related to this topic even after researching for about 3 days. I have to use Magnification APIs because I have the need to capture windows that stays behind other windows on the desktop.
Any help would be appreciated.
Update 1:
I figured out that the application is able to capture the screen only when Aero theme is enabled and that contradicts with the statement in https://learn.microsoft.com/en-us/windows/desktop/api/magnification/nf-magnification-magsetimagescalingcallback.
I'm not sure how could I make it work on Operating systems with Aero theme disabled or not available by default.
As the title indicate, i'm trying to port ExpanderView from windows phone toolkit and use it with windows store universal app ie. WinRT. After re-writing all the necessary classes from Phone:Toolkit into my app, I just founded that the Header of the ExapnderView is neither showing in design mode or in debug mode.
Can't find out what is the problem with this. Is there anyone who tried the same thing and have a solution? I attached the the classes so you can take a look on it, if you can.
Expander RT codeplex
Just found out what the problem was. I missed the style xaml that targets the ExpanderView. If anyone is intresseted in this control for WinRT, both windows 8.1 or windows phone 8.1, please pm me and I will send you the files.
EDIT***
You can find the full Project in codeplex using this link ExpanderRT
I searched both the web and stackoverflow and I feel I'm the only one, so probabyl I'm soing something very simple ver wrong.
I run VS11 (2012) on a Win 8 64 machine and everything is nice and neat, the profiler too seems (!) to work as it should just that at the very end he's never able to show any results. I get an almost empty window which say that there are no data to show.
I used the "Sampling"
What i found browsing the web is a MS article saying the "Sampling" (which I used) is not available, which would explain it, but A) the article was about the Win8 preview and B) I also found some people giving nice examples of using the VS11 Profiler on Win 8 (in Sampling), so I know some people got it working. But how ?
I also tried running VS explicitly as Admin but it didnt make a difference. And yes, Instrumentation is working, but thats of no help for our project, we need Sampling.
I am also having this problem (I'm running Visual Studio Ultimate 2012, Windows 8 x64). It seems that if the program runs very quickly (mine runs under a second), there are no results. I decided to make it run for a few seconds and the sampling profile worked. After scouring the internet I have found some unhelpful webpages - but maybe they will report a fix in the future:
A thread on msdn about this issue
http://social.msdn.microsoft.com/Forums/en-US/vstsprofiler/thread/c609d76c-be22-4ffb-858c-73ccab591a78/
A blog saying that you should use Windows 7 to be able to configure anything for sampling (I hoped to be able to turn the sampling frequency down, but that isn't possible).
http://blogs.msdn.com/b/profiler/archive/2012/12/10/the-visual-studio-profiler-on-windows-8.aspx
What can be the cause of my Windows CE 6.0 installation to turn to black screen after initial loading ? I built the Win CE 6.0 myself. After initial screen displaying Win CE 6.0 logo with progress bar reaching 100% the screen turns black.
Is there any way to debug, test or emulate the run time image before deploying.
I have not a real hardware in my development environment to test it.
I just built the image and sent to the client for testing.
I based the Win CE image on Board Support Package from the ICOP company. The target touch panel is ICOP with Vortex86DX chipset.
Every possible, permutation, combination results in black screen. I disabled all debuging techniques (KITL, ... ) without progress.
Please, give mi some advice where and how to find the problem.
Thanks in advance.
For all those who have similar problems as mine I will give the solution that worked for me.
In the Project properties\Building Options must be unchecked everything and specially KITL and all debugging options. In addition the project must be built in Release mode.