Re: [Freedos-user] Bolitare (Bolitaire) "Error loading datafile"

2006-09-27 Thread John Hupp
Yes, I ran it from C:\FDOS\GAMES\BOLITARE.

But I tested with 32MB instead of 16MB and it worked.  So it turns out that 
the program simply has an unpublished minimum requirement this machine 
didn't meet.

--John Hupp

- Original Message - 
From: Blair Campbell
To: freedos-user@lists.sourceforge.net
Sent: Tuesday, September 26, 2006 9:55 PM
Subject: Re: [Freedos-user] Bolitare (Bolitaire) "Error loading datafile"


were you in the same directory as the executable?

-- 
Fall is my favorite season in Los Angeles, watching the birds change
color and fall from the trees.
   David Letterman (1947 - )

See ya

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user 


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] OpenGEM - GEM.BAT fails with ChDir under FreeDOS 1.0

2006-09-27 Thread John Hupp



We're working over/tripping over some small 
details here, but many people won't know what to do with an error message like 
this and will just give up.  So a little background and a fresh detail or 
two:
 
Background:
 
OpenGEM 4 and 5 used this command in 
C:\GEM.BAT:
CD\GEMAPPS\GEMSYS\
 
This worked fine in MS-DOS 6 but the version of 
FreeCOM current at the time failed without a space after CD.
 
OpenGEM 6 attempted to adjust to FreeCOM by using 
this command:
 
CD GEMAPPS\GEMSYS
 
This executes fine if entered from the command 
line at C:\ and will make the current 
directory C:\GEMAPPS\GEMSYS.  But if you put that command in a batch 
file at C:\TEST.BAT and then ChDir to C:\FDOS and rely on PATH or native ability 
to find and run TEST.BAT in the root directory, you will generate the error 
"CHDIR failed for 'GEMAPPS\GEMSYS.'"
 
If you edit TEST.BAT to CD \GEMAPPS\GEMSYS (adding 
the initial backslash), it will run fine.  Contrary to what I said earlier, 
you do not need to enter the full drive:\path to get a successful fix.  In 
fact, with the current version of FreeCOM, you can once again omit the space 
after CD.
 
In short, there is still a small deviation 
from behavior under MS-DOS 6.  But previously when I entered a 
program-startup command from an improper location (like trying to start DESCENT 
from FDOS\BIN, to make up an example) FreeDOS would tend to run something like 
C:\SETUP (the GEM setup program).  So this may be progress.
 
--John Hupp
 
- Original Message - 
From: Eric Auer 
To: freedos-user@lists.sourceforge.net 

Sent: Tuesday, September 26, 2006 6:42 PM
Subject: Re: [Freedos-user] OpenGEM - GEM.BAT fails with ChDir under 
FreeDOS 1.0
Hi John,> ... the GEM.BAT installed by GEM 6 
bundled with FreeDOS> 1.0 fails at CD \GEMAPPS\GEMSYS if you try to start 
GEM from outside the> root directory (where GEM.BAT is located) on a pure 
FreeDOS machine.> To work around that, do a search-and-replace in GEM.BAT 
to change all> instances to CD C:\GEMAPPS\GEMSYS.There are two 
oddities in GEM here:1. it assumes that you start gem.bat from the same 
drive whereyou have GEM installed and2. gem.bat should be in, for 
example, c:\fdos\bin instead of in c:\(which is sth. which the FreeDOS 
installer, not GEM, should tweak...)The first issue should be worked 
around by usingc:CD \GEMapps\GEMsysinstead of only using the "CD" 
line. Because usingCD c:\GEMapps\GEMsys still does not force going to 
C:Using CDD c:\GEMapps\GEMsys would, but would be FreeCOM specific,so 
the better solution is to use the above two line one.However, FreeCOM 
has behaved odd for me recently (since I updatedfrom 1.0 base to 1.0 full) - 
sometimes it just stops to run programs!No error message or anything, just 
does not run the programs any more.This might depend on whether doslfn is 
loaded, not sure. Any 
ideas?Eric-Take 
Surveys. Earn Cash. Influence the Future of ITJoin SourceForge.net's Techsay 
panel and you'll get the chance to share youropinions on IT & business 
topics through brief surveys -- and earn cashhttp://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___Freedos-user 
mailing listFreedos-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/freedos-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


[Freedos-user] DOSFSCK issue

2006-09-27 Thread John Hupp
This concerns a pure FreeDOS machine (Pentium 120, 16MB) having a 4.3GB hard 
drive with a single FAT32 partition created by the CD Installer's partition 
and format tools after the drive had been zero-filled.

Except for the few problems I've reported here, things seem to be working 
fine with a couple dozen games, Arachne, CD players, networking, and more, 
but I wanted to try the DOSFSCK tool for FAT32.

Running DOSFSCK -N C: generates a screen of 5 columns, each "row-field" 
entry being of a format like ", 504:20/00" and then under that set of 
columnar data:
Not automatically fixing this
malloc: general problems
Aborting

Running DOSFSCK -R C: generates the same screen of data followed by:
1) Copy original to backup
2) Copy backup to original
3) No action
? _
Entering 3 results in:
malloc: general problems
Aborting

I booted with a Win 98 startup disk and ran Scandisk, and it found no 
problems.

So it seems both that DOSFSCK is finding problems and is also having a hard 
time running, though I don't know what the program output is supposed to 
look like.

Where do I start here?

--John Hupp 


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user