I have inherited a program written in VB 6 that is not working when the user tries to print. I had some ocx files I needed to register (regsvr32), which I found using Process Monitor, but I can't see where this error is coming from. Is it possible to find out what component the program was trying to create? This program was written by someone else and I don't have access to anything but the original setup program. Thanks.
So the issue was not the old program, but something to do with Access. I happened upon some articles dealing with this particular issue, but nothing worked. I had to install Access 2013 32 bit in order to make this work. I didn't really fix the cause of the problem, but I wanted to put this here to point any future sufferers they check Office and their program if they run into a similar issue.
HTH
Wade
I am making a retro text adventure game in Turbo Pascal that will be played in MS-DOS, and I want it to be in the COM file format. I've looked it up and have found nothing on this subject. If you can help me that would be greatly appreciated.
Something other than that, whenever I try to run my program (compiled into EXE) from DosBox it can't run due to "This program cannot be run in DOS mode". Is this because I'm using Turbo Pascal 7 and need to downgrade? Thanks a lot of you can figure this out.
Set your TP7 to target dos, not windows. Note that you might have an Windows only TP product (also known as TPW)
COM files will still be out of your reach, but at least DOS exe files should run in dosbox. Keep in mind that COM files have a 64k limitation, and therefore are of limited interest.
Free Pascal is working on a DOS16-bit Dos compiler that can generate com files directly from (64-bit) Windows, and while it is working, it is not released yet.
As far as I can detect all machines are the same that excelDna is being used on.
On one specific machine I tried to use the code I have created, and ran into an issue. Logically I thought this was odd and instead tried to add a sample file that comes with the download.
So now, I am trying Errors.xll/Errors.dna that come as a sample. The same error occurrs. Therefore to me there is an issue on this specific machine.
The error I am receiving is "a problem occurred while an add-in was being initialized (InitialIntegration failed). The add-in is built with ExcelDna and is being loaded from P:\xlDna\Distribution\Errors.xll"
Has anyone encountered this? Help needed to understand why this is happening as it seems quite opaque to debug.
Hi what solved this for me was moving the xll and DNA to the users c:. Once located on the c: worked flawlessly.
Hope this helps someone else in the future.
I have been looking into the possibility of creating a soft copy(image/EMF file) of everything printed from Windows - for archival purposes. Does anyone know if it is possible to create a hooking DLL that can grab the printed data in such a general way?
A low tech way of solving it might be to install pdf printer driver as the default printer and remove all others and set it up to automatically write all the files to certain directory on the network and then write a tiny app on another computer to monitor that folder for changes and if any new pdfs appear just print them out to a real printer.
Edit: Otherwise there's apparently something called the Print Monitor API. Here's an article that describes using that from VC++ 6 and seems to be pretty much what you want (assuming it's still supported by the OS you use).
Having looked at this problem in more detail the best solution seems to handle it through Spooler notifications in the Win32.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
My printer ran out of black toner and I didn’t have a spare, so I thought it’d be a good idea to “print” documents to .XPS files for now, then print them when the new toner arrives.
So, now I have my toner but I can’t work out how to print the files. I found this great post on Tim Barcz’s blog which seems to indicate I’m not alone.
I can open them and view them in IE, but if I try to print them it either ignores the command altogether or crashes.
I downloaded the XPS Essentials Pack from the Microsoft website and tried to install it, but it refuses to install and keeps crashing with a ten-page error message. Ironically, I would normally print this message out to deal with it.
My “solution” is to open the .XPS files in IE, then screenshot them and paste them into Paint Shop Pro so I can print them as graphics.
As Tim Barcz says in his post that I linked to:
That’s it…simple. What I don’t get is why people are so afraid to embrace new technology?
I have had no problems printing XPS docs from IE. The first thing that comes to mind is what OS are you running, what version of IE, are all service packs installed, etc?
Another option would be to copy the XPS files to a thumb drive (or send over the network) and print from another computer that does not have any issues.
Edit:
Follow up questions...Can you print non-XPS docs? Have you restarted the printer? Is your print spooler messed up?
I have had many instances where I could not print due to a bad print job clogging the spooler. Restart the spooler or restarting your PC usually takes care of this issue.
IE has an issue with printing XPS files to a network printer, is this a network printer?
The short answer to printing XPS is to use the "Microsoft XPS Document Writer".
This 'printer' gets installed when you install Essentials Pack/XPS Viewer on your system. IMHO, it is better to install the former. Note that MS has upgraded the EP from RC to 1.0 sometime back. So, probably, the problem you have is one of using the older EP. Now, downloading and installing the newer EP (i.e. EP 1.0) doesn't work always. The safest bet in this case is to manually uninstall the EP RC Pack, and then install EP 1.0.
Also, remember that you'd probably have to uninstall/upgrade the installed .NET runtime (or reinstall it). Oh, and then there is MS Core XML Services 6.0 that is required for MS XPSDW (the printer I mentioned earlier, remember?) to work. However, a quick look back at MS's site (http://www.microsoft.com/downloads/details.aspx?familyid=993C0BCF-3BCF-4009-BE21-27E85E1857B1&displaylang=en#Requirements) tells us this is supported for upto XP SP2. Check with MS to know if SP3 is supported as well.
In case you manage to get around all this somehow, you'd want to view the output of the prints you fire. I have the IE-tab extension on my browser and I open all XPS files using this one. Recently, however, I've heard that Pagemark has come up with a ff plug-in for viewing XPS files. You might want to check it out (http://www.pagemarktechnology.com/home/xps-test.html).
And of course, check out Wikipedia (http://en.wikipedia.org/wiki/XML_Paper_Specification)!
If you don't want to print to XPS, select another printer as the default one as indicated by previous comments. Also the XPS printer seems to have problems with margins or page size (some information are outside the A4 or too close to border to be printed).
Otherwise, when opening XPS files in IE9, the "File>Print" menu option is disabled. But you can use the keyboard shortcut: Ctrl+P
There are XPS to JPG/JPEG converters all over the web, pick one ;/
I had big problems with the XPS essentials pack, too.
After a lot of research and debugging I found the installation of XPS to be damaged somehow, and just scrapped and reinstalled the whole computer.
Afterwards everything XPS did work like charm.
So my guess would be: your XPS installation is faulty. Fix: reinstall. Workaround: print from some other computer.
With all due respect to the other answers, I believe you're overlooking the most likely cause and the easiest solution. The most likely cause is that the person's default browser is not Internet Explorer. The solution in that case is to open IE and type in the address of the xps file (e.g., C:\Users\Public\Documents\EVIDENCE\groupon.xps
Windows XP SP3, IE6, all up to date AFAIK.
I use Firefox mostly, so haven't updated IE for ages. Maybe IE7 would be more successful.
The point was that XPS is meant to be some kind of PDF-killer, but the difference is that PDF just works, while XPS has been a disaster. I don't mind errors, but I want it to tell me what is wrong, not just say it didn't work, as I can see that from the lack of pages coming out of the printer.
My answer: anytime you need to resort to 'steps' to resolve an issue that normally 'just works' in any other format, you have by definition gone beyond 'just works' to that place where you need to do work to make something 'just work'.