Re: [Freedos-user] freedos-98

2012-12-20 Thread dos386
 I am curious if you can run Warcraft II under Wine

I never tested this WC II at all :-|

 ReactOS used to an effort to clone Windows 95

YO ... FreeWin95 IIRC tried to clone 95, ReactOS always
NT (but moving: NT4 - 2K - XP - Wi$ta - 7 - 8 - ???)

 until that was abandoned in favor of the NT architecture

NT sucks less than ME (in some areas).

 but 95/98 era games are not always compatible with plain old dos

2 options for Win32 stuff:

1. HX
2. ReactOS

But there is no solution for Win16 crap.

--
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] freedos-98

2012-12-20 Thread Felix Miata
On 2012-12-20 08:30 (GMT) dos386 composed:

 there is no solution for Win16

There is. It's just not free: OS/2 Warp (old IBM name)  eComStation (current 
release)
-- 
The wise are known for their understanding, and pleasant
words are persuasive. Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

--
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


[Freedos-user] Re (2): Another possible ambiguity of target; a drive part not acceptable to the installer.

2012-12-20 Thread peasthope
From:   Felix Miata mrma...@earthlink.net
Date:   Wed, 19 Dec 2012 23:36:42 -0500
 Why do you think a partitioning tool would damage a table? 

Isn't the most common source of a failure, a bug.  

 No FDISK I've 
 ever used will ignore existing partitions. To alter existing partitions 
 requires you to direct it delete first, then create anew. To create new from 
 freespace does not require it do anything to what's already there.

I've never had FDISK break anything either but this is unfamiliar 
territory and there can always be a first time.  Thanks for the 
reassurance.

 The only catch ...

I was afraid there might be.  =8~)

 ... as long as that tool conforms to common conventions.

All too often, conventions are broken by ignorance or sloppyness 
or just by a simple blunder.

Regards,... Peter E.



-- 
123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
Tel +13606390202  Bcc: peasthope at shaw.ca  http://carnot.yi.org/  
http://members.shaw.ca/peasthope/index.html#Itinerary 


--
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


[Freedos-user] Stack overflow

2012-12-20 Thread Santiago Almenara
Hello list:

I am having Stack Overflow problems with this simple code under FreeDOS and
OpenWatcom:

#include stdio.h

char a[8192];

int main()
{
int i;
char b[8192];
for(i=0; i8192; i++) a[i]=b[i]=0;
return 0;
}

I keep getting stack overflow problems.

I know this code is very simple and meaningless, but it's an example of how
I am having stack overflow problems with static arrays of size 8192.

Excuse me if the mail is too off-topic, but I think the problem is
something to do with memory.

Thanks,

Santiago
--
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] Stack overflow

2012-12-20 Thread Chris Evans
wouldnt using  memset() be better ? 



On Dec 20, 2012, at 10:24 AM, Santiago Almenara wrote:

 Hello list:
 
 I am having Stack Overflow problems with this simple code under FreeDOS and 
 OpenWatcom:
 
 #include stdio.h
 
 char a[8192];
 
 int main()
 {
 int i;
 char b[8192];
 for(i=0; i8192; i++) a[i]=b[i]=0;
 return 0;
 }
 
 I keep getting stack overflow problems.
 
 I know this code is very simple and meaningless, but it's an example of how I 
 am having stack overflow problems with static arrays of size 8192.
 
 Excuse me if the mail is too off-topic, but I think the problem is something 
 to do with memory.
 
 Thanks,
 
 Santiago
 
 --
 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] Stack overflow

2012-12-20 Thread Mateusz Viste
AFAIK when you use static tables they are allocated on the stack.
You might want to try allocating them on the heap...

To do so, simply use malloc().

  char *a;
  a = malloc(8192);
  if (a == NULL) return(1);
  /* do your stuff */
  free(a);
  return(0);

cheers,
Mateusz




On 12/20/2012 07:24 PM, Santiago Almenara wrote:
 Hello list:

 I am having Stack Overflow problems with this simple code under FreeDOS
 and OpenWatcom:

 #include stdio.h

 char a[8192];

 int main()
 {
  int i;
  char b[8192];
  for(i=0; i8192; i++) a[i]=b[i]=0;
  return 0;
 }

 I keep getting stack overflow problems.

 I know this code is very simple and meaningless, but it's an example of
 how I am having stack overflow problems with static arrays of size 8192.

 Excuse me if the mail is too off-topic, but I think the problem is
 something to do with memory.

 Thanks,

 Santiago



 --
 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] Stack overflow

2012-12-20 Thread Michael B. Brutman

First, the good news - Watcom includes code at the start and end of each 
function to detect stack overflows.  It is a lot easier to debug code 
when you know what the root cause of the problem is. If the stack 
overflow were to happen and remain silent, you could have all sorts of 
strange behavior.

- Don't allocate large structures on the stack.  That is the first 
problem.  8KB for a stack object is pretty large.  Use malloc or other 
dynamic memory allocation instead.

- If you need a large stack because you have lots of functions calling 
each other or are writing recursive code, there is a linker option to 
increase the size of the stack.  The default size is small.  I usually 
use stack=4096 on my mTCP apps to increase the size to something more 
reasonable for my code.  You can figure out the correct value for your 
code by trial and error or by doing a careful analysis of your code.


Mike


--
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] Another possible ambiguity of target; a drive part not acceptable to the installer.

2012-12-20 Thread Rugxulo
Hi,

On Wed, Dec 19, 2012 at 10:36 PM, Felix Miata mrma...@earthlink.net wrote:
 On 2012-12-19 10:37 (GMT-0800) peasth...@shaw.ca composed:

 From: Rugxulo

 FDISK creates at least one partition (primary, active, FAT, presumably
 bootable) for DOS. (This is written into the partition table, ...

 OK.  If it damages the table in the process, there will be
 a problem accessing data on parts 2, 3 or 4.  Exactly what
 I wish to avoid.

 Why do you think a partitioning tool would damage a table? No FDISK I've
 ever used will ignore existing partitions. To alter existing partitions
 requires you to direct it delete first, then create anew. To create new from
 freespace does not require it do anything to what's already there.

 The installer will install to existing without need to change any table
 entries with FDISK, so you're safe to complete partitioning with any tool
 that suits you prior to beginning installation, as long as that tool conforms
 to common conventions.

If really worried, you can backup your MBR before hand (preferably to
bootable floppy or similar). You can use BTTR's BOOTMGR for this. And
even if your partition table was corrupted somehow, you could maybe
use TestDisk to recover it for you.

Anyways, it's probably best to create partition (FDISK) and format it
at the same time so there is no confusing. But you have to reboot
after using FDISK for the changes to take effect. Yes, it's a bit
dicey when multibooting, but that's unavoidable.

--
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] Re (2): Another possible ambiguity of target; a drive part not acceptable to the installer.

2012-12-20 Thread Bernd Blaauw
Op 19-12-2012 19:37, peasth...@shaw.ca schreef:

 The FreeDOS 1.1 Base CD offers to apply fdisk;  but you
 recommend not using it?  An installer which should not be used?

The FDISK of any DOS has always been very limited, mimicking Microsoft's 
installation procedure (I'm the only operating system, overwrite any 
previous code).

For a blank harddisk FDISK will do just fine.



 ... make sure the partition (drive) ...

 There's that ambiguity again.  Do you mean hard disk drive as
 in /dev/sda or part of a drive as in /dev/sda1, /dev/sda2 and etc.

'Drive' is a typical DOS terminology, meaning partition/volume, thus 
sda1 etc. It's used as 'Drive C:'. Basically referring to everything 
which has a driveletter assigned (floppy, harddisk, cdrom, network 
shares, etc).

More advanced operating systems have improved partitioning tools that 
also take multiple operating systems into consideration and allow to 
setup multibooting by installing a bootmanager or including previous 
operating systems to their own bootloader.

Bernd

--
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] Stack overflow

2012-12-20 Thread Santiago Almenara
Michael:

Where can I find the default size for the watcom stack?

If you use stack=4096, it means the default stack size might be much
smaller than the 16384 I am using.


Santiago


On Thu, Dec 20, 2012 at 2:42 PM, Michael B. Brutman
mbbrut...@brutman.comwrote:


 First, the good news - Watcom includes code at the start and end of each
 function to detect stack overflows.  It is a lot easier to debug code
 when you know what the root cause of the problem is. If the stack
 overflow were to happen and remain silent, you could have all sorts of
 strange behavior.

 - Don't allocate large structures on the stack.  That is the first
 problem.  8KB for a stack object is pretty large.  Use malloc or other
 dynamic memory allocation instead.

 - If you need a large stack because you have lots of functions calling
 each other or are writing recursive code, there is a linker option to
 increase the size of the stack.  The default size is small.  I usually
 use stack=4096 on my mTCP apps to increase the size to something more
 reasonable for my code.  You can figure out the correct value for your
 code by trial and error or by doing a careful analysis of your code.


 Mike



 --
 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] Re (2): Another possible ambiguity of target; a drive part not acceptable to the installer.

2012-12-20 Thread Rugxulo
Hi,

On Wed, Dec 19, 2012 at 12:37 PM,  peasth...@shaw.ca wrote:

 From:   Rugxulo rugx...@gmail.com
 Date:   Wed, 19 Dec 2012 16:31:31 -0600
 Do you also have a working floppy drive? Working CD drive?

 Both.  I had hoped to use the CD made from file fd11src.iso
 to install FreeDOS.  Isn't that the recommended procedure?

Yes and no. Bernd was very insistent on having things automated as
much as possible, and he worked very hard on it. But he didn't include
every old DOS package in the universe, even compared to older 1.0. So
it's not a super duper full install like some OSes (which give you
lots of pre-built third-party stuff).

Others of us (e.g. me) find it easier to manually install in minimal
pieces than go the automated route. So if you know what you're doing
or have specific needs, an automated installer may not be what you
want (though it's certainly nice to have both options, IMO).

 FDISK creates at least one partition (primary, active, FAT, presumably
 bootable) for DOS. (This is written into the partition table, ...

 OK.  If it damages the table in the process, there will be
 a problem accessing data on parts 2, 3 or 4.  Exactly what
 I wish to avoid.

Multibooting is so confusing for a billion reasons, not the least of
which is that all OSes do things differently.

As mentioned, you can always back up your MBR if you're worried. And
there are tons of external tools for these kinds of things.

If you're worried about any personal data, back it up to external
drive (USB?) before installing / reconfiguring anything.

 Go back to Debian, or
 even better use GParted (if possible) or SPFdisk, ...

 The FreeDOS 1.1 Base CD offers to apply fdisk;  but you
 recommend not using it?  An installer which should not be used?

FreeDOS traditionally comes with three fdisk tools. And plenty more
exist out in the wild. FD FDISK is Brian Reifsnyder's
classic-style version. Then there's XFDISK, written in Turbo Pascal
(IIRC). And SPFdisk supports SATA disks and various other niceties. I
think the latter two have custom boot sectors they can install (and/or
boot monitors, I forget exactly, lots of options).

 ... make sure the partition (drive) ...

 There's that ambiguity again.  Do you mean hard disk drive as
 in /dev/sda or part of a drive as in /dev/sda1, /dev/sda2 and etc.

 Ref. http://www.catb.org/~esr/writings/cups-horror.html

I was trying to separate the distinction. Disk is the whole
(presumably one) physical hard drive disk. Drive here is the primary
FAT partition which DOS is installed and attempts to boots from. (I
also vaguely recall auxiliary DOS FAT extended partitions being called
logical drives.)

--
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] Stack overflow

2012-12-20 Thread Tom Ehlert
 Hello list:
asking programming errors on a mailing list that is focused on
operating system development is considered BAD.

 I am having Stack Overflow problems with this simple code under FreeDOS and
 OpenWatcom:

 #include stdio.h

 char a[8192];

 int main()
 {
 int i;
 char b[8192];
 for(i=0; i8192; i++) a[i]=b[i]=0;
 return 0;
 }

 I keep getting stack overflow problems.

 I know this code is very simple and meaningless, but it's an example of how
 I am having stack overflow problems with static arrays of size 8192.

b is a dynamic array on the stack.

 Excuse me if the mail is too off-topic, but I think the problem is
 something to do with memory.
I won't excuse.


 If you use stack=4096, it means the default stack size might be much
 smaller than the 16384 I am using.
most likely  you are not using 16384. 

Tom


--
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] Stack overflow

2012-12-20 Thread Rugxulo
Hi,

On Thu, Dec 20, 2012 at 2:28 PM, Santiago Almenara almen...@gmail.com wrote:

 Where can I find the default size for the watcom stack?

Dunno. I think it used to be 4 kb for 16-bit targets, but they may??
have increased it to 16 kb in the meantime.

http://www.openwatcom.com/index.php/C_Compilers_Release_Changes

That says 1.7 increased 32-bit stack from 4 kb to 64 kb by default.
(But 16-bit stack is probably smaller for obvious reasons.)

(Note that I vaguely remember the warning that any map file created
won't reflect changes in stack and only reports default size.)

 If you use stack=4096, it means the default stack size might be much
 smaller than the 16384 I am using.

Don't put big arrays on the stack. As mentioned, dynamically allocate
them from the heap via malloc or similar. Or statically declare them
global, but    ;-)

BTW, stack= is a WLINK option. I think you can also change it at
compile time with -k switch. (Not sure if there is any functional
difference here, doubt it, just mentioning for completeness.)

-kstack_size set stack size

--
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] freedos-98

2012-12-20 Thread Rugxulo
Hi,

On Wed, Dec 19, 2012 at 10:14 PM, Michael Robinson
plu...@robinson-west.com wrote:

 So yes, if I can run hxrt on top of freedos and come up with some sort
 of packet driver for the PCI Realtek network card...  that will be legal
 and I won't have to worry about how many computers I'm setting
 up to play Warcraft II.

No idea if Warcraft II actually runs under HX. It may not, and that
wouldn't be a huge shock. Sad but true. Go back to Warcraft 1 (or
similar game, search Gog.com), which actually ran on real DOS.

But as far as Realtek goes, here's two packet drivers, not sure which
one you need (or other), but give 'em a try:

http://www.georgpotthast.de/sioux/packet.htm

Honestly, though, I'm not too savvy with Wattcp, you may have to set
WATTCP=wattcp.cfg and change it to my_ip = dhcp or such. (mTCP is
easier to use, IMHO, but that's separate from HX.)

But thinking of all the crap that Windows games need, it's unlike to
work (well, if at all) under HXGUI, even if you did manage to find all
the proprietary .DLLs you need.

Not trying to smash your dreams, just saying, almost nobody ever had
the foresight with such old games to make them portable.

 A 98 clone or ReactOS stabilized is definitely needed for these old
 games.  DOS is a good choice on aging computers where anything that
 operates at speeds below a gigaherz is an antique already, except for
 embedded processors.

I am against abandoning or throwing out working hardware just
because it's not the latest fad anymore. But most people want to chase
newer tech than support older stuff. If it's old, it's automatically
bad, but new is somehow perfect (but only for a few months!).

--
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] Stack overflow

2012-12-20 Thread Ralf A. Quint
At 12:58 PM 12/20/2012, Louis Santillan wrote:
The Memory Model (Tiny vs. Small vs. Compact vs. Medium vs. Large, 
.COM vs. .EXE) of the compiler could be causing the issue. Some 
compilers used to default to Small.  What compiler flags are you using?

Even in the TINY model, there is no reason to get a stack overflow, 
if the compiler indeed is not artificially limiting the stack size.
The sample program is using 8KB static data, 8KB+some slack for stack 
and likely 2KB of code, as there is no output like printf. All well 
below of the limit of 64KB.
SMALL and MEDIUM memory models only have static data and stack in the 
same segment and separate 64KB for code, while COMPACT, LARGE and 
HUGE (Borland only) even have their own 64KB stack segment...

This should compile and run, regardless of the memory model...

Ralf 


--
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] Stack overflow

2012-12-20 Thread Michael B. Brutman
On 12/20/2012 2:41 PM, Tom Ehlert wrote:
 asking programming errors on a mailing list that is focused on
 operating system development is considered BAD.


I don't think we have enough developers (OS or application) or enough 
list traffic where we can afford to be picky ...



Mike


--
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] Stack overflow

2012-12-20 Thread Michael B. Brutman
On 12/20/2012 3:11 PM, Ralf A. Quint wrote:
 At 12:58 PM 12/20/2012, Louis Santillan wrote:
 The Memory Model (Tiny vs. Small vs. Compact vs. Medium vs. Large,
 .COM vs. .EXE) of the compiler could be causing the issue. Some
 compilers used to default to Small.  What compiler flags are you using?
 Even in the TINY model, there is no reason to get a stack overflow,
 if the compiler indeed is not artificially limiting the stack size.
 The sample program is using 8KB static data, 8KB+some slack for stack
 and likely 2KB of code, as there is no output like printf. All well
 below of the limit of 64KB.
 SMALL and MEDIUM memory models only have static data and stack in the
 same segment and separate 64KB for code, while COMPACT, LARGE and
 HUGE (Borland only) even have their own 64KB stack segment...

 This should compile and run, regardless of the memory model...

 Ralf

Ah, but the compiler probably is creating some boundaries based on 
having to fit static variables, code, near heap and stack all in the 
same segment.

This is a simple problem to fix.  The Watcom linker guide has a 
discussion of the STACK= option.  You can create a map file and look at 
it to see what the default is for your particular memory model. (They 
wisely did not publish the defaults, as they might change from release 
to release.)


Mike


--
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] Stack overflow

2012-12-20 Thread Tom Ehlert
 At 12:58 PM 12/20/2012, Louis Santillan wrote:
The Memory Model (Tiny vs. Small vs. Compact vs. Medium vs. Large, 
.COM vs. .EXE) of the compiler could be causing the issue. Some 
compilers used to default to Small.  What compiler flags are you using?

 Even in the TINY model, there is no reason to get a stack overflow, 
 if the compiler indeed is not artificially limiting the stack size.
there's a very good reason to limit stack size.

most compilers use a memory setup like

static initialized data( hello world )
static uninitialized data( a[8000] )
stack   (usually 1-4 K unless specified different)
heap( to be used by malloc())

stack is initialized either by the linker (the .EXE format
has a filed for SS:SP), or early during RTL initialization.

 The sample program is using 8KB static data, 8KB+some slack for stack
 and likely 2KB of code, as there is no output like printf. All well 
 below of the limit of 64KB.
sure. just linkit with stacksize of 9K



 SMALL and MEDIUM memory models only have static data and stack in the 
 same segment and separate 64KB for code, while COMPACT, LARGE and 
 HUGE (Borland only) even have their own 64KB stack segment...

 This should compile and run, regardless of the memory model...
no.

Tom



--
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] Stack overflow

2012-12-20 Thread Tom Ehlert
 asking programming errors on a mailing list that is focused on
 operating system development is considered BAD.

 I don't think we have enough developers (OS or application) or enough 
 list traffic where we can afford to be picky ...

this is stillnot the 'programming for dummies' mailing list.

https://groups.google.com/forum/?fromgroups=#!forum/comp.os.msdos.programmer
might be better suited

Tom


--
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] Re (2): Another possible ambiguity of target; a drive part not acceptable to the installer.

2012-12-20 Thread Jim Hall
On Thu, Dec 20, 2012 at 10:22 AM,  peasth...@shaw.ca wrote:
 From:   Jim Hall jh...@freedos.org
 Date:   Wed, 19 Dec 2012 06:55:23 -0600
 It wants to run the FORMAT command, which operates on one partition to lay
 down a DOS file system. If you want to be really safe you can run mkdosfs
 from Debian to put a DOS file system on that partition, then boot the
 FreeDOS installer again.

 Thanks.  It appeared to install to the first part of a CF card OK, although
 the system fails to boot from it.  I must have missed something at the
 end of the installation process.


It may be obvious, but you should also check that your BIOS supports
booting from CF cards.

--
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


[Freedos-user] Stack overflow

2012-12-20 Thread bruce.bowman tds.net
Static/global variables are allocated from the heap. Dynamic variables
(like the b array in your code) are pushed on the stack.

Either use compiler directives to increase stack space or make both arrays
static.

This is not a FreeDOS problem and should not have been posted to this list.

Bruce

-- Sent from my meager, humble desktop computer.
--
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


[Freedos-user] Re (2): Re (2): Another possible ambiguity of target; a drive part not acceptable to the installer.

2012-12-20 Thread peasthope
From:   Bernd Blaauw bbla...@home.nl
Date:   Thu, 20 Dec 2012 21:28:55 +0100
 'Drive' is a typical DOS terminology, meaning partition/volume, thus 
 sda1 etc. It's used as 'Drive C:'. Basically referring to everything 
 which has a driveletter assigned (floppy, harddisk, cdrom, network 
 shares, etc).

Well that was OK when diskettes were the only rotating media.  Usually 
a diskette wasn't partitioned.  Part and volume were synonymous.  
Where a hard disk drive is involved, drive should mean hard disk drive 
and part should mean part of a hard disk drive.  When software 
says it will format the drive I want to be sure it doesn't mean format 
the whole hard disk drive.  Unambiguous terminology really does help.

I had hoped to run FreeDOS on the OLPC XO-1.5 but it is no simple problem.
http://wiki.laptop.org/go/Talk:Our_software

Regards,... Peter E.





-- 
123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
Tel +13606390202  Bcc: peasthope at shaw.ca  http://carnot.yi.org/  
http://members.shaw.ca/peasthope/index.html#Itinerary 


--
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


[Freedos-user] Re (5): Another possible ambiguity of target;

2012-12-20 Thread peasthope
From:   Jim Hall jh...@freedos.org
Date:   Thu, 20 Dec 2012 17:17:26 -0600
 It may be obvious, but you should also check that your BIOS supports
 booting from CF cards.

Just tried to boot an older FreeDOS installed years ago on another CF card.
It appears OK until this.

Bad or missing Command Interpreter
Enter the full shell command line: 
command.com /P /E:256

Seems hopeful ... if configured correctly or a command.com is added. 
Can the current installation process using the CD set these things?  
Human intervention required?

Thanks,  ... Peter E.

-- 
123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
Tel +13606390202  Bcc: peasthope at shaw.ca  http://carnot.yi.org/  
http://members.shaw.ca/peasthope/index.html#Itinerary 


--
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] freedos-98

2012-12-20 Thread TJ Edmister
On Thu, 20 Dec 2012 15:58:34 -0500, Rugxulo rugx...@gmail.com wrote:

 Hi,

 On Wed, Dec 19, 2012 at 10:14 PM, Michael Robinson
 plu...@robinson-west.com wrote:

 So yes, if I can run hxrt on top of freedos and come up with some sort
 of packet driver for the PCI Realtek network card...  that will be legal
 and I won't have to worry about how many computers I'm setting
 up to play Warcraft II.

 No idea if Warcraft II actually runs under HX. It may not, and that
 wouldn't be a huge shock. Sad but true. Go back to Warcraft 1 (or
 similar game, search Gog.com), which actually ran on real DOS.

There may have been a Windows-specific version of Warcraft II released at  
some point? But the Warcraft II that I`m familiar with did run under plain  
DOS (well... with DOS4GW). Only the included map editor needed Windows  
(3.1 or higher) to run. And I played LAN games under DOS by setting up an  
IPX network. Check the device driver archive for the ethernet card for: a  
setup program (for configuring IRQ and I/O address, not all cards come  
with one), LSL.COM, NET.CFG, and a driver (often called IPXODI).


*snip*

 I am against abandoning or throwing out working hardware just
 because it's not the latest fad anymore. But most people want to chase
 newer tech than support older stuff. If it's old, it's automatically
 bad, but new is somehow perfect (but only for a few months!).

This is my feeling as well. The implications of buy our new version!  
because our old version was crap! seem to be lost on most.

--
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


[Freedos-user] Windows 98SE and ipxwrapper...

2012-12-20 Thread Michael Robinson
Windows 98 sort of running on top of a DOS system doesn't work with
ipxwrapper-0.4.0.  There is an error that iplphapi.dll can't be found
or something similar.  Turns out, this DLL probably doesn't show up
till Windows 2000.  So the thought of using Windows 98 boxes and 
Windows 7 boxes together goes out the Window.  A game that was
originally run from the DOS command line if I'm not mistaken can't
be run from Windows 98SE when Windows 7 is the master server.  Yikes!

Hmm, I guess I could run 2000 instead even though the computer is only
a K6-2 500 and I'd probably have to search for SIS 530 W2K video
drivers.  Don't have a legal 2nd copy of 2000, but there doesn't seem to
be a legal way to solve this.  There are a lot of games that aren't 
DOS games and aren't NT games.  Windows 98 in my opinion is a sort 
of aberration, Microsoft should have skipped Windows 9x in favor of
bringing everyone into an NT environment sooner.

I'm sure there is a dos driver for my Realtek 8139 10/100 network card.
But ipxwrapper is intended for NT and HX probably won't run Warcraft II.

I'd love something legal that isn't the full blown Windows 98SE to run
games like Warcraft II and Diablo II that are in that transitional
period.  I just hope that the ReactOS developers get something stable
put together soon.

I have a Windows XP Home upgrade kit, it is in use though.  I'm worried
that XP won't even run on this old machine, but I guess stripped down I
can get away with it.  Sadly, XP phones home so Microsoft will know that
I'm running it illegally.

What is needed is a protected mode DOS like Windows 98SE, but much
lighter, that can run directx 6 or so and do the ipxwrapper trick.


--
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] Windows 98SE and ipxwrapper...

2012-12-20 Thread Felix Miata
On 2012-12-20 21:32 (GMT-0800) Michael Robinson composed:

 I'd probably have to search for SIS 530 W2K video drivers.

Asus P5S-B motherboards had the 530 chip on the board. Maybe Asus still has 
those ancient drivers for download. I have the driver CD for it here 
somewhere, but it would be older than W2K. If you can't find it let me know. 
Maybe it has an NT driver that would work.
-- 
The wise are known for their understanding, and pleasant
words are persuasive. Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

--
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] Windows 98SE and ipxwrapper...

2012-12-20 Thread TJ Edmister
On Fri, 21 Dec 2012 00:32:18 -0500, Michael Robinson  
plu...@robinson-west.com wrote:

 Windows 98 sort of running on top of a DOS system doesn't work with
 ipxwrapper-0.4.0.  There is an error that iplphapi.dll can't be found
 or something similar.

Why do you need an ipx wrapper on win98? You can install the IPX protocol  
natively under the network control panel and DOS programs running within  
Windows will be able to use it.

 Hmm, I guess I could run 2000 instead even though the computer is only
 a K6-2 500 and I'd probably have to search for SIS 530 W2K video
 drivers.

If SIS 530 has a VESA 2.0 BIOS you could try the VBEMP universal driver.

*snip*
 I'm sure there is a dos driver for my Realtek 8139 10/100 network card.

This is quite likely. RTL8139 has drivers for everything. Even NT 3.51.  
Even Amiga.

--
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] Windows 98SE and ipxwrapper...

2012-12-20 Thread Michael C. Robinson

Quoting TJ Edmister damag...@hyakushiki.net:

 On Fri, 21 Dec 2012 00:32:18 -0500, Michael Robinson
 plu...@robinson-west.com wrote:

 Windows 98 sort of running on top of a DOS system doesn't work with
 ipxwrapper-0.4.0.  There is an error that iplphapi.dll can't be found
 or something similar.

 Why do you need an ipx wrapper on win98? You can install the IPX protocol
 natively under the network control panel and DOS programs running within
 Windows will be able to use it.

Well, if I use IPX wrapper I'm no longer using standard IPX networking, I
am tunneling via UDP.  The Windows 98 client understandably can't find an
IPX network because strictly speaking there isn't one.  This is why you
have to use IPX wrapper under Windows XP even though XP has native IPX
support.  There is really only a problem when Windows 7 is introduced.
A better workaround would be an open source IPX/SPX implementation that
works on all versions of Windows up to 8.


--
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