We just realized that we cannot print correctly our labels, using the **gc420t **printer.
The problem:
All our labels, are printed as if the code instructed it to start on the left of the label, way too far from the label's center. Thus we get labels that are half printed, only what is on the left of the center gets printed. We tried to reinstall everything. We calibrated the printer. But even the test page gets printed in the same way, only the half of the text is shown, and only in the left of the label. All text that starts each row, is truncated in the left side, in the beginning.
The setup process is like:
1. install the printer drives 2. install zebra browser print (zebra-browser-print-setup-1.2.0.3.exe) 3. https://localhost:9101/default?type=printer(link is external) and we accept the certificate
During the process, in abve step #3, of reinstalling the printer, we get the following error:
This CA Root certificate is not trusted because it is not in the Trusted Root Certification Authorities store.
Could someone please with some thorough guidance give us instructions on how we should fix this issue?
Should we set the printer back to its factory defaults?
What drives should we use? What are the latest recommended for windows 10 pcs? (A link would be highly appreciated)
What could be wrong with the certificate? How could one solve this?
What other steps (in detail if possible) one should follow, so as to be able to print the labels like they used to be printed? What is strange and i would like your help, is why without any other modification from our side, labels are miss-printed since yesterday
We have tried reinstalling the printer, calibrating it, but no success.
Related
A user that works in my company has an Error 13 Type mismatch in the moment that she wants to input some data in a grid.
The thing is that when she has that problem, my application only shows the error screen and nothing more (I mean it doesn't say where the error occurs).
I want to know if there is a way that I can "see" the problem in a debug application because I don't have the source code of my application in this computer and I don't know if the problem is because of a Windows configuration issue or why this error pops up provided that when she uses another terminal, different to the one that she normally uses, she can do her job without problems (they have the same settings in the two pcs).
I have the source code in my terminal but as say above, in my terminal the error doesn't pop up so I need to see it in her terminal.
How can I do this?
My apologies to all, if this is in the wrong group.
We’d like to use Fedora 23 in Kiosk mode, but there is was a recently added left edge swipe feature that was added to Gnome Shell (https://github.com/GNOME/gnome-shell)that cannot be disabled easily.
https://github.com/GNOME/gnome-shell/commit/9c4ffc4bf353fe9c64368f3e194e38b0e8f61311
As far as I can tell, our options are:
1) Write an extension to fix this — My favorite
We spoke to the original author, who recommended removing the gesture via an extension.
We have tried writing an extension, but cannot figure out a way to iterate over the gesture list in global.stage to remove it.
(These gestures were added using global.stage.add_action(gesture) and can be removed using global.stage.remove_action(gesture).)
The author has since stopped responding to our emails :(
Any advice on this would be great!
2) Check out the version that we’re on, comment out the code, recompile
and install onto our machines
This sounds great! That way we can fix other bugs also. Looking at the README file
https:// github.com/GNOME/gnome-shell/blob/master/README
It says:
For more information about GNOME Shell, including instructions on how
to build GNOME Shell from source and how to get involved with the
project,
See https:// wiki.gnome.org/Projects/GnomeShell
So, we’ve followed it to this page:
https:// wiki.gnome.org/Newcomers/BuildGnome
And this tells us to check out JHBuild, but we can’t seem to figure out where the gnome shell code is checked out on the machine when we use JHBuild.
If there’s an easier way to make/install, that’d be great. We probably just followed the wrong recommended link.
3) Roll back to an earlier version of gnome shell
But this brings us back to the problem of checking out the gnome shell and make/install as shown in #2.
4) Switch to KDE
We could try KDE instead of Gnome, but we've done lots of testing in Gnome already and could be a major setback.
5) Build a Fedora 22 box to get back to Gnome 3.16 — my least favorite
It’s a huge effort and we can’t be sure what’s changed and what will break. Our Kiosk software may not even run on Fedora 22. But it’s the hail mary back up plan
I work with SciComputing, and, with the help of Florian Müllner, we realized that an extension with the following Javascript code would get rid of the gestures that closed our kiosk window:
/*
* Disable all of the unwanted touchscreen gestures.
*/
function enable() {
global.stage.get_actions().forEach(a => a.enabled = false);
}
/*
* Re-enable the touchscreen gestures.
*/
function disable() {
global.stage.get_actions().forEach(a => a.enabled = true);
}
I have a question, after I have whole built the AOSP source code, it generates couple image files, such as ramdisk.img, recovery.img, system.img, res-package.img,etc .
Right now, I am considering partial flashing my Android Box without formatting all of the system, for keeping some previous data remains.
Therefore, I just tried to use the command “adb sideload filename.img”, which filename might be ramdisk,recovery, etc.
Then, after I did so, the android system shows the message :
“footer is wrong”
“signature verification failed”
“Installation aborted”
There, what should I correct my command, to make the process correct?
as the figure shows enter image description here
And, my methods to do so is trying to refresh a new system feature, but keep the previous data, such as APPs, or user data, remain, does anybody have other good suggestions? Thank you in advance.
it depends on the flash type and file-system you are using, and it is not possible to partially flash in the partition, but you can update the partition.
I maintain a PowerBuilder Classic 12.5 application which has functionality to print checks on a Source Technologies MICR printer. The application has been running fine in a Windows XP environment. We are trying to move to a Windows-7 operating system and the check printing no longer works.
Here is the issue. PowerBuilder issues a PrintOpen followed by several Print commands to send command strings to the printer to unlock MICR mode and various secure fonts:
il_job = PrintOpen( )
Print(il_job,'&%STF[password]$')
Print(il_job,'&%SMCPFFFF$')
Print(il_job,'&%STP10003$')
Print(il_job,'&%STP10002$')
Print(il_job,'&%STP10001$')
Print(il_job,'&%1B$&u600D')
Print(il_job,'&%1B$*t600R')
This works fine on XP, and if you redirect the printer to "print to file", you can see the command strings right there in the file.
In Windows-7, the printer does not recognize the command strings, and in fact, just prints the commands on the check stock. If you do the same "print to file", you can see the commands in there, but each character in the command string is separated by other characters.
The following is a sample taken from the "print to" file, and you can see the string '&%SMCPFFFF$' by looking at each character that precedes an asterisk (*).
*p171Y&*p50X%*p100XS*p150XM*p200XC*p250XP*p300XF*p350XF*p400XF*p450XF*p500X$
This would seem to be a print driver issue, and in fact, Source Technologies now provides a "Universal Print Driver" which we have been told to use. Our PC support person was able to get the check printing working temporarily by re-installing the old print driver that we used on Windows XP, but as soon as the printer is turned off and on again, it resets to the new universal driver.
I tried using PrintDefineFont and PrintSetFont, to set the font to Courier Regular 8pt (which is what the Tech Support guy at Source Technologies told us we needed), but that didn't help:
PrintDefineFont(il_job, 1, "Courier", -8, 400, Fixed!, AnyFont!, FALSE, FALSE)
PrintSetFont(il_job, 1)
Can anyone help me with this issue? Or suggest where I might get help.
Thanks.
Try this: Add a new printer. Select the port your printer is connected to. Select Manufacturer: Generic, Printer: Generic/Text only. When you print to this printer it should send exactly what's in your Print statements to the printer.
Thanks Hugh, I tried your suggestion which sounded good, but unfortunately it had no effect.
As it happens, as of yesterday I did resolve the last of the printing issues. I had to address each of the special fonts (micr line, signature, check amount etc.) individually, and used a combination of using PrintDefineFont/PrintSetFont, embedded printer command strings to reset the font, and changing a Column control in the datawindow to a Text control (a printer command string is moved into this field as well as the data, and the one worked, the other didn't).
Appreciate your help.
Les
Please right click on your software and go to compatibility mode and select "Windows XP with SP3" in it, click APPLY and OK.
Confirm if the software now send print commands perfectly?
When I am programming in Xcode (in C), and I am using the debugging console (brought forth with Cmd-R) to view the program and its output, and give it input, when I am entering input only the first character that I want to input shows up on the console. All the rest are invisible and non-selectable to me. Say I want to enter "20": all that shows up is "2". It still behaves as though I had entered all those characters (in the previous example, 20), so technically this bug (?) doesn't interfere with the actual software, but it's still annoying not to see all of the keystrokes that I had inputted previously. I just updated Xcode a day or two ago and installed Command Line Tools as well (though I doubt the latter is relevant). I believe the version number is 4.3 or so. Is anyone else having the same problem, and has anyone found a fix? Yes, I've tried restarting it.
I have the same problem.
It looks like it's a XCode 4.5 bug:
https://discussions.apple.com/message/19701332?tstart=0#19701332?tstart=0
So, you can wait or install a previous version.