[Freedos-user] Freedos needs hardware testing tools...

2009-03-19 Thread Michael Robinson
Something specific to my hardware on my 486 DX2 66 must be causing
fdupdate to crash, but there seem to be no diagnosis tools to find
out what that is.  Please rectify this problem.  I want something
that detects resource conflicts, flaky memory, etcetera.


--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] Freedos needs hardware testing tools...

2009-03-19 Thread Eric Auer

Hi!

 Something specific to my hardware on my 486 DX2 66 must be causing
 fdupdate to crash, but there seem to be no diagnosis tools to find
 out what that is.  Please rectify this problem.  I want something
 that detects resource conflicts, flaky memory, etcetera.

First try to boot without loading (J)EMM386, a common cause of
problems is a bad default EMM386 configuration which makes UMB
space available for DOS in areas that should stay reserved for
something else, such as BIOS or extension cards. You can use a
tool like PCISLEEP to get a list of devices. The Quarterdeck MFT
Manifest tool is also freeware by now, might be useful even if
it is not hardware oriented. Similar to a very extended MEM :-)

There is also a RAM/resource info tool from Japheth that can be
used to debug the autoconfig abilities of JEMM386, if you can
not find it on (www) japheth.de you can always ask him by mail.

Eric

PS: For flaky memory, run MEMTEST86 or MEMTEST86+. There is also
a version that can be started from DOS called MEMTESTE. Note that
it can only start if no EMM386 is loaded. It works best if you do
not load any other drivers at all before starting MEMTESTE...


--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


[Freedos-user] unload previsiously loaded exe and sys on fdconfig.sys

2009-03-19 Thread Fabrício Ceolin
Hi,

I want free some freedos memory after using a packet driver and others sys
(under fdconfig.sys) and exe (like doskey).
There are any way to unload programs without reboot?

Thanks!
-- 
Fabrício Ceolin
ulevel.com
Diretor Executivo
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


[Freedos-user] Installation Problems

2009-03-19 Thread usul
Hello I am having problems installing the current version.
I get everything completed and it seems to be ok,
fdisked and set 2g to the os as primary partition, active
and after booting from the CD Rom I can go to the c:
and see all the files including the system ones.

but when I try and boot from the harddrive after I go through all the system
checks
I get a blank screen. no cursor, no beeps etc nothing.
If I then boot from the cd I can see everything on the harddrive.

I tried out of fustration to install Puppy Linux. and that worked.
Could it be working because Puppy did something else to the mbr or because
of grub the bootloader?
any thoughts here?

it is a
Fujitsu LifeBook 770Tx
With an additional memory card, maxed out memory
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] unload previsiously loaded exe and sys on fdconfig.sys

2009-03-19 Thread Christian Masloch
Hi,

 I want free some freedos memory after using a packet driver and others  
 sys
 (under fdconfig.sys) and exe (like doskey).
 There are any way to unload programs without reboot?

The best method is to use programs that provide unloading as option so  
that they can properly unload themself. If you have to use a program  
without such an option you may want to try out the TSR Utilities (freeware  
without source code) which save some important system data before you  
install the program, then try to unload the program later by restoring  
this data. This method doesn't work for all programs so you have to be  
careful with it. I think the TSR Utilities don't work with programs loaded  
in FDCONFIG.SYS but you could try whether that program can be loaded by  
DEVLOAD (on Eric's site, or on the FreeDOS software page) instead.

Regards,
Christian

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] unload previsiously loaded exe and sys on fdconfig.sys

2009-03-19 Thread Eric Auer

Hi,

 I want free some freedos memory after using a packet driver
 and others sys (under fdconfig.sys) and exe (like doskey).

I recommend to have 2 different config sys menu items:
With and without internet :-). Doskey should not be
necessary, FreeCOM and 4DOS have built-in history...

 There are any way to unload programs without reboot?

Some tools which work with snapshot and restore of some
system state can do this, and some drivers have a built-
in unload option, but it is easier and more stable in the
result to just reboot. Booting DOS only takes seconds :-)

Eric



--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


[Freedos-user] FreeDOS on Virtual PC 2007

2009-03-19 Thread Michael Horvath
Hi!

I am having trouble with FreeDOS on Virtual PC 2007. I am able to 
install it OK, and two of the three (four?) boot options work.



Option #2 (the default, and the one that doesn't work) results in the 
following error:

Illegal instruction occured.
CS= IP=EEC3 SS=D0B4 SP=0004 ES=0070
...etc...
...etc...
Aborting program
EMM386 - unable to continue - Please reboot=

The last four characters  are a set of hexadecimal numbers that 
are change several times each second.



I am able to boot to the command prompt using options #1 and #3, but am 
having trouble running software. For instance, I am trying to install 
the video game Out of this World, but receive the following errors 
when running the installation program:

Line #1 in batchfile 'A:\INSTALL.BAT' too long

If I try to run the setup file directly I get this error:

Interrupt divide by zero, stack:
091B 04e3 ... ...



I also am unable to read the SimCity installation disk in FreeDOS. I am 
able to mount the drive and change drive letters, but when I try to 
retrieve the directory contents using the DIR command I get this error:

Volume in drive A Error reading from drive A: DOS error: sector not found



Here are some details regarding my host system:
AMD Sempron 3000+
1.5GB RAM
Windows XP Home
GeForce 4 TI
Plenty of free hard disk space
Onboard sound/networking
Samsung DVD writer
SuperDisk IDE drive for reading floppies

Details regarding my virtual system:
Virtual PC 2007
128MB RAM
8MB video RAM
1MB code cache
1GB hard disk space
Video mode: Text mode, 640 x 400 x 0



I'd appreciate any help you could provide.

-Mike

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] Installation Problems

2009-03-19 Thread Eric Auer

Hi Usul,

 Hello I am having problems installing the current version.
 I get everything completed and it seems to be ok,
 fdisked and set 2g to the os as primary partition, active

You can easily use more with FAT32 and LBA...

 and after booting from the CD Rom I can go to the c:
 and see all the files including the system ones.

 but when I try and boot from the harddrive after I go
 through all the system checks I get a blank screen.
 no cursor, no beeps etc nothing.

 If I then boot from the cd I can see everything on the harddrive.

Please explain what all the system checks means, do
you get only the BIOS init or do you get at least some
message like FreeDOS or Initdisk before the blank?

Sometimes harddisks come with non-bootable MBRs, then
marking as active is not enough. You could do something
like FDISK /MBR but be aware that this will often
destroy other boot menus such as GRUB... Which in turn
can be fixed by re-installing GRUB, of course ;-). It
is also possible that the SYS C: part somehow failed
but then you can just run SYS C: manually once more.

To check whether your C: drive is SYSed with FreeDOS,
use the tool OSCHECK from your install CD or from WWW.

Eric :-)


--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


[Freedos-user] Installation difficulties...

2009-03-19 Thread John Ames
Okay. I would really like to use FreeDOS, preferrably the full-install CD,
and definitely with USB disk support. Problem is, the NIC in the computer I
want to install it on (a 3Com 3C595-TX) does not appear to be recognized by
either the default packet driver or the manufacturer's DOS driver, unless it
requires some fiddling with the PCI arguments (which are, frankly, over my
head.) And a large portion of the packages, including some absolutely
critical ones like the USB mass storage driver, seem to rely on the
installer's ability to use wget to download the latest version off the
Internet. Is there a way around this problem, or am I SOL without a more
commonly-supported network card?
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] Installation difficulties...

2009-03-19 Thread Eric Auer

Hi,

 Okay. I would really like to use FreeDOS, preferrably the full-install CD,
 and definitely with USB disk support. Problem is, the NIC in the computer I

On modern PC, your BIOS already does USB disk support for you and DOS.
For the others, you can try the USB drivers made by Georg Potthast:

www.georgpotthast.de/usb/ (see also Sioux server, NIC driver page ;-))

 want to install it on (a 3Com 3C595-TX) does not appear to be recognized by
 either the default packet driver or the manufacturer's DOS driver, unless it
 requires some fiddling with the PCI arguments (which are, frankly, over my
 head.) And a large portion of the packages, including some absolutely

You should give some more details about why the manufacturer driver
fails. Any error messages? Did you try NwDSK yet? www.veder.com/nwdsk/

 critical ones like the USB mass storage driver, seem to rely on the
 installer's ability to use wget to download the latest version off the
 Internet. Is there a way around this problem, or am I SOL without a
 more commonly-supported network card?

On the FdDependencies page on the fd-doc wiki, you can see that mostly
the following use internet (invoke wget) during install:

FProt, ASPI, SCSI (not needed for BIOS drives), USBDOS, VIA (VIA audio)

Also, wget, wattcp, fdstpop, bsflite, lnxsmal, lynx, lynxex, openxp,
vnc, hxrt and arachne can be useful online. XHarbor and OWatcom are
very big (XHarbor also requires OWatcom).

I would recommend to NOT install any of the use internet during
install packages initially, as internet connections often hang
at this point. You can add and finetune internet drivers later.
And of course you can download ZIPs with any other system where
the internet does work and then unzip them on your DOS drive :-).

Eric



--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


[Freedos-user] I want to port drivewire to freedos...

2009-03-19 Thread Michael Robinson
I have the C source code for the 1.7 release that is meant for Linux.

I want to port this code to freedos and build a gem compatible 
interface for it.

Drivewire, for those who don't know, is a piece of software that 
allows a color computer 1/2/3 to access via serial port a modern
computer and the modern computer emulates a disk drive.  These old 
computers used 5 1/4 low density floppies which are no more now.  
The drives for low density 5 1/4 floppies aren't available 
anymore.  Drivewire doesn't always work, but most of the time 
it does.  Programs that follow the Tandy standard for disk 
access have no problem with drivewire.

Now then, the Linux version depends on specific Linux only C 
libraries.  I need to know what the equivalent libraries are 
under Freedos and as necessary I will need to recode if the 
dos equivalent library is different.

The following link:

 http://drivewireserver.cvs.sourceforge.net/drivewireserver/ 

is where the source code for the drivewire server can be 
downloaded from.

I am interested in doing a port because Windows 98SE is awfully 
heavy on a 486 DX2-66 with only 20 megs of ram, and it isn't free.

I could use some help getting the information about what the C 
library equivalents are under freedos and how they vary from the 
ones in Linux.  Another area where I need help is understanding 
gem so I can make my drivewire port a gem application.


--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] Freedos needs hardware testing tools...

2009-03-19 Thread Michael Robinson

On Thu, 2009-03-19 at 10:25 +0100, Eric Auer wrote:
 Hi!
 
  Something specific to my hardware on my 486 DX2 66 must be causing
  fdupdate to crash, but there seem to be no diagnosis tools to find
  out what that is.  Please rectify this problem.  I want something
  that detects resource conflicts, flaky memory, etcetera.
 
 First try to boot without loading (J)EMM386, a common cause of
 problems is a bad default EMM386 configuration which makes UMB
 space available for DOS in areas that should stay reserved for
 something else, such as BIOS or extension cards. You can use a
 tool like PCISLEEP to get a list of devices. The Quarterdeck MFT
 Manifest tool is also freeware by now, might be useful even if
 it is not hardware oriented. Similar to a very extended MEM :-)
 
 There is also a RAM/resource info tool from Japheth that can be
 used to debug the autoconfig abilities of JEMM386, if you can
 not find it on (www) japheth.de you can always ask him by mail.
 
 Eric
 
 PS: For flaky memory, run MEMTEST86 or MEMTEST86+. There is also
 a version that can be started from DOS called MEMTESTE. Note that
 it can only start if no EMM386 is loaded. It works best if you do
 not load any other drivers at all before starting MEMTESTE...

Okay, I have tried loading no drivers and then with just the
packet driver running fdupdate.  It still crashes.  Is there
a way to scan for bios usage of memory so that I can put in
the necessary exceptions?  The PCISLEEP comment is interesting,
but I'm on an old EISA only Intel 80486 DX2-66 that uses 32 pin
simms.  The bios is an AMI bios circa 1993.

I'll see about grabbing a copy of memteste.


--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] I want to port drivewire to freedos...

2009-03-19 Thread Blair Campbell
 Now then, the Linux version depends on specific Linux only C
 libraries.  I need to know what the equivalent libraries are
 under Freedos and as necessary I will need to recode if the
 dos equivalent library is different.

O.K.  It looks like it depends at least on pthreads, curses, termios,
and linux-specific tty devices.
Often (as is the case with curses), linux C libraries are available
under FreeDOS with DJGPP; they are the same libraries, just
re-compiled (DJGPP has a fairly POSIX-compatible c-library, it is
somewhat comparable to cygwin on Windows..
Curses is easy, pdcurses is available for 16-bit or 32-bit DOS.  Also
ncurses is available for DJGPP.  If you plan on implementing it with
GEM, you would likely want to replace the parts that depend on curses
with GEM-equivalent functions (curses does all of the
screen-manipulation).
If you plan on a 32-bit port (GEM has djgpp bindings IIRC), termios is
available in the c-library to manipulate the screen and also there are
pthreads libraries available for djgpp.  But if termios is used to
manipulate the serial ports as well, you would need to implement a
file-system extention (see
http://www.delorie.com/djgpp/doc/libc/libc_321.html for a description)
to handle serial devices as well as screen devices (and maybe also
create your own termios interface to serial ports).  The file-system
extention would probably suffice to access linux-specific tty devices.
If you plan on a 16-bit port, pthreads (a multi-threading library),
would be a challenge to implement (but likely possible), and termios
would be possible to implement, but I don't think there exists a
termios-compatible library for 16-bit DOS.
termios probably wouldn't be too difficult to implement for 16-bit
DOS.  Accesses to linux-specific tty devies would have to be replaced
with DOS-equivalent functionality.

Overall, it's a decently-sized job.  Plus if you don't know how to
write GEM applications, you would have to learn that as well.

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user