Hi,
On Sun, Jul 20, 2014 at 4:52 AM, Jim Michaels wrote:
> On 7/19/2014 4:20 AM, Rugxulo wrote:
>>
>>> the new alpha cygwin DJGPP compiler's host is I think any version of
>>> windows possibly even x64 cpu -
>>> it must be compiled right now, a binary may be later. the target is still
>>> DOS i
>>> Sent: Friday, July 18, 2014 11:21 AM
>>> Subject: Re: [Freedos-devel] FreeDOS JetDirect driver (was: Getting started)
>>>
>>> On Fri, 18 Jul 2014, Rugxulo wrote:
>>>
>>>> On Fri, Jul 18, 2014 at 10:26 AM, Jim Michaels
>>> wr
Hi,
On Sat, Jul 19, 2014 at 4:45 AM, Jim Michaels wrote:
> - Original Message -
>
>> From: Steve Nickolas
>> To: Technical discussion and questions for FreeDOS developers.
>>
>> Cc:
>> Sent: Friday, July 18, 2014 11:21 AM
>> Subject: Re: [Fr
- Original Message -
> From: Steve Nickolas
> To: Technical discussion and questions for FreeDOS developers.
>
> Cc:
> Sent: Friday, July 18, 2014 11:21 AM
> Subject: Re: [Freedos-devel] FreeDOS JetDirect driver (was: Getting started)
>
> On Fri, 18 Jul 2014,
Or thinking of Andrew Wu's/DM&P's cross compiler script [1]? It would let
you build on Windows for DOS/djgpp.
[1] https://github.com/andrewwutw/build-djgpp
On Fri, Jul 18, 2014 at 11:21 AM, Steve Nickolas wrote:
> On Fri, 18 Jul 2014, Rugxulo wrote:
>
> > Hi, Jim,
> >
> > On Fri, Jul 18, 2014
On Fri, 18 Jul 2014, Rugxulo wrote:
> Hi, Jim,
>
> On Fri, Jul 18, 2014 at 10:26 AM, Jim Michaels wrote:
>>
>> a windows version of DJGPP is in the wings, based on cygwin I think. there's
>> an alpha you can compile with cygwin.
>
> This is so wrong that I don't even know where to begin.
>
> DJG
Hi, Jim,
On Fri, Jul 18, 2014 at 10:26 AM, Jim Michaels wrote:
>
> a windows version of DJGPP is in the wings, based on cygwin I think. there's
> an alpha you can compile with cygwin.
This is so wrong that I don't even know where to begin.
DJGPP only runs on DOS (or similar like NTVDM or DOSEM
:18 PM
> Subject: Re: [Freedos-devel] FreeDOS JetDirect driver (was: Getting started)
>
> Hi,
>
> On Thu, Jul 10, 2014 at 5:30 PM, Jim Michaels wrote:
>>
>> seg:ofs=(seg*16)+ofs=(seg<<4)+ofs (note that it is not bit or, it is
> addition). translation of such an add
ssage -
> From: Michael B. Brutman
> To: Technical discussion and questions for FreeDOS developers.
>
> Cc:
> Sent: Saturday, July 12, 2014 9:17 AM
> Subject: Re: [Freedos-devel] FreeDOS JetDirect driver
>
>
> My understanding of the printer problem leads to beli
On 7/18/2014 4:10 AM, Mateusz Viste wrote:
> Actually, that's exactly what jd.exe does from the wattcp/pprd package,
> too. "Send job to printer or spooler using direct protocol."
>
> http://archives.scovetta.com/pub/simtelnet/msdos/lan/pprd200.zip
>
> Source code is included.
>
> The nice thin
Actually, that's exactly what jd.exe does from the wattcp/pprd package,
too. "Send job to printer or spooler using direct protocol."
http://archives.scovetta.com/pub/simtelnet/msdos/lan/pprd200.zip
Source code is included.
The nice thing is that it uses printer configuration from wattcp.cfg,
On 7/17/2014 1:49 PM, Jim Michaels wrote:
> for the network stufff, I was thinking of opening a socket and just dumping
> the printer data from stdin or from a file depnding on commandline options.
> it'
> s the easiest way to go. sockets is probably about 10-20 lines of code I
> think.
> google
utman
>To: Technical discussion and questions for FreeDOS developers.
>
>Sent: Saturday, July 12, 2014 9:17 AM
>Subject: Re: [Freedos-devel] FreeDOS JetDirect driver
>
>
>
>My understanding of the printer problem leads to believe this is not
>terribly easy.
>
>If ev
>> it's not terribly difficult either. however nobody will program this
>> either :<
> My understanding was that the OP was willing to do some work in this area :)
if OP is 'original poster', then note that this long mail ends with
'well, that's enough food for thought for whoever is getting sta
Hi,
On Mon, Jul 14, 2014 at 12:50 AM, Mateusz Viste wrote:
>
> You should definitely stick to as standard Ansi C as possible, so your
> project would compile
> on pretty much anything. I know some (most?) people here use OpenWatcom,
> since it's free.
> Myself I use rather Turbo C (when doing s
from Rugxulo:
> DJGPP has no "Windows version". It's a pure DOS compiler only. There
> is no Windows support. None is in the works. None was ever made. (I'm
> aware of very very small and obscure and incomplete hacks like RSXNT,
> but those don't count. Or at least haven't counted, even unofficial
Hi,
On Thu, Jul 10, 2014 at 5:30 PM, Jim Michaels wrote:
>
> seg:ofs=(seg*16)+ofs=(seg<<4)+ofs (note that it is not bit or, it is
> addition). translation of such an address is
> I think requires some macros or functions in DJGPP C/C++ compiler which uses
> protected mode (or other
> dos extend
Hi Andy,
> I'm just getting started programming for DOS but have worked a bit with
> different printing languages and would love to get started on a project
> that converts ESC/P to something more modern like PCL or PS on the fly. I
> will definitely need help on the TSR side as I know what they
Hi Andy,
You should definitely stick to as standard Ansi C as possible, so your project
would compile on pretty much anything. I know some (most?) people here use
OpenWatcom, since it's free. Myself I use rather Turbo C (when doing some real
mode things). There is also DJGPP of course, but I th
On Sun, 13 Jul 2014, Andy Stamp wrote:
> Hi,
>
> (Kind of sidetracked from FreeDOS roadmap but seems to belon here...)
>
> I'm just getting started programming for DOS but have worked a bit with
> different printing languages and would love to get started on a project
> that converts ESC/P to some
Hi,
(Kind of sidetracked from FreeDOS roadmap but seems to belon here...)
I'm just getting started programming for DOS but have worked a bit with
different printing languages and would love to get started on a project
that converts ESC/P to something more modern like PCL or PS on the fly. I
will
> I suggested the shelling technique for somebody who wants to experiment
> with hooking the BIOS interrupts but is not ready to tackle the TSR
> portion.
right; also much easier to debug (as you already pointed out)
> "Too big" depends on the program being used; there are many
> programs that
I don't pretend to make judgements on what is "sane" or not sane. I'm
merely pointing out that if the BIOS interrupts are not used then the
task is not feasible. Your point about the viability of NET USE printer
commands is taken, and probably confirms that this is a more than
feasible projec
Hello,
On 07/12/2014 06:33 PM, Tom Ehlert wrote:
> it's not terribly difficult either. however nobody will program this
> either :<
My understanding was that the OP was willing to do some work in this area :)
> *every* sane program used BIOS interrupts to communicate to the
> printer, which coul
> My understanding of the printer problem leads to believe this is not
> terribly easy.
it's not terribly difficult either. however nobody will program this
either :<
> If every program out there uses the BIOS interrupts to send data to the
> printer, then it is pretty easy -
*every* sane program
My understanding of the printer problem leads to believe this is not
terribly easy.
If every program out there uses the BIOS interrupts to send data to the
printer, then it is pretty easy - you install a handler to intercept the
BIOS calls and buffer the outgoing data elsewhere. The outgoing d
e project rolling. I wish I had my DOS dev environment
working!
Jim Michaels
>____________
> From: Mateusz Viste
>To: freedos-devel@lists.sourceforge.net
>Sent: Monday, July 7, 2014 11:37 PM
>Subject: Re: [Freedos-devel] FreeDOS JetDirect driver (was: G
Hi,
I feel this belongs more to freedos-user and not that much to -devel, as
you are having a typical end-user problem, with no development involved
on your part...
About your "network printer under dos" problem, you might want to take a
look into the archive. It is a subject I played with in
28 matches
Mail list logo
