VOGONS

Common searches


Reply 40 of 72, by qv90

User metadata
Rank Newbie
Rank
Newbie

Hi I encountered a bug in original Dosbox code, so I created a new patch definition

//
// Name: Bug fixes for DosBox itself
// Version: DosBox 0.70 - 0.1
// Last Update: 2007/06/23
// Created by: Florian Daeumling, Jaballa Software
// Description: Fix bugs in original DosBox code
//
#define PATCH_DOSBOX

in Source code and compiled a new .EXE.

Last edited by qv90 on 2012-11-11, 09:18. Edited 1 time in total.

Jam
Live long and prosper!
http://syncgw.com

Reply 42 of 72, by qv90

User metadata
Rank Newbie
Rank
Newbie

- New Version 1.74

I updated source as well as EXE file to support Clipboard read/write access with more than 32K (32768 Bytes) of text data (now it's hopefully unlimited 🤑)

//
// Name: Enable CLPBOARD as clipboard device
// Version: DosBox 0.70 - 0.2
// Last Update: 2007/07/25
// Created by: Florian Daeumling, Jaballa Software
// Description: Enable read/write access to Windows Clipboard.
// Exit has some limitations:
// 1. Works only on Windows host operating systems
// 2. Supports only text read/write to/from clip board
//
// Howto test: Test can only be performed, if you've enabled
// "PATCH_RWDEV" patch!
// - start notepad.exe
// - copy z:\autoexec.bat clpboard in DosBox
// - switch to notepad and enter <CTRL><V>
// - you should see content of autoexec.bat
// - modify content and mark block; enter <CTRL><C>
// - switch to DosBox and enter copy clpboard c:\test
// - c:\test should contain copied block
//
#define PATCH_CLIPB

Jam
Live long and prosper!
http://syncgw.com

Reply 45 of 72, by qv90

User metadata
Rank Newbie
Rank
Newbie

Hi wd,

oh sorry, it is indeed a bug.

*(strrchr(path,'\\')+1)=0;

is a very buggy code: If path does not contain any "\" it will fail resulting in an memory exception.

To expect "path" will always contains an backslash is erroneous - I know many projects failing because the code expects something which reality does not support.

btw - I'm surprised, not to see such an simple bug fixed in 0.71...

Jam
Live long and prosper!
http://syncgw.com

Reply 49 of 72, by qv90

User metadata
Rank Newbie
Rank
Newbie

Hi wd,

you're absolutely right - I stumbled over my own feet. PATCH_RWDEV skipped some of the code in DOS_Canonicalize()...

Please apologize...

But... I still stick on my opinion: To believe a function does what it should do is risky. I fall into the trap, because I slightly modified DOS_Canonicalize(). Maybe next time someone else of the DosBox project team modifies a function and then your code may fail...

Jam
Live long and prosper!
http://syncgw.com

Reply 52 of 72, by qv90

User metadata
Rank Newbie
Rank
Newbie

Hi bijan_alavi,

Jaballa Edition does not access parallel port itself - it uses the OS provided interfaces to the hardware (available in CMD environment).

Jam
Live long and prosper!
http://syncgw.com

Reply 53 of 72, by qv90

User metadata
Rank Newbie
Rank
Newbie

Hi,

I updated sources to DosBox version 0.72.

- You can find modified sources here
- You can find compiled .exe version here

Please enjoy - and give feedback if something doesn't work 😳

Jam
Live long and prosper!
http://syncgw.com

Reply 55 of 72, by robo456

User metadata
Rank Newbie
Rank
Newbie

This program looks like what I am looking for, but having a little trouble. I have an old GWBASIC program that needs to print to an Okidata ML 320 connected to LPT1.

I downloaded the latest Jaballa Edition 1.81 from your site and used the 'copy %s LPT1 >Nul' as the configuration text. Not sure if that's correct or not for my situation. (running Windows Vista Premium)

If you have any ideas, I'd love to hear them! I really would like to get this program to print!

**EDIT**
I looked at the actual program, and it is trying to use the gwbasic "lprint" command.

--rob

Reply 56 of 72, by qv90

User metadata
Rank Newbie
Rank
Newbie

Hi robo456,

to check if your Basic prog prints in a manner my patch can catch it, try to modify the destination of the output by changing configuration to:

"copy %s C:\Test.prn"

Then start your Dosbox app and try printing. If you see the "1 file copied" message in your DosBox console, check "C:\Test.prn" file size. If it's > 0 then you catched the printer output and your problem is somewhere in the OS printer configuration; if it's = 0, then your Basic prog don't use the "access to device name" way to print (may be it uses interrupts or direct port access for printing).

Jam

Jam
Live long and prosper!
http://syncgw.com

Reply 59 of 72, by mchanna

User metadata
Rank Newbie
Rank
Newbie

QV,

Thanks for investing so much effort into enabling printing in DOSBOX. It's nice that someone has put so much effort on this task. I'm looking to use DOSBOX to support an old medical application that has a few old printers to choose from (like the HP deskjet 630c). I'm familiar with DOSBOX, and have downloaded your complied executable for windows that you posted on your site. I'm hoping you wouldn't mind helping me out by answering a few questions:

1: My goal is to replace an ancient printer with a new one . If I get my app running correctly with DOSBOX, and configure it with the printing app correctly, will it print to a specified default printer in windows (like a modern one XP has installed?)?

2: I'm guessing in order to use your version, you have to copy the files in your DOSBOX181 in place of the ones that might come in a DOSBOX .72 install for windows. Correct?

3: The Dosbox.conf file is not included in your zipped up batch of files, how should that look, in order to support printing.

-Thanks in advance for any input you might have.-