Dear gentlemen,
today I've tested some ideas... one worked, one did not.
1) put a UNIX-domain named pipe in the Samba share, locally on the
server:
cd /mnt/samba
mknod print.q p
chmod 666 print.q
The above needs to run as user root.
The following can run as an unprivile
Thanks, Frank:
...while looking for some existing "LPT port redirection software"
for DOS, I've first found this proggie:
I have tried using that. But I found its documentation limited! And I
have not been able to get printing done thereby.
It's a little TSR in .COM format that installs in m
...while looking for some existing "LPT port redirection software"
for DOS, I've first found this proggie:
http://info.elf.stuba.sk/packages/pub/pc/utiltext/lpt2file.zip
It's a little TSR in .COM format that installs in memory, captures
any printing on LPT1 (done using the BIOS printing service
Thanks to Eric for taking a look at my Wireshark screenshot...
I was getting ready to make some PCAP files available, but ultimately
it is not needed, because I already know where the problem is :-)
After some further investigation, it started dawning on me, that this
does look like a bug in Sam
Thanks, Michael:
I hate to even suggest this, but are you using the /B option on the file
copy to indicate that a binary copy is needed?
That didn't fix the printing problem. It's the same with /a. The first
5.1 lines of a text file got printed.
--
members.iinet.net.au/~kilgallin/
__
Just a short update:
I've retreated in my footsteps all the way back to my lab at work,
and its PXE-booted legacy NetBootDisk profile, and I have to say that
the LPT2 obtained via
net use lpt2: \\printserver\queue
misbehaves *exactly* the same as in my minimized VirtualBox
environment, a
Hi Frank,
http://support.fccps.cz/download/adv/frr/dosnet/write_print_file_request.png
This says that, assuming that 192.168.3.54 is your DOS
computer, you got a TCP ACK from the Linux PC (139 to
39183), then SMB tree connect ANDX from the Linux PC,
then a MALFORMED PACKET from the DOS PC for S
This is a re-post, my first two attempts had too many attachments.
I'm re-attaching just the TXT file being printed, and here are some
relevant screenshots:
http://support.fccps.cz/download/adv/frr/dosnet/ps.png
http://support.fccps.cz/download/adv/frr/dosnet/write_print_file_reque
st.png
I'm giv
I hate to even suggest this, but are you using the /B option on the file
copy to indicate that a binary copy is needed? Otherwise, the first Ctrl-Z
in the file will end the file copy prematurely.
On Wed, Jun 16, 2021 at 3:37 PM Frantisek Rysanek
wrote:
> Dear gentlemen,
>
> on and off, with B
Dear gentlemen,
on and off, with Bryan we've been playing with Ubuntu, Samba, CUPS
and the MS Network Client running in FreeDOS. And we're facing a dead
end - same symptoms observed by me and by Bryan:
We can load the MS stack, to the point that we can "net use" network
disk volumes = map a lo
OK, Eric:
https://downloadcenter.intel.com/download/29138/Intel-Ethernet-Adapter-Drivers-for-MS-DOS-
Linux Archive Manager unpacked it!
Maybe you could copy paste a directory listing
of what was in it to the mailing list
{
.
├── APPS
│ └── NVMCHECK
│ └── DOS
│ ├── nvmcheck
On Mon, 26 Apr 2021 at 19:49, Bryan Kilgallin wrote:
>
> Linux Archive Manager unpacked it!
Great!
So, your next step is probably to try to get the MS Network Client.
It's included on all the Windows NT Server CDs.
If I remember correctly, v3.0 includes sharing functionality -- it
makes DOS in
On 4/26/2021 1:53 PM, Thomas Mueller wrote:
roven – Profile: https://about.me/liamproven
I think it might be possible to extraxt a self-extracting archive under DOS or
other OS with UNZIP.
But I see Linux Archive Manager did it for you.
7Zip does it most likely as well...
RAlf
--
This ema
> On Mon, 26 Apr 2021 at 01:21, Bryan Kilgallin wrote:
> > I copied the PRODOS.EXE file to my FreeDOS PC and entered "prodos".
> > Which resulted in this error:
> > "This program cannot be run in DOS mode.".
X-CMAE-Envelope:
MS4wfEiBrDMfwu2ej4M78s5EatnUwGwg+Qn1lpn92MBsnyvNtZKtCm2FPW73sQl
You are right, Liam:
I copied the PRODOS.EXE file to my FreeDOS PC and entered "prodos".
Which resulted in this error:
"This program cannot be run in DOS mode.".
Could be a self-extracting archive. If you have Windows, try running
it under Windows, then copy across the unpacked files. If you d
On Mon, 26 Apr 2021 at 01:21, Bryan Kilgallin wrote:
>
> I copied the PRODOS.EXE file to my FreeDOS PC and entered "prodos".
> Which resulted in this error:
> "This program cannot be run in DOS mode.".
Could be a self-extracting archive. If you have Windows, try running
it under Windows, then cop
Eric Auer wrote:
Intel actually does provide DOS drivers for this chip
(but they say the stopped supporting DOS after 2019)
which contains at least NDIS support. I have not
checked whether it contains a packet driver as well:
https://downloadcenter.intel.com/download/29138/Intel-Ethernet-Adapte
On Sun, 25 Apr 2021 at 10:44, Bryan Kilgallin wrote:
>
> Transmission Control Protocol / Internet Protocol ( TCP/IP ) used
> for instance by UNIX, GNU/Linux, Windows Vista, OS X and the Internet,
We already know it must be TCP/IP. Everything else is obsolete.
> Unfortunately, I don't see a
Sorry, Eric:
PCISCAN showed:
Bus 1
Dev C
Func 0
Slot 2C
Vend 0006
Dev. 100E
Class Name Network
Subclass Name Ethernet.
Correction: the vendor is "8086".
In case the vendor is something else, this might be an
Intel 82540EM Gigabit LAN controller.
You
Hi Bryan,
> PCISCAN showed:
> Bus 1
> Dev C
> Func 0
> Slot 2C
> Vend 0006
> Dev. 100E
> Class Name Network
> Subclass Name Ethernet.
In case the vendor is something else, this might be an
Intel 82540EM Gigabit LAN controller. If 0006:100e is
indeed correct, it i
Hm, Liam:
[1] Find out what network protocol(s) your printer speaks
Device URI: implicitclass://Brother_HL_3150CDN_series/
Make and Model: Brother HL-3150CDN series, driverless, cups-filters 1.27.4
--
members.iinet.net.au/~kilgallin/
___
Freedos-us
Liam wrote:
{[1] Find out what network protocol(s) your printer speaks}
{Protocols
IPv4 ARP, RARP, BOOTP, DHCP, APIPA(Auto IP), WINS/NetBIOS name
resolution, DNS Resolver, mDNS, LLMNR responder, LPR/LPD, Custom
Raw Port/Port9100, IPP/IPPS, FTP Server, TELNET Server,
HTTP/HTTPS server, TFTP clien
Liam wrote:
{[2] Look for DOS support for 1 of those protocols}
FreeDOS protocols:
{The following protocols are supported by these three drivers:
Transmission Control Protocol / Internet Protocol ( TCP/IP ) used
for instance by UNIX, GNU/Linux, Windows Vista, OS X and the Internet,
I
On Fri, 23 Apr 2021 at 00:37, Bryan Kilgallin wrote:
>
> OK, I have plugged-in an Ethernet cable from the DOS PC to my router.
> Now what?
[1] Find out what network protocol(s) your printer speaks
[2] Look for DOS support for 1 of those protocols
[3] Install a DOS network stack that includes tha
As requested, I reply to a private message from Eric Auer.
{As you say that this
printer can also print via network, have you tried to
use that method in DOS? Network drivers are sometimes
easier than USB drivers and you can use "netcat" (nc).}
OK, I have plugged-in an Ethernet cable from the DO
25 matches
Mail list logo
