Re: [Freedos-user] Print via USB
Dear Bryan, > My FreeDOS PC's FDCONFIG.SYS file now says this. > Should I put `!' before the BREAK and STACKS statements? That is not necessary. Actually I find it a bit odd that the default config used ! so frequently. Tastes differ :-) Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Print via USB
Oops. I've goofed up by running the last message throught the list. Already. For more than one reason, and going off topic being the least important. Apologies. Such an example of bad taste on my part. I should know better. I'll keep the possible networking follow-ups in private messages. Frankq ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Print via USB
Bryan thanks for your progress reports :-) Nice to see how you have cartographed your local network, and that you're showing quite a bit of understanding. Your existing autoexec looks pretty harmless to me. I don't have any demands on what to put in there, that's why I didn't provide an example. Feel free to tweak the PATH variable to your liking. Let me know if you don't know what the %PATH% is good for. For instance, the pktdrv/start.bat modifies the %PATH% accordingly to fit its own needs = no need to do that in the autoexec. Basically I'd say you're all set to try and load the DOS network stack, and see if that works :-) Again there are two alternative flavours of the DOS TCP/IP stack, one tastes of Microsoft, the other one of "independent open-source stuff" (the CRYNWR packet driver API). This is what you should try next - either A) or B), reboot inbetween A) and B) when you want to switch to the other: A.) the one Microsoft way: cd msnet start ping 10.1.1.1 ping 10.1.1.2 ping 10.1.1.92 B.) the CRYNWR packet driver: cd pktdrv start ping 10.1.1.1 ping 10.1.1.2 ping 10.1.1.92 I suggest that you also try mem /c /p after A) and B) in turns for comparison. Look at the "largest executable program size" at the end of the listing :-) If you get bored before I end up sending further "printing" instructions to you, try tcpdump or Wireshark on the Linux box :-) The output probably won't make much sense to you for a start, but it may open your eyes a little, to how chatty your local network is. Obviously plenty more info is available from me on that topic, and questions are welcome. Only we're getting off topic in this list. Maybe one small thing to test on your Ubuntu box: if you open a terminal window, and type which lpr what do you get? If you get something like /usr/bin/lpr, could you also try this? which lpq lpq -a Explanation: lpr is a command-line program that allows you to copy/send a file to a print queue, locally within your Linux box. The file = print job is expected at standard input. lpq is a print queue "manager" command, for your overview of the jobs being printed, and the queues present in the system. Not sure if your CUPS comes with those utilities included. Frank ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Print via USB
Further, Eric:
I assume you have already added things from the FD_NET
autoexec to your existing autoexec?
Frank's package at this address--doesn't contain "autoexec"!
http://frantisek.rysanek.sweb.cz/FD_NET.zip
Whereas my FreeDOS PC's C: directory has an AUTOEXEC.BAT file. It
contains this.
{@ECHO OFF
SET DOSDIR=C:\FDOS
SET LANG=EN
SET TZ=UTC
SET PATH=%dosdir%\BIN
if exist %dosdir%\LINKS\NUL SET PATH=%path%;%dosdir%\LINKS
SET NLSPATH=%dosdir%\NLS
SET HELPPATH=%dosdir%\HELP
SET TEMP=%dosdir%\TEMP
SET TMP=%TEMP%
SET BLASTER=A220 I5 D1 H5 P330
SET DIRCMD=/P /OGN /Y
SET COPYCMD=/-Y
IF "%config%"=="4" GOTO END
DEVLOAD /H /Q %dosdir%\BIN\UDVD2.SYS /D:FDCD0001
LH FDAPM APMDOS
IF "%config%"=="2" LH SHARE
rem IF EXIST %DOSDIR%\BIN\DOSLFN.COM LH DOSLFN
REM NLSFUNC %dosdir%\BIN\COUNTRY.SYS
REM DISPLAY CON=(EGA),858,2)
REM MODE CON CP PREP=((858) %dosdir%\CPI\EGA.CPX)
REM KEYB US,858,%dosdir%\bin\keyboard.sys
REM CHCP 858
REM MKEYB UK
REM MOUSE
CTMOUSE
SHSUCDX /QQ /D3
REM LH SHSUCDHD /QQ /F:FDBOOTCD.ISO
REM DEVLOAD /H /Q %dosdir%\BIN\UIDE.SYS /H /D:FDCD0001 /S5
SHSUCDX /QQ /~ /D:?SHSU-CDR,D /D:?SHSU-CDH,D /D:?FDCD0001,D
/D:?FDCD0002,D /D:?FDCD0003,D
MEM /C /N
SHSUCDX /D
:END
SET AUTOFILE=%0
SET CFGFILE=C:\FDCONFIG.SYS
alias reboot=fdapm warmboot
alias reset=fdisk /reboot
alias halt=fdapm poweroff
alias shutdown=fdapm poweroff
alias cfg=edit %cfgfile%
alias auto=edit %0
set OS_NAME=FreeDOS
set OS_VERSION=1.2
if exist %dosdir%\bin\fdnet.bat call %dosdir%\bin\fdnet.bat start
if exist %dosdir%\bin\welcome.bat call %dosdir%\bin\welcome.bat}
Which changes have
you applied to load the network things? Any other config
sys or fdconfig sys changes not mentioned in your mail yet?
Note: When FreeDOS finds a fdconfig.sys file, it will use
that and ignore config.sys, but if it does not find one,
it will use config.sys like any other DOS. So it will not
use both files at the same time. Check which one you use.
Eric
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
--
members.iinet.net.au/~kilgallin/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Print via USB
Dear Eric:
feel free to notify the bootablecd.de maintainer that you
would prefer less contrast for the Blinky mascot background
to distract visitors less from reading the text on the page.
Yes, I've sent an e-mail request there.
Indeed ! marks
a line as "always use" while ? marks it as "ask user". Note
that there are a few bugs in the config, which I have listed
in a mail about 1.3rc3 or rc4 recently.
1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG
2?DEVICE=C:\FDOS\BIN\JEMM386.EXE X=TEST I=TEST I=B000-B7FF NOVME NOINVLPG
device=DOS\JEMMEX.EXE X=TEST NOEMS
You could edit the "1..." line above by removing I=TEST NOVME NOINVLPG
to make it match the FD_NET example, while still being menu-driven: It
will still only be loaded when you select menu option 1 at boot.
Other differences worth copying are:
break=off
buffers=30
stacks=0,0
You can add those lines to your config, at any place, but for
readability, I recommend "nearby the old settings for those".
Of course, you remove the "!buffers=20" in the old config.
SHELLHIGH=C:\COMMAND.COM /E:4096 /P
That actually makes a big difference to your old
12?SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT
The old line expects command.com to be in c:\fdos\bin\
while the FD_NET line has it in c:\ so only change the
old line if you want to use the command.com in the new
location.
Also note the different /E: values: They define how
much space you want for environment variables and you may
have to go from 1024 to 4096 if the network config needs
that much space.
My FreeDOS PC's FDCONFIG.SYS file now says this. Should I put `!' before
the BREAK and STACKS statements?
{SET DOSDIR=C:\FDOS
!COUNTRY=061,858,C:\FDOS\BIN\COUNTRY.SYS
!LASTDRIVE=Z
BREAK=OFF
!BUFFERS=30
!FILES=40
STACKS=0,0
!MENUCOLOR=7,0
MENUDEFAULT=1,5
MENU 1 - Load FreeDOS with JEMMEX, no EMS (most UMBs), max RAM free
MENU 2 - Load FreeDOS with EMM386 (Expanded Memory) and SHARE loaded
MENU 3 - Load FreeDOS without drivers (Emergency Mode)
MENU 4 - Load FreeDOS low with some drivers (Safe Mode)
124?DOS=HIGH
12?DOS=UMB
124?DOSDATA=UMB
1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST
234?DEVICE=C:\FDOS\BIN\HIMEMX.EXE
2?DEVICE=C:\FDOS\BIN\JEMM386.EXE X=TEST I=TEST I=B000-B7FF NOVME NOINVLPG
34?SHELL=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT
SHELLHIGH=C:\COMMAND.COM /E:4096 /P}
I assume you have already added things from the FD_NET
autoexec to your existing autoexec?
You are ahead of me! I need to hunt for such unknown magic
--
members.iinet.net.au/~kilgallin/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
