Re: [Freedos-user] VirtualBox and FTP
If you're really concerned about a bunch of other parameters in WATTCP.CFG, the more elegant solution (in my opinion of course) is this: Do my original bat file. At the end of the bat file put this: echo include c:\otherwat.cfg wattcp.cfg Keep all your other stuff in otherwat.cfg ... Most (likely all) of that other stuff is not needed anyway. Dave -Original Message- From: Ulrich my.gr...@mailbox.org To: Discussion and general questions about FreeDOS. freedos-user@lists.sourceforge.net Sent: Sun, Aug 31, 2014 12:15 pm Subject: Re: [Freedos-user] VirtualBox and FTP I am sorry, there were some errors in my previous post: The batchfile has to be called like this in AUTOEXEC.BAT, right after the line DHCP: DHCP CALL C:\FDOS\M2WAT.BAT Otherwise it wouldn't return to AUTOEXEC.BAT. There were also errors in the batchfile itself. I made some changes, now it seems to work. Sorry for the inconvenience. @echo off rem convert MTCP config file to WATTCP format rem 1. Make a backup of WATTCP.CFG copy /y c:\fdos\wattcp.cfg c:\fdos\wattcp.bak rem 2. Preserve the settings of WATTCP.CFG copy /y c:\fdos\wattcp.cfg c:\fdos\wattcp.mtr rem 3. Delete the settings we need to get from MTCP.CFG C:\MTR202B\mt.exe -b- -c -n c:\fdos\wattcp.mtr ^my_ip.*\n = \z C:\MTR202B\mt.exe -b- -c -n c:\fdos\wattcp.mtr ^IP.*\n = \z C:\MTR202B\mt.exe -b- -c -n c:\fdos\wattcp.mtr ^netmask.*\n = \z C:\MTR202B\mt.exe -b- -c -n c:\fdos\wattcp.mtr ^gateway.*\n = \z C:\MTR202B\mt.exe -b- -c -n c:\fdos\wattcp.mtr ^nameserver.*\n = \z C:\MTR202B\mt.exe -b- -c -n c:\fdos\wattcp.mtr ^hostname.*\n = \r C:\MTR202B\mt.exe -b- -c -n c:\fdos\wattcp.mtr \r = \z rem 4. Get the settings from MTCP.CFG copy /y c:\fdos\mtcp.cfg c:\fdos\wattcp.cfg rem 5. First comment out every line with a '#' C:\MTR202B\mt.exe -b- -c -n c:\fdos\wattcp.cfg (^) = # rem 6. Now uncomment the ones we want, add equal sign and change if needed C:\MTR202B\mt.exe -b- -c -n c:\fdos\wattcp.cfg #ipaddr = my_ip= C:\MTR202B\mt.exe -b- -c -n c:\fdos\wattcp.cfg #netmask = netmask= C:\MTR202B\mt.exe -b- -c -n c:\fdos\wattcp.cfg #gateway = gateway= C:\MTR202B\mt.exe -b- -c -n c:\fdos\wattcp.cfg #nameserver = nameserver= C:\MTR202B\mt.exe -b- -c -n c:\fdos\wattcp.cfg #hostname = hostname= rem 7. Remove all lines leftover from MTCP.CFG C:\MTR202B\mt.exe -b- -c -n c:\fdos\wattcp.cfg #.*\n = C:\MTR202B\mt.exe -b- -c -n c:\fdos\wattcp.cfg # = rem 8. Append all the other settings from the original WATTCP.CFG type c:\fdos\wattcp.mtr c:\fdos\wattcp.cfg rem 9. Clean up. del c:\fdos\wattcp.mtr -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VirtualBox and FTP
I suggest that somebody write a small program that takes the current
configuration parameters from the mTCP configuration file and updates a
WATTCP configuration file. It should not be a terribly complicated program -
you just have to do some light string processing.
Here' you go:
/*
M2WAT - Convert mTCP configuration file to WATTCP format.
Copyright (C) 2011 by Cordata
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
This program uses the environment variable MTCPCFG to find
an mTCP configuration file. This file is interesting to the
WATTCP user because it may contain IP address information from
DHCP.
*/
#include stdlib.h
#include stdio.h
#include string.h
#include io.h
#include conio.h
#include ctype.h
#ifdef __WATCOMC__
#define mktemp _mktemp
#endif
#define MAX_CFG 4 /* increase this if more data from mTCP goes to WATTCP */
#define MAX_ALIAS 2 /* increase if a WATTCP parameter has more names */
#define NO_ALIAS
#define LINE_LEN 81
typedef struct cfg_dat
{
char *mtcp_name;/* how does mTCP refer to parameter */
char *wattcp_name[MAX_ALIAS]; /* how does WATTCP refer to parameter */
char mtcp_value[LINE_LEN]; /* what is the mTCP value for parameter */
int written_2_wat; /* has parameter been written to WATTCP file */
} cfg_dat_type;
/* the following table can be used to add items from mTCP to push
into the WATTCP file. To add new items just add entries to this
table. We account for WATTCP having multiple names for parameters.
In particular the IP address can be called IP or MY_IP.
*/
cfg_dat_type cfg_data[MAX_CFG] =
{
{ IPADDR,MY_IP,IP,,0},
{ GATEWAY,GATEWAY,NO_ALIAS,,0},
{ NETMASK,NETMASK,NO_ALIAS,,0},
{ NAMESERVER,NAMESERVER,NO_ALIAS,,0},
};
/* function prototypes */
void adjust_wat_line (char *wat_line, char *dst);
void store_mtcp_line(char *);
void strip(char *);
void usage(void);
void main(int argc, char *argv[])
{
char *mtcp, *wattcp; /* environment variable pointers */
char str[LINE_LEN],w_fname[LINE_LEN],tmp_fname[LINE_LEN];
FILE *m_file, *w_file, *new_w_file;
int l,p,new_file=0;
if (argc != 1)
usage();
if (!(mtcp=getenv(MTCPCFG)))
{
fprintf(stderr,ERROR: must set MTCPCFG environment variable\n);
exit(1);
}
m_file = fopen(mtcp,r);
if (!m_file)
{
fprintf(stderr,Error opening mTCP config file %s\n,mtcp);
exit(1);
}
while (fgets(str,LINE_LEN -1,m_file))
{
str[LINE_LEN -1]='\0';
strip(str);
store_mtcp_line(str);
}
fclose(m_file);
if (!(wattcp=getenv(WATTCP.CFG)))
{
printf(No WATTCP.CFG Environment variable. Using current directory.\n);
wattcp=.;
}
strcpy(w_fname,wattcp);
w_fname[LINE_LEN -1 ]='\0';
l=strlen(w_fname);
if (l (LINE_LEN - 12))
{
fprintf(stderr,ERROR: WATTCP directory too long.\n);
exit(1);
}
if ((w_fname[l-1] != '\\') (w_fname[l-1] != '/'))
strcat(w_fname,\\);
strcpy(tmp_fname, w_fname); /* same directory for temp file */
strcat(tmp_fname,XX);
strcat(w_fname,WATTCP.CFG);
if (!(w_file=fopen(w_fname,r)))
{
char ch;
printf(WATTCP config file %s does not exist.\n,w_fname);
printf(Do you want to create it? (Y/N));
do ch=toupper(getch());
while ((ch != 'Y') (ch != 'N'));
if (ch == 'N')
exit(0);
new_file=1;
}
if (!mktemp(tmp_fname))
{
printf(Error: Unable to create temporary file.\n);
exit(1);
}
new_w_file= fopen(tmp_fname,w);
if (!new_file)
{
while (fgets(str,LINE_LEN -1,w_file)) /* read lines from WATTCP file */
{
char buf[LINE_LEN];
str[LINE_LEN -1]='\0';
strip(str);
adjust_wat_line(str,buf); /* add mTCP info to line, comment out or do
nothing*/
fprintf(new_w_file,%s\n,buf); /* write to new file*/
}
fclose(w_file);
}
/* now check to see if we missed anything */
for (p=0;pMAX_CFG;p++)
if (( cfg_data[p].written_2_wat==0) strlen(cfg_data[p].mtcp_value))
fprintf(new_w_file,%s =
%s\n,cfg_data[p].wattcp_name[0],cfg_data[p].mtcp_value);
fclose(new_w_file);
unlink(w_fname);
rename(tmp_fname, w_fname);
printf(\nWATTCP.CFG updated successfully.\n);
exit(0);
}
void store_mtcp_line (char *mtcp_line)
{
/* this function will parse the input line from the MTCP file. First it
checks if the line contains something interesting and if so it stores
the value in our data structure */
int parm;
char
Re: [Freedos-user] VirtualBox and FTP
For those who want a DIY conversion of MTCP DHCP to WATTCP, you can do this: Step 1: Install minitrue on your PC. mt.exe ... google it. (I think it's idiotsdelight.net or something) Step 2: Create a batch file called M2WAT.BAT Put this stuff in the batch file: @echo off rem convert MTCP config file to WATTCP format copy mtcp.cfg wattcp.cfg rem first comment out every line with a '#' mt -b- -c -n wattcp.cfg (^) = # rem now uncomment the ones we want, add equal sign and change if needed mt -b- -c -n wattcp.cfg #ipaddr = my_ip= mt -b- -c -n wattcp.cfg #netmask = netmask= mt -b- -c -n wattcp.cfg #gateway = gateway= mt -b- -c -n wattcp.cfg #nameserver = nameserver= mt -b- -c -n wattcp.cfg #hostname = hostname= Step 3 Run it after MTCP DHCP. Dave -Original Message- From: Michael Brutman mbbrut...@brutman.com To: Discussion and general questions about FreeDOS. freedos-user@lists.sourceforge.net Sent: Tue, Aug 26, 2014 10:53 am Subject: Re: [Freedos-user] VirtualBox and FTP David Dunfield has a utility called DHCP that will work with both mTCP and WATTCP. I've not tried it, but David is well known in vintage-computer circles and his software is supposed to be pretty good. http://www.classiccmp.org/dunfield/dos/index.htm Mike -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VirtualBox and FTP
mTCP vs wattcp.cfg - I agree this would be awesome if mTCP could read/write WatTCP config files for backward compatibility :) Step 1: Install minitrue on your PC. mt.exe ... google it. Step 2: Create a batch file called M2WAT.BAT Put this stuff in the batch file: @echo off rem convert MTCP config file to WATTCP format copy mtcp.cfg wattcp.cfg rem first comment out every line with a '#' mt -b- -c -n wattcp.cfg (^) = # rem now uncomment the ones we want, add equal sign and change if needed mt -b- -c -n wattcp.cfg #ipaddr = my_ip= mt -b- -c -n wattcp.cfg #netmask = netmask= mt -b- -c -n wattcp.cfg #gateway = gateway= mt -b- -c -n wattcp.cfg #nameserver = nameserver= mt -b- -c -n wattcp.cfg #hostname = hostname= Run it. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Newbie Q - How do I get a USB flash drive operating please?
My advice to anyone trying to use a USB storage device on FreeDOS is to first try using the BIOS. First realize that USB drives will be FAT 16 for smaller devices (1G or less) and FAT32 for larger devices. So find a device which is small or make sure you are using the FAT32 enabled FreeDOS kernel. (You can check whether the device is FAT16 or FAT32 in Windows easily) Second make sure the BIOS on your computer is up to date - if possible get the newest version and flash it. Third, just insert the USB stick into the computer and boot FreeDOS. See what happens, try to access drive D: ... you may be pleasantly surprised. The stories that you must boot from the USB drive in order for the BIOS to see it are not true in my experience. If this works, you are done, just realize you must boot the computer every time you insert the USB device. If it doesn't work, you are going down the path of exploration that you're doing now. There are some folks on this list that know quite a lot, you might try either Bret Johnson's drivers or Georg Potthast's. Dave -Original Message- From: Andrew Robins arob...@fastmail.fm To: Freedos-user Freedos-user@lists.sourceforge.net Sent: Sun, Feb 3, 2013 2:20 am Subject: [Freedos-user] Newbie Q - How do I get a USB flash drive operating please? I'm stumped I'm afraid - how do include the requisite instructions in fdconfig.sys (and? autoexec.bat) to have USBUHCI and USBDRIVE resident and functional in a fresh Freedos 1.1 install? I'm in the process of constructing small DOS games environment on a 2Gb sd-card drive (IDE adapter). The eventual 'home' for the card is in an old 430CDS Satellite Pro laptop (48 MB RAM), but I've housed it in a desktop with an Asrock K7S41GX mbo and 2GB RAM, for testing of game installs. The card is re-formatted with the freedos1.1 iso CD to FAT32, and I performed a basic install of the OS without GUI and networking extras. For installing games it occurred to me that I could test the games that I downloaded on to my main Linux box straight to a flash drive. But what I thought should be really straightforward, I'm finding isn't. I see that Bret Johnson's USB drivers are included in the install, but I can't seem to get it working... UPDATE: OK I'm running in FreeDOS commandline and typing usbhosts gives me 3 OHCI ports. Going to C:\FDOS\DOC\DOSUSB and editing* (see below) READ.ME I see that I have backed the wrong horse and only UHCI ports are currently viable. Seems like I might have to go with a 3rd party like DUSE 4.4, if nobody would like to give me an alternative approach? So this little excursion has taken me quite a bit longer to get around than I hoped. I have a couple of questions from a noobs perspective - 1) I seem to recall (?) 'type' and 'write' commands in previous DOS versions that could be used with a given switch to print to screen a large document page-by-page. What is the trick to do this in commandline FreeDOS? I find I have to use EDIT to read text over a page long - and EDIT won't let me read large files like USBINTRO.DOC. 2) How do I see error messages that flip off-screen during bootup? I had a few memory allocation error messages when trying to get USBUHCI.com and USBDRIVE.com loaded in FDCONFIG.SYS using either install c:\fdos\bin... or device=c:\fdos\bin... approaches. Had to film the bootup with my smartphone and take a snapshot to read the apparent memory conflict (? red herring- no uhci) with JEMMX, EMM386 and XMGR bootup options. Is there a log file generated somewhere for such error messages? 3) rather than muddle from a commandline level, is there a file manager that could be recommended to new users to DOS, for retrieving background docs etc? I've tried DOSSTART and even Arachne seemed to have that feature... what are the possible alternatives? 3) Are there any intentions to automate fdconfig and autoexec file updates? When installing different modules from the options menu on the FreeDOS CD, it would be nice to have the respective devices implanted at the optimum position in the fdconfig.sys file... that is probably an insurmountable wish, however.. Seems like I'll have to go with a 3rd-party option like USBASPI.SYS from Panasonic (http://www.computing.net/answers/dos/usb-driver-for-dos-usbaspisys/15568.html) or DUSE 4.4 (http://www.tecumsehconsulting.com/usb.htm). I seem to recall that Eric Auer had packaged some likely prospects for USB in DOS together somewheres, will have to back-track. Any suggestions on the matter would be gratefully accepted - including perhaps some example fdconfig.sys and/if autoexec.bat line inclusions that work for others in the OHCI boat. Thanks. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan ___ Freedos-user
Re: [Freedos-user] hunting a program?
Karen, If by getting old hardware on the internet you mean successfully connecting old hardware to the internet then you may be referring to Mike Brutman and his networking package mTCP. If on the other hand by getting old hardware on the internet you mean someone who buys stuff from ebay or craigslist I'm unsure... Dave -Original Message- From: Karen Lewellen klewel...@shellworld.net To: freedos list freedos-user@lists.sourceforge.net Sent: Tue, Dec 18, 2012 10:04 pm Subject: [Freedos-user] hunting a program? HI folks, I have seen it referenced a few times here, although the last incident I remember was not on this list. it is a networking /Internet package, and its creator prides himself on getting very very old hardware on the Internet. Anyone remember the name? thanks, Karen -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FDNPKG: FreeDOS network package manager
is the WatTCP program doing something anti-social like calling exit and killing the program outright? WATTCP programs generally start by calling sock_init() Sock_init() will exit the program if a packet driver is not found. If your program might have some useful purpose without TCP/IP services then you can call sock_init_noexit() Dave -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] vmware and dos drivers
George, Where is the printer physically located? Is it an LPT port on the host PC? If so why not configure VMWare to use a physical LPT port? Alternatively VMWare can be configured to send print information to a file which you could then send to a network printer from Windows. Dave -Original Message- From: George Brooks truckeetr...@yahoo.com To: Eric Auer e.a...@jpberlin.de; freedos-user freedos-user@lists.sourceforge.net Sent: Thu, Sep 20, 2012 9:55 pm Subject: Re: [Freedos-user] vmware and dos drivers Well, I've reached the conclusion that I can't get there from here. Even with a seemingly bootable floppy image (using FreeDOS to format the VMWare Player blank floppy image specified in the vm's setting then copying netbootdisk.com's files to that floppy) I get stuck. Boot hangs at the line install=NetBoot\tunz.com -o NetBoot\boot.zip N:\ with the screen displaying only RDISK 11-27-2009. 8-MB Memory. I even tried modifying the FreeDOS boot menu, adding option 5 to run the commands from netbootdisk.com, but pointing to files on C:. Stepping this way failed at the equivalent tunz line, only with the additional error Inflating N:\command.com Incorrect DOS version I tried three different versions of command.com: From XP's \i386, from Bart's network boot disk, and the one added when formatting FreeDos. Each was placed in boot.zip. None worked. I'm glad to know that others have been successful getting an MSClient to work in FreeDOS running in VMWare Player. I'm just not in that happy band. Georeg From: Eric Auer e.a...@jpberlin.de To: George Brooks truckeetr...@yahoo.com; freedos-user@lists.sourceforge.net freedos-user@lists.sourceforge.net Sent: Thursday, September 20, 2012 12:32 PM Subject: Re: vmware and dos drivers Hi! Here are some network boot disk images: http://veder.com/nwdsk/ http://www.netbootdisk.com/download.htm http://www.nu2.nu/bootdisk/ Somehow they seem not linked on http://www.freedos.org/links/ but that page also is shorter than I had remembered (with many ... now?) The networkbook65.iso failed on my virtual machine so... Details? I searched for a floppy image of the netbootdisk without success so... See above :-) Eric -- Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to do networking from Win7 to FreeDOS and other stuff
Derp, First, I suggest you put the text into your email that you want people to read rather than making them click on a link - you will get more responses. Second, I personally would recommend VMWare player in this case over Virtual Box. Use the VMSMOUNT program by Eduardo Casino and you will get exactly what you are looking for. Others will give you different advice. Dave -Original Message- From: Derp 1223...@gmail.com To: freedos-user freedos-user@lists.sourceforge.net Sent: Fri, Sep 14, 2012 8:06 pm Subject: [Freedos-user] How to do networking from Win7 to FreeDOS and other stuff I was told to go here from the Virtualbox forum https://forums.virtualbox.org/viewtopic.php?f=4t=51549p=236044 -- View this message in context: http://old.nabble.com/How-to-do-networking-from-Win7-to-FreeDOS-and-other-stuff-tp34435540p34435540.html Sent from the FreeDOS - User mailing list archive at Nabble.com. -- How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Serial port or USB/PCMCIA modem support
You don't say whether you want to run FreeDOS on the bare metal or in a VM. My suggestion would be that if you already have Windows on your laptop it's quite easy to run FreeDOS in a VM, then you can connect the USB port using Windows and set it up as COMx inside the VM, then you don't need to worry about DOS drivers for USB. If you are writing your own application I suggest using a FOSSIL driver like BNU inside the FreeDOS environment rather than re-inventing the wheel of interrupt-driven communications. Dave -Original Message- From: Aman Singer aman.sin...@gmail.com To: freedos-user freedos-user@lists.sourceforge.net Sent: Sun, Sep 2, 2012 9:53 pm Subject: [Freedos-user] Serial port or USB/PCMCIA modem support Hi, All. I have a laptop on which I would like to install Free DOS. I am, however, in some difficulty. The laptop has only one serial port built in. I am in need of two such ports. The unit has a USB port and several PCMCIA slots, but no other serial port. If I may ask, is there any external hardware which provides a serial port that I could use? Alternatively, does FreeDOS support any PCMCIA or USB modems? Thanks. Aman Singer -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDos in VirtualBox not a sure thing
Hi Eric, Note that this is probably not VM specific and wouldalso happen on real hardware. If I'm running DOS in a production environment on real hardware I (personally) would make sure the hardware could handle it and not overheat. There are plenty of industrial solutions out there that will do this. So I do think this issue applies more to VMs. In SSH2DOS, for example, the problem is that it always iskeeping an eye on the network to see whether there is anynew data to display, which makes your CPU go to 100%. Ifit had some concept of now I have looked often enough inthe incoming network data buffer for this second, and abuffer which can block when it gets full, it would help.Regards, Eric Note that SSH2DOS uses WATTCP. WATTCP already includes a yield function which can be used to provide for multitasking which in this case is a HLT. Simply write a small function that does nothing but HLT, then set the WATTCP yield function to point there, then recompile... I have had success with this method on the old WATTCP FTP client. Maybe if I ever get the time this could be a good contribution for me to make... (since I think it's so easy and all that.. :-) Dave -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDos in VirtualBox not a sure thing
Can you describe what exactly were the problems?
As for myself I've had no issues with getting FreeDOS to run in VMWare player,
QEMU and VitualBox. I used the original FreeDOS 1.0 install and have manually
updated the kernel since then. As for VirtualBox specifically, it will run a
VMDK file so I use the same VMDK file that I have created for VMWare - no
problems. For daily use I use VMWare under Windows XP, under Linux I use QEMU
and sometimes use QEMU under Windows in special situations. I almost never use
VirtualBox but fired it up just now after your posting.
So is the problem simply eating up processor time?
FreeDOS from an OS point of view is actually pretty good - there is an option
in the kernel to HLT during waits for keyboard input (IDLEHALT=-1 in
FDCONFIG.SYS) which I have used and recommend.
But the real problem is the applications. For example FreeDOS EDIT.EXE is a
terrible offender. I modified it for my own use to throw in a few HLTs and now
it works great. People will talk about making applications FDAPM aware and
using the mutliplex interrupt - I personally don't do these things - I make
sure that the application in question is doing a HLT frequently. (For those
who think the computer will lock up the HLT directive halts the processor until
the next interrupt... not forever)
So you must customize every application the user will touch.
If you have the source code, this should be easy. .. look for processor loops
and put in some HLTs.
If you don't have the source code you are going to have to run thru a debugger
and find where the program is looping ... break the debugger when windows says
you're at 100% utilization, should be easy to figure out. Then you need to
patch the BIOS routine, DOS routine or do a binary patch to the application.
Basically we have no idea what kind of loop or polling your application might
do. There is no guarantee that
your app is calling the OS or BIOS on these loops so the operating system will
not be able to fix your problems.
Here's an example:
Original program:
while (hw_not_ready)
{
int hw_status = read_hw(); /* read_hw could be anything, like inportb() */
if (hw_status == GOOD) hw_not_ready=FALSE;
}
Better program for a VM:
while (hw_not_ready)
{
int hw_status=read_hw();
if (hw_status==GOOD) hw_not_ready=FALSE;
else delay_a_tick();
}
bios_clk_ptr = MK_FP(0,0x46c);
void delay_a_tick()
{
long ticks = *bios_clk_ptr;
while(*bios_clk_ptr == ticks)
_asm hlt;
}
-Original Message-
From: john s wolter johnswol...@wolterworks.com
To: freedos-user freedos-user@lists.sourceforge.net
Sent: Wed, Aug 15, 2012 5:47 pm
Subject: [Freedos-user] FreeDos in VirtualBox not a sure thing
I spent four days getting FreeDOS to work as a guest OS inside a VirtualBox
machine. The path to success was a rocky and time consuming trial and error
process. Once the particular console program was running it was not very fast.
The customer deemed it to be usable.
Later in the day the customer cancelled a small DOS software install in
preference to a larger native Windows 7 development. The customer had decided
to purchase an older computer to run the DOS application from hard disk. It
amounts to a lost increment of business for myself that is not significant.
This situation indicates to me that efficient execution of FreeDOS in Virtual
Machines must be made to be transparently easy. VMs are a way to make FreeDOS
available as 16-bit support withers away. The industry leader's 64-bit OS does
not support 16-bit DOS programs directly as in prior versions. Open source
software developers, unfairly, have more pressures on them to prove the
results.
I've seen the form discussions as do others about run-away keyboard polling and
other such issues. Solving these nagging issues may not look to be glamorous
but can swing perceptions of FreeDOS substantially. There are commercial
utilities claiming to control problems but I ask are there equivalent features
or settings within FreeDOS?
FreeDOS did not create these wild-hare programs but is being painted with their
behaviors. It is FreeDOS's burden in life:(i.
The tweaking of the FreeDOS VM with networking in VirtualBox...0
GeneralBasic: OS = Other, Version = DOS
SystemMotherboard: 32 MB, Chipset PIIX3,
...Processor: Cap 87%
...Acceleration: uncheck Enable VT-x/AMD-V
Storage: IDE Controller, FreeDOS...vdi image
NetworkAdapter 1: Enabled, Host-only Adapter, Name=VirtualBox Host-Only
Ethernet Adapter
USB: Enabled for 1.1, Addon Extensions not used
The virtual machine network adapter choice was the 'VirtualBox host-only
Ethernet adapter'. I used that to establish a CIFS/SMB LPT1: printer
redirection to the host's, Windows 7, USB attached HP C4400 printer. The
computer is an HP laptop with i5 CPU with 8 GB of RAMM.
If there is a list of well-known issues, I would like to see if an altered
configuration would help performance.
I have taken
[Freedos-user] Does EMM386 allocate a UMB for its own use when using the NOEMS option?
Hi FD users, I've seen some random comments about EMM386 allocating UMBs for its own use but I have not been able to locate the source code to check this out. (Yes, I expect several comments deprecating EMM386 and directing me to JEMM386.) When using EMS both EMM386 and JEMM386 will allocate a UMB as a transfer area. But what about when using the NOEMS option? It looks like JEMM386 has an option to avoid high memory (ie UMBs) = NOHI. But what's the behavior of EMM386? Will it allocate some of the UMBs it creates for its own use? I would rather that this not be the case and am in the process of migrating to JEMM386 with the NOHI option but want to understand the behavior better. Thanks, Dave -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Any success stories with Kernel 2041, FAT32 and DOSUSB?
Thanks for your note Bernd.Some good ideas I can try. Dave -Original Message- From: Bernd Blaauw bbla...@home.nl To: freedos-user freedos-user@lists.sourceforge.net Sent: Wed, Jun 6, 2012 12:11 pm Subject: Re: [Freedos-user] Any success stories with Kernel 2041, FAT32 and DOSUSB? Op 6-6-2012 17:08, cordat...@aol.com schreef: On most OHCI drivers (including DOSUSB), the driver will load but then the keyboard starts acting erratically. (I'm using PS2 keyboard not USB) Effectively the computer is not usable at this point - I suppose I could write a batch file to test whether it is strictly a keyboard problem or if there are other problems. I've succesfully used Georg's DOSUSB v2.0 with USB flash drive containing a single active primary FAT32 partition. Problem is my USB keyboard then typically gets disabled as DOSUSB replaces BIOS drivers by its own stack, but a keyboard driver isn't present currently within DOSUSB. My final solution was to get a PCI-express USB 3.0 controller card. As add-in cards aren't bootable (no bootrom, no driver in BIOS) nor seen in DOS, I'm booting from some slow USB flash drive, which loads DOSUSB 3.0 and thus gains access to the fast flash drive connected to the add-in card. As all other devices are on USB1/USB2 ports, they don't get disabled by the USB3-only DOSUSB 3.0 driver. All in all, this works pretty well for me. The downside is that the slow USB stick that I boot from, gets drive C: assigned, which I dislike. Messing around with Syslinux, Memdisk and floppy image files works around this nicely, so I can keep C: available for either a ramdisk drive, or for the USB3.0 flash drive. Alternative options are loading this driver from a floppy drive, or cdrom or something, but that's slower. If this device you're loading from is USB as well, you're in trouble as soon as loading DOSUSB v2.0 (it resets the controller, thus also the connected drives, and you end up with a hung system). DOSUSB will find the device and set up a drive. If I use a FAT16 device I can get things working reasonably well but a directory listing will wind up crashing the system and creating all sorts of bad behavior. (Yes, I understand that directory listing may take a long time but my expectation is that it would not crash the OS) I've experienced that DOSUSB sometimes needs a bit longer initialisation time. You might also want to check the errorcode generated by it. My way of solving it was to load and unload DOSUSB a few times, once no more errorcode, I load USBDISK.SYS so the USB flash disk gets mapped. If I use a FAT32 device all hell breaks loose when trying to access the USB disk, FCB error messages or other scrolling messages pop up and the computer must be reset. Any other older kernels or MSDOS suffering the same behaviour? I've got most luck with JEMMEX combined with DOSUSB. Anyway, I'm hoping my next machine can boot natively from USB3.0 ports/devices in UEFI (and BIOS!) at above-USB2.0 speeds. Heck, Apple even made FireWire (and Thunderbolt?) bootable on years old EFI. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Any success stories with Kernel 2041, FAT32 and DOSUSB?
I've tried the Panasonic driver, it hangs on my PC. Also tried DUSE, Iomega and whatever else was on a boot disk which someone put together. Didn't bother trying Bret's drivers because I have EHCI / OHCI. Georg's DOSUSB is the only one that works for me to some degree. Just curious if there is anyone out there who's used FreeDOS with kernel 2041 and Georg's drivers on USB mass storage devices formatted for Fat32? My point being that if yes, things are working great for someone then I'm going to give up. If no, then I'll try MS-DOS 7.0/7.1 with my MB and see if that helps at all. Thanks, Dave -Original Message- From: spvh66 spv...@myopera.com To: freedos-user freedos-user@lists.sourceforge.net Sent: Fri, Jun 1, 2012 2:37 am Subject: [Freedos-user] Any success stories with Kernel 2041, FAT32 and DOSUSB? And http://panasonic.jp/com/support/drive/other/f2h_usb.html doesnt work? -- spv...@myopera.com -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Any success stories with Kernel 2041, FAT32 and DOSUSB?
Hi Eric, My MB has EHCI/USB 2.0 and OHCI/USB 1.1. My understanding was Bret's drivers are strictly UHCI. On most OHCI drivers (including DOSUSB), the driver will load but then the keyboard starts acting erratically. (I'm using PS2 keyboard not USB) Effectively the computer is not usable at this point - I suppose I could write a batch file to test whether it is strictly a keyboard problem or if there are other problems. If I disable OHCI support in the various drivers, most of them hang, for example the Panasonic will hang as it scans for devices. (ie use the /E option) DOSUSB will find the device and set up a drive. If I use a FAT16 device I can get things working reasonably well but a directory listing will wind up crashing the system and creating all sorts of bad behavior. (Yes, I understand that directory listing may take a long time but my expectation is that it would not crash the OS) If I use a FAT32 device all hell breaks loose when trying to access the USB disk, FCB error messages or other scrolling messages pop up and the computer must be reset. Dave -Original Message- From: Eric Auer e.a...@jpberlin.de To: freedos-user freedos-user@lists.sourceforge.net Sent: Wed, Jun 6, 2012 7:48 am Subject: Re: [Freedos-user] Any success stories with Kernel 2041, FAT32 and DOSUSB? Hi! Didn't bother trying Bret's drivers because I have EHCI / OHCI. Georg's DOSUSB is the only one that works for me to some degree. EHCI = USB 2.0, OHCI = similar to UHCI, both USB 1.x... (you have no XHCI = USB 3.0 I guess) In what ways do the DOSUSB drivers work, in which ways do they not? Bret's drivers are only for UHCI (www.bretjohnson.us says that OHCI, EHCI, WHCI, XHCI may be added later?) so I guess this is why you did not try those. someone then I'm going to give up. If no, then I'll try MS-DOS 7.0/7.1 with my MB and see if that helps at all. I doubt that it makes a difference on which DOS you are running the same drivers. By the way, are there any USB storage drivers available in your BIOS itself? Eric -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Any success stories with Kernel 2041, FAT32 and DOSUSB?
I've been trying to get USB working under FreeDOS ... My motherboard has EHCI controller, the only driver which comes close to working is Georg Potthast's DOSUSB. Currently the system crashes (messages about corrupt MCB) when I try to access the USB disk. Just curious if anyone has had success with FAT32 on kernel 2041 and especially with Georg's drivers. Thanks! Dave -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Arachne Troubles
FreeDOS user, Make sure that the NAMESERVER parameter is filled in your WATTCP file. This parameter should come back from the MTCP DHCP program and is probably going to be the same as your router IP address. For fun you can try the IP address 8.8.8.8 as the NAMESERVER if you are unsure on what to do here. Alternatively just try accessing 8.8.8.8 in Arachne itself, just that specific IP and see what happens. -Original Message- From: Kenny Emond cheeseylem...@gmail.com To: FreeDOS User freedos-user@lists.sourceforge.net Sent: Mon, Apr 9, 2012 3:06 pm Subject: Re: [Freedos-user] Arachne Troubles Okay, Thanks everyone! I filled in the my_ip section with my ip (according to dhcp.exe), but Arachne still points me to the Roadrunner search, saying Why Am I Here? - You entered a web address that was used to present site suggestions I tried a lot of things, one of which was filing in mtcp (which I did successfully and when I ping a web address or other computers connected to our router, it comes back positive), but nothing really worked. I know that our internet works on our other comps because I'm browsing right now on our mac. Also, Arachne is clearly connected because it brings up the home page, which it couldn't do before I set it up right. I also have to add (since I didn't really in the first place): I'm pretty new to DOS, so I don't know all the DOS-talk terms and whatnot. I do know how to effectively do a lot of things, but not as much as most of you experienced users and such. --- A FreeDOS User (The one that started this post, just for the sake of reference) On Sun, Apr 8, 2012 at 9:46 PM, Kenny Emond cheeseylem...@gmail.com wrote: Hey, I was finnaly able to find a packet driver for my DOS computer (ethernet connection), but for some reason Arachne shows the main page, but when I try to go to a different page, it brings up a roadrunner search thing. I tried to edit the wattcp.cfg file, like so: my_ip = dhcp netmask = 255.255.255.0 gateway = 192.168.0.1 domain_list = www.rr.com I had to use our mac to find out our router ip (it was under dhcp as router). I put the ip under the gateway section, which I don't know was correct. Anyway, it didn't really work, so I'm at a loss of what to do next. Arachne is at least able to connect, so I did something right. Also, what does the mtcp.cfg file do? I know it has to do with ping and other such things, but how do I use it? And how did it look originally (I accidently did something and it made the file blank)? Any help on any of these questions would be wonderful. Thanks! --- A FreeDOS User P.S.- Please don't use any info I gave you to hack me or something like that. I'm doing this on the honour system. Thanks! Again! -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Arachne Troubles
FreeDOS User ... If WATTCP is working correctly you don't need the other lines in your config file beyond my_ip=dhcp as they are filled in if DHCP works. As has been discussed here before some versions of WATTCP support DHCP and some don't. My guess is that yours does support DHCP since if you didn't have an IP you could not get to the roadrunner search. You mention MTCP.CFG -this is the config file for MTCP, not WATTCP. The two packages are very similar but they have different configuration files. WATTCP and MTCP differ in that WATTCP will provide DHCP services within each application (like Arachne) while MTCP has a stand-alone DHCP program which then updates a config file and all other MTCP apps (like Ping or FTP) assume that the IP is static. One way to remove some uncertainty from your WATTCP configuration is to adopt the MTCP DHCP method. In order to do this you would have a very basic MTCP config file (I think the minimum is the interrupt vector - would be nice if this were not needed :-) and then run the MTCP DHCP program. Everything from your DHCP server (ie your router) will get dumped into the MTCP config file as well as show on your screen. You can then update your WATTCP config file to match. This can be automated in one of a couple of ways I can share with you if you are interested. -Original Message- From: Kenny Emond cheeseylem...@gmail.com To: FreeDOS User freedos-user@lists.sourceforge.net Sent: Sun, Apr 8, 2012 8:47 pm Subject: [Freedos-user] Arachne Troubles Hey, I was finnaly able to find a packet driver for my DOS computer (ethernet connection), but for some reason Arachne shows the main page, but when I try to go to a different page, it brings up a roadrunner search thing. I tried to edit the wattcp.cfg file, like so: my_ip = dhcp netmask = 255.255.255.0 gateway = 192.168.0.1 domain_list = www.rr.com I had to use our mac to find out our router ip (it was under dhcp as router). I put the ip under the gateway section, which I don't know was correct. Anyway, it didn't really work, so I'm at a loss of what to do next. Arachne is at least able to connect, so I did something right. Also, what does the mtcp.cfg file do? I know it has to do with ping and other such things, but how do I use it? And how did it look originally (I accidently did something and it made the file blank)? Any help on any of these questions would be wonderful. Thanks! --- A FreeDOS User P.S.- Please don't use any info I gave you to hack me or something like that. I'm doing this on the honour system. Thanks! Again! -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Packet Driver
Tomdean, I think it should be clear now that it isn't very likely your wireless adapter can be directly controlled from DOS (Free or otherwise). A workable solution would be to boot Windows or Linux on the PC in question and use their wireless card drivers, then boot FreeDOS in a virtual machine. The virtual machine simulates a wired Ethernet interface which is no problem to bridge onto the PC's wireless network adapter. Is there any reason why this solution wouldn't work? Is there a specific reason why you are trying to boot onto real hardware? Cordata -Original Message- From: Thomas D. Dean tomd...@speakeasy.org To: Mike Eriksen thinstation.m...@gmail.com Cc: freedos-user freedos-user@lists.sourceforge.net Sent: Mon, Jul 18, 2011 12:33 pm Subject: Re: [Freedos-user] Packet Driver On Mon, 2011-07-18 at 19:16 +0200, Mike Eriksen wrote: The network is in a semi-remote location - no kids! There is only one other wireless network I can detect, with a marginal signal level. The machine will provide a data stream that will not end the world if it stops. tomdean -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Packet Driver
tomdean, Yes, you need a packet driver. However I'm not sure about running a wireless card under DOS - packet drivers are typically not capable of configuring wireless security. They normally operate with a wired ethernet port. Others will know more about this than I. Is there a reason you are running on real hardware compared to a virtual machine? Packet drivers can be found at one of two places: 1) www.crynwr.com - many of these are open source. 2) The web site of whoever makes the Ethernet interface of your PC. This driver will likely be closed source. What applications are you trying to run?If they are basic FTP, Telnet, etc. you may want to look into mTCP as well. Cordata -Original Message- From: Thomas D. Dean tomd...@speakeasy.org To: freedos-user freedos-user@lists.sourceforge.net Sent: Sun, Jul 17, 2011 9:39 pm Subject: [Freedos-user] Packet Driver I want to install WATTCP on my FreeDOS system. I have a Linksys Wireless-G Notebook Adapter Model WPC54G Ver. 3.1 I have wat2001b.zip. I think I need a packet driver. Correct? Where may I find a driver for FreeDOS? Google returns too many results to be meaningful. tomdean -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Basic question on UIDE
All this talk about UIDE prompted me to investigate this tool. It looks interesting. How does the caching work for disk writes? I assume that when the cache is full the next sector read in will cause the oldest sector to be written out? Is there any sort of a timer which will flush the cache to the hard drive periodically? How do you make sure that the RAM cache is written to the disk? I poked around in the documentation but did not find this information. -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Lynx and DHCP issues
BTW, how did you detect what messages Lynx sent? neither -trace nor -wdebug options seem to log protocol IDs. I use wireshark packet sniffer and recommend it highly. -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Using mTCP DHCP with WATTCP applications
Updates to what? I think I'm done with this at this point. -Original Message- From: Lee Eric openlinuxsou...@gmail.com To: freedos-user freedos-user@lists.sourceforge.net Sent: Mon, Mar 21, 2011 5:24 am Subject: Re: [Freedos-user] Using mTCP DHCP with WATTCP applications Any updates here? On Mon, Mar 21, 2011 at 9:36 AM, Lee Eric openlinuxsou...@gmail.com wrote: Nice! Thanks mate. Eric On Mon, Mar 21, 2011 at 7:36 AM, cordat...@aol.com wrote: To those of you interested in using the mTCP DHCP client with WATTCP applications that don't behave well with DHCP please do the following: a) Find and download minitrue, the executable is MT.EXE. (maybe it's in FreeDOS 1.0, who knows). You can find at: http://www.idiotsdelight.net/minitrue/ b) Create a batch file, I call mine M2WAT.BAT. It looks like this: @echo off rem convert MTCP config file to WATTCP format copy mtcp.cfg wattcp.cfg rem first comment out every line with a '#' mt -b- -c -n wattcp.cfg (^) = # rem now uncomment the ones we want, add equal sign and change if needed mt -b- -c -n wattcp.cfg #ipaddr = my_ip= mt -b- -c -n wattcp.cfg #netmask = netmask= mt -b- -c -n wattcp.cfg #gateway = gateway= mt -b- -c -n wattcp.cfg #nameserver = nameserver= mt -b- -c -n wattcp.cfg #hostname = hostname= --- end of the batch file. c) Run this perhaps as another batch file: SET MTCPCFG = MTCP.CFG DHCP M2WAT whatever your wattcp application is, should work fine. Enjoy. -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Using mTCP DHCP with WATTCP applications
To those of you interested in using the mTCP DHCP client with WATTCP applications that don't behave well with DHCP please do the following: a) Find and download minitrue, the executable is MT.EXE. (maybe it's in FreeDOS 1.0, who knows). You can find at: http://www.idiotsdelight.net/minitrue/ b) Create a batch file, I call mine M2WAT.BAT. It looks like this: @echo off rem convert MTCP config file to WATTCP format copy mtcp.cfg wattcp.cfg rem first comment out every line with a '#' mt -b- -c -n wattcp.cfg (^) = # rem now uncomment the ones we want, add equal sign and change if needed mt -b- -c -n wattcp.cfg #ipaddr = my_ip= mt -b- -c -n wattcp.cfg #netmask = netmask= mt -b- -c -n wattcp.cfg #gateway = gateway= mt -b- -c -n wattcp.cfg #nameserver = nameserver= mt -b- -c -n wattcp.cfg #hostname = hostname= --- end of the batch file. c) Run this perhaps as another batch file: SET MTCPCFG = MTCP.CFG DHCP M2WAT whatever your wattcp application is, should work fine. Enjoy. -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] ntool help
First, it was not necessary to re-install FreeDOS. Lynx, Ntool, and all other WATTCP programs are applications, not part of the operating system. The only OS related thing to consider is whether the packet driver is loaded. It sounds like now that your virtual machine settings may have changed such that DHCP is not working. But back to your original problem - how to know if you are accessing the right WATTCP.CFG file? You can add a line to WATTCP.CFG using the PRINT directive. So create a WATTCP.CFG file which contains only the following line: PRINT = James WATTCP.CFG file has been accessed Or whatever text you want. When you run either NTOOL or LYNX if you see this line printed out during initialization then you know that your config file and not that of some evil genius, has been accessed. WATTCP will access one and only one config file. First it looks at the environment variable WATTCP.CFG which represents a directory (not a file name!) if this environment variable does not exist it uses the current directory. It looks first for the file name WATTCP.CFG and if not found for the file name TCP.CFG. I recommend playing around with different config files using the PRINT directive to completely understand which file the applications will access. You could have one file in directory c:\tmp with PRINT = config file in TMP and another file in C:\BIN with PRINT = config file in BIN and try to access these files by being in the current directory and using the WATTCP.CFG environment variable. In any case your applications will access one and only one WATTCP.CFG file (unless that config file has the INCLUDE directive). So that will eliminate a mystery config file setting some strange IP address and get you to the point where you completely understand which config file is being used. Regarding DHCP not working anymore that sounds like an incorrect packet driver for your VM or a setting on the VM or a virtual bridge misconfiguration. -Original Message- From: James Collins james.collin...@yahoo.com To: freedos-user freedos-user@lists.sourceforge.net Sent: Sat, Mar 19, 2011 11:15 am Subject: Re: [Freedos-user] ntool help hello, I reinstalled freedos to get a fresh start. I just now have been fooling around with ntool and mTCP. just now I got dhcp under mTCP to work. but now it isn't working. I can't get ntool to work either? when I run dhcp through mTCP I get an error: failure to get dhcp address. check your cabling and packet driver settings. I have tcp.cfg, edited and I have the packet driver that I need. and the packet driver is loaded via autoexec.bat. and I just got dhcp to work. when I run ntool I get bootp/dhcp failed. like I said I reinstalled freedos, one reason I did reinstall was to try to figure anything about wattcp.cfg. as far as I know I have wattcp.cfg in c:\fdos\bin\wattcp.cfg I edited wattcp.cfg to just have the line my_ip=dhcp when I run ntool and it fails, I then look at wattcp.cfg and it is empty? like the my_ip=dhcp is gone. mtcp's dhcp doesn't do this. I just renamed wattcp.cfg to wattold.cfg and ran ntool again it ran without any error and wrote nothing to the screen. this makes me think that these programs are like you said getting a fixed ip somewhere. but I am not sure. like I said I reinstalled freedos. any help would be appreciated Sent from my iPhone On Mar 17, 2011, at 6:20 PM, Willi Wasser wiw...@web.de wrote: i just tried to run ntool and i got back an ip address of: MY_IP=0.0.0.0 NTOOL is a WATTCP application itself, one that is linked to a relatively recent version of the WATTCP library that does support dhcp properly. That means, it will try to get its ip parameters from dhcp if the WATTCP.CFG file it finds at program start tells it to do so by specifying MY_IP=DHCP or if it doesn't find a WATTCP.CFG file at all. In this case it will write something like Configuring through BOOTP/DHCP to the screen. If on the other hand it finds a WATTCP.CFG file that defines a static ip address, then it will simply accept this setting, assuming that you know what you are doing. Nevertheless NTOOL -g will output the actual ip parameters that are in effect in this moment. So if NTOOL just tells you MY_IP=0.0.0.0 without any message about using dhcp, then you probably have a WATTCP.CFG file somwhere which defined that address. Probably you just copied that file from somewhere and failed to adjust it to your personal needs. Try to find that file and make it invisible to the program, by re-naming it or by deleting it completely. If that helps, you could even try whether you need NTOOL (or any other external dhcp client) at all. Perhaps lynx just has the very same problem? If the lynx version you use, is also linked to a more recent version of WATTCP, then it could do this all by itself. It not, you could still use
Re: [Freedos-user] ntool help
How do I load the packet driver manually? I have been running autoxec.bat via reboot to load the packet driver. You may need to step back and try reading up a little on DOS. If you don't understand what a batch file is or how to run commands from a given batch file manually you will find life much less frustrating if you study a little and get familiar. In any case in autoexec.bat there will be a line which loads the packet driver. This like will look like RTSPKT 0x60 or maybe PCNTPK int=0x60 It may or may not be either of those but it will likely have an 0x60. You can execute this command manually by entering it from the DOS prompt.This 0x60 is the interrupt number on which the packet driver will be installed. Note that WATTCP applications will find this number out manually while mTCP has to have the same number written into its config file. The point of the exercise, as Mike points out, is to verify that when the packet driver is loaded that it detects a valid Ethernet MAC address. Most packet drivers will print out the detected MAC address when the driver loads. If the packet driver prints out 00:00:00:00:00:00 or FF:FF:FF:FF:FF:FF then that is not a valid MAC address and something didn't work. (ie wrong packet driver or VM set up wrong) So if the packet driver prints out something interesting with several digits that are not 0's or F's then it is highly likely that the packet driver loaded correctly. You can test this even by *not* loading it manually provided it does not scroll off your screen when you reboot. Just look for this information when you reboot the VM. So as a minimum we now know from the previous email that the file you think is the WATTCP config file is truly the config file via the PRINT statement. Once you check the MAC on the packet driver load then we know that the packet driver is (probably) OK. If this is true then the problem is not likely in DOS - it is more likely to be in your VM. You also need to understand how your VM does networking ... but that's another issue. -Original Message- From: James Collins james.collin...@yahoo.com To: freedos-user freedos-user@lists.sourceforge.net Sent: Sat, Mar 19, 2011 2:43 pm Subject: Re: [Freedos-user] ntool help How do I load the packet driver manually? I have been running autoxec.bat via reboot to load the packet driver. Sent from my iPhone On Mar 19, 2011, at 3:09 PM, Willi Wasser wiw...@web.de wrote: If NTOOL tells you bootp/dhcp failed it means exactly what it says. But this can have two different reasons. Either your packet driver is OK, but no dhcp server answered NTOOL's request. In this case there must be a problem with the dhcp server. Or your packet driver did not load properly, possibly because it is misconfigured or invoked with incorrect parameters. Watch carefully the messages the packet driver issues while loading. Sometimes it helps in debugging to load the packet driver manually as it is easier this way to read all the messages. Usually the packet driver reports the ehternet address of the card it found. Does it look reasonable? And mTCP's DHCP message failure to get dhcp address. check your cabling and packet driver settings means the very same thing. If you failed to load the packet driver completely, then NTOOL would tell you NO PACKET DRIVER FOUND while mTCP's DHCP would write Could not access packet driver. ___ Empfehlen Sie WEB.DE DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 100,- Euro! https://freundschaftswerbung.web.de -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] ntool help
Note that WATTCP applications will find this number out manually while mTCP has to have the same number written into its config file. Note that manually should be automatically in the above. -Original Message- From: cordata02 cordat...@aol.com To: freedos-user freedos-user@lists.sourceforge.net Sent: Sat, Mar 19, 2011 3:30 pm Subject: Re: [Freedos-user] ntool help How do I load the packet driver manually? I have been running autoxec.bat via reboot to load the packet driver. You may need to step back and try reading up a little on DOS. If you don't understand what a batch file is or how to run commands from a given batch file manually you will find life much less frustrating if you study a little and get familiar. In any case in autoexec.bat there will be a line which loads the packet driver. This like will look like RTSPKT 0x60 or maybe PCNTPK int=0x60 It may or may not be either of those but it will likely have an 0x60. You can execute this command manually by entering it from the DOS prompt.This 0x60 is the interrupt number on which the packet driver will be installed. Note that WATTCP applications will find this number out manually while mTCP has to have the same number written into its config file. The point of the exercise, as Mike points out, is to verify that when the packet driver is loaded that it detects a valid Ethernet MAC address. Most packet drivers will print out the detected MAC address when the driver loads. If the packet driver prints out 00:00:00:00:00:00 or FF:FF:FF:FF:FF:FF then that is not a valid MAC address and something didn't work. (ie wrong packet driver or VM set up wrong) So if the packet driver prints out something interesting with several digits that are not 0's or F's then it is highly likely that the packet driver loaded correctly. You can test this even by *not* loading it manually provided it does not scroll off your screen when you reboot. Just look for this information when you reboot the VM. So as a minimum we now know from the previous email that the file you think is the WATTCP config file is truly the config file via the PRINT statement. Once you check the MAC on the packet driver load then we know that the packet driver is (probably) OK. If this is true then the problem is not likely in DOS - it is more likely to be in your VM. You also need to understand how your VM does networking ... but that's another issue. -Original Message- From: James Collins james.collin...@yahoo.com To: freedos-user freedos-user@lists.sourceforge.net Sent: Sat, Mar 19, 2011 2:43 pm Subject: Re: [Freedos-user] ntool help How do I load the packet driver manually? I have been running autoxec.bat via reboot to load the packet driver. Sent from my iPhone On Mar 19, 2011, at 3:09 PM, Willi Wasser wiw...@web.de wrote: If NTOOL tells you bootp/dhcp failed it means exactly what it says. But this can have two different reasons. Either your packet driver is OK, but no dhcp server answered NTOOL's request. In this case there must be a problem with the dhcp server. Or your packet driver did not load properly, possibly because it is misconfigured or invoked with incorrect parameters. Watch carefully the messages the packet driver issues while loading. Sometimes it helps in debugging to load the packet driver manually as it is easier this way to read all the messages. Usually the packet driver reports the ehternet address of the card it found. Does it look reasonable? And mTCP's DHCP message failure to get dhcp address. check your cabling and packet driver settings means the very same thing. If you failed to load the packet driver completely, then NTOOL would tell you NO PACKET DRIVER FOUND while mTCP's DHCP would write Could not access packet driver. ___ Empfehlen Sie WEB.DE DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 100,- Euro! https://freundschaftswerbung.web.de -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d
Re: [Freedos-user] ntool help
I downloaded VirtualBox and got FreeDOS running on it with networking (WATTCP clients) using a Windows host. (Sorry, no macs here) It looks like a correct packet driver is in fact PCNTPK.COM, so check if that is in your autoexec.bat file. I also tested and verified that it is possible to load this driver twice on two different interrupts and things get screwed up pretty bad. So it would be good to somehow get a clean AUTOEXEC.BAT with no packet drivers in it, then install the packet driver via PCNTPK INT=0x60 and test. You can also use the command MEM /U to show you if the packet driver is loaded and perhaps multiple drivers or multiple copies of the same driver. -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Lynx issues
I got Lynx 2.8.5 running on FreeDOS in Virtual Box on Windows. I was able to navigate to yahoo.com and some other spots. There are some anomolies in the way Lynx works compared to typical WATTCP programs. It looks like Lynx is using WATT-32 which makes sense in retrospect since Lynx is compiled with DJGPP. Apparently DHCP does not work right in this case. I detected that Lynx sends a DHCP request message immediately rather than the expected DHCP discover message (which if successful is then followed by DHCP request). Bottom line: Lynx does not work with DHCP. Someone would need to re-link with a later version of WATT-32 assuming that there exists a later version with DHCP working right. So the idea of using NTOOL is probably the right way to go here. Here is my WATTCP.CFG file: my_ip = 192.168.1.41 (assigned via DHCP, then manual edit file) nameserver = 8.8.8.8(google public nameserver) gateway = 192.168.1.1 (my wireless router) netmask = 255.255.254.0 You need to set up some environment variables. I put all the lynx files in a directory called c:\lynx. I then deleted the local WATTCP.CFG file since I already have one. Again the behavior is squirrely perhaps because it's using WATT-32. SET WATTCP.CFG = C:\ SET HOME=C:\lynx SET LYNX_CFG=C:\lynx\lynx.cfg Put yourself into the directory c:\lynx, type lynx, things start working... I have VirtualBox set up as bridged mode so that the VM gets its own IP from the router. You could in theory also do NAT and share the host IP. -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Help: How to enable networking in a FreeDOS client?
As has been noted here in the past, WATTCP is technically not part of the operating system, it's a library that is linked in with the application program. Wattcp *does* support DHCP and the line my_ip = DHCP should be all you need to get DHCP running. The key is that you need to make sure that the more recent update of wattcp has been linked with your application program. What you should see with the config file below is that if DHCP fails you will get an error message. If you don't get an error message then it worked. An alternative is to use Mike Brutman's mTCP DHCP program. Mike separates DHCP into a separate program which will tell you the IP selected. You could then edit your WATTCP config file to match the IP returned by the DHCP client program. The mTCP DHCP program will at least test your hardware to verify that things are working. So to sum up: if your application program uses the right version of WATTCP then you don't need to do anything, run the program and it will tell you if DHCP fails. -Original Message- From: Lee Eric openlinuxsou...@gmail.com To: freedos-user freedos-user@lists.sourceforge.net Sent: Sun, Mar 13, 2011 7:10 am Subject: Re: [Freedos-user] Help: How to enable networking in a FreeDOS client? Any update here? Eric On Sat, Mar 12, 2011 at 11:40 PM, Lee Eric openlinuxsou...@gmail.com wrote: Hi, I installed FreeDOS with wattcp and FreeDOS has recognized the ethernet interface in the system. However, how can I get DHCP IP from the server? Here's C:\AUTOEXEC.BAT file content. @echo off SET dosdir=C:\FDOS REM C:\FDOS\BIN\BANNER2 REM C:\FDOS\BIN\BLACKOUT set PATH=%dosdir%\bin set NLSPATH=%dosdir%\NLS set HELPPATH=%dosdir%\HELP set temp=%dosdir%\temp set tmp=%dosdir%\temp SET BLASTER=A220 I5 D1 H5 P330 REM ShsuCDhd /QQ /F:C:\FDBOOTCD.ISO if not %config%==4 REM LH VIAUDIO if not %config%==4 REM LH VIAFMTSR if not %config%==4 LH FDAPM APMDOS if %config%==2 LH SHARE if not %config%==4 ShsuCDX /QQ /~ /D:?FDCD0002 /D:?FDCD0003 /D:?CDRCACH0 SET autofile=C:\autoexec.bat alias reboot=fdapm warmboot alias halt=fdapm poweroff SET CFGFILE=C:\fdconfig.sys echo type HELP to get support on commands and navigation echo. echo Welcome to FreeDOS echo. if not %config%==4 mouse C:\FDOS\drivers\net\crynwr\rtspkt 0x60 SET WATTCP.CFG=%DOSDIR%\BIN And here's wattcp.cfg file content. my_ip = dhcp netmask = 255.255.255.0 gateway = 0.0.0.0 domain_list = your.domain.com So what commend I shall execute to get the IP address by DHCP? Thanks very much. Eric -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] ARC and shareware
The discussion about TUNZ got me thinking about the ARC file format. There are several of the old shareware utilities out on the internet - ARCE, ARC-E, PKXARC .. but are there any available which are GPL or close to GPL? (For DOS, of course!) Poking around I noticed that Vernon Buerg passed away a year or so ago. It seems like a lot of shareware will wind up dying with their authors due to licensing issues. I wonder if shareware authors or their heirs are willing to open up their software licensing after death Dave -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Connecting FreeDOS to a SMB share
With all the discussion on mTCP it seems this package is getting a lot of attention. Is there any update as to when we might be able to get source or even just a binary library? -Original Message- From: mbbrutman mbbrut...@brutman.com To: freedos-user freedos-user@lists.sourceforge.net Sent: Mon, Jan 17, 2011 2:31 pm Subject: Re: [Freedos-user] Connecting FreeDOS to a SMB share Quoting Eric Auer e.a...@jpberlin.de: Hi Santiago, Update: I installed easily the NDIS2 drivers for my card, then the packet driver wrapper. mTCP is working perfectly. Right now, I am trying TCP's MS CLIENT 3.0 to connect to the SMB share through TCP/IP. Nice! Maybe you could email a summary of how you did it? I mean what you installed and which config files you had to edit in which way to make MTCP work via NDIS etc :-) I second that motion - I've never used NDIS and a shim before and I'd like to see how that is done. The SMB share is actually a Dlink NAS, I can use NFS too, but I have to install some modules before. I'll try a little more for SMB and then try NFS. Interesting. I assume you can also access the NAS via FTP or even HTTP? Samba sounds okay for me, but of course the choice between MSCLIENT and the ported Linux Samba command line tool smbclient is not that big :-) Eric If most NAS boxes do HTTP, is this the reason/motivation I need to get wget done? Mike -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Fwd: File corruption
Sorry to sound dense but how do you change the kernel from 16 to 32 bits? Isn't there just one kernel and it works with a filesystem that is FAT16 or FAT32? Or are these kernels compiled with different memory models? Dave -Original Message- From: Marcos Favero Florence de Barros fav...@mpcnet.com.br To: FreeDOS List freedos-user@lists.sourceforge.net Sent: Thu, Sep 23, 2010 4:45 pm Subject: [Freedos-user] File corruption Hi Tom, Here are the results you asked. Tests were done in a Compaq Armada E500. is that reproducable with COPY/XCOPY ? Yes. I changed the kernel back to 16 bits and copied about 200 files with COPY and XCOPY. The errors appeared as before. I also decompressed some zip files, just to check once more, and the errors appeared too. I have screen captures of ChkDsk, but because they have strange characters in them I'm sending them as an attached zip file. In all three cases, the files could be deleted, and the remainder of the file system returned to normal. is that reproducable with empty config.sys/autoexevc.bat ? No. I skipped fdconfig.sys and fdauto.bat with the F8 key, and repeated the same copies with COPY and XCOPY. This time there were no errors! Regards, Marcos -- Marcos Favero Florence de Barros Campinas, Brazil fav...@mpcnet.com.br -- -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] How to detect power button in DOS?
Hi, I searched the archives for the answer to this question but I couldn't find much. I'd like to be able to detect that the power button on the computer has been pressed while running freedos. (Also this would apply to the powerdown event from the QEMU emulator) I know there is a power management utility from Eric but it doesn't seem to monitor for the power button. Obviously I would need to incorporate some code into my application to notice the button press and then to take action (like closing files, etc) before invoking a program to shut down the computer. (This type of program I can find). Any ideas? Thanks, Dave -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Emulating obsolete HW in FreeDOS
Eric et al, Thanks for your replies.??? The application is a very old network manager. The obsolete communications device is a serial board. It is not, however, a typical serial board.? The serial board performs certain functions of a proprietary protocol which is somewhat similar to frame relay.? The interface to this board is not through a standard I/O port (like 0x3f8) but is based on a shared memory area of frame buffers.?? The application software running on the PC allocates a frame buffer ( physically located in the comm board) and copies a 128 byte frame to the buffer.? The comms board then takes the frame and does some link level processing (ie makes sure a channel is open, etc, imagine frame relay or X.25 but proprietary). The application software knows nothing about the low level things happening on the comms link - all it knows is that when it has a frame to send it allocates a chunk of memory and when it sees a chunk of memory appear in the receive queue area that is an incoming frame. So what I would want to do is something along the lines of what Eric suggested about the VGA- a certain memory area is defined for this buffer transfer.? So the emulator would then actually process the information or perhaps just open a more standards-based channel (pipe, socket, whatever) towards a small program which would do the link level communications. I took a look at QEMU and have a ways to go but the source does not look all that big. I was impressed at how quickly I got a Linux environment running on my PC.. Dave -Original Message- From: Eric Auer [EMAIL PROTECTED] To: freedos-user@lists.sourceforge.net Sent: Fri, 8 Aug 2008 11:36 am Subject: Re: [Freedos-user] Emulating obsolete HW in FreeDOS Hi Dave, Please explain that obsolete peripheral communications device. 1)? Re write the application to use WATTCP or something similar. If it is open source, you can do that. 2) Leave the application alone and modify the emulator (like VMWare Player) to provide a bridge between the fixed shared memory addresses and some sort of standard Windows (or even Linux) interfaces. You cannot modify VMWare (closed source) but you can modify Bochs, Qemu and Dosemu. The latter is only available in Linux but it has a nice virtual hardware infrastructure. I once planned to write a TI Pro PC set of hardware for it but of course it is still a lot of work so I never got around doing it. The TI Pro has non standard COM ports and a high end 3 plane special 720x350 RGB graphics card. Leaving the application alone has some benefits since it's pretty complex, brittle and old. What exactly does that application do? So option 1 is pretty obvious and I could run the app either with FreeDOS booted directly on the hardware or booted on VMWare under Linux or Windows. It makes a big difference whether you boot on hardware or VMWare. Option 2 is what I'm trying to explore -- has anyone had experience with this?? Does either VMWare or DOSEmu have capabilities in this area? Both do, but as -you- do not have the vmware source code, you cannot help yourself and write hardware for vmware. You can write your own hardware for dosemu, bochs and qemu, though :-). some sort of memory range which is shared between FreeDOS and the emulator which would then communicate to the outside world? Look at the way the emulators support VGA graphics: DOS writes to the virtual VGA RAM and the emulator calculates what you would see on a real VGA and then shows that on your Linux or Windows desktop in an image :-). Note that VGA hardware is pretty complex so do not get scared when you fail to understand the VGA emulation engine sources. Eric - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
