Re: [Freedos-user] XP NTVDM

[Rugxulo]

Hi,

On Tue, Nov 27, 2012 at 10:47 PM, kurt godel  wrote:
>
> As touchy as xp ntvdm can be(oh!illegal instruction!), my little gui
> runs flawlessly in the box or in
> dos itself. In fact, with one teeny change in a parameter, it even ran in
> dosemu, which by the way,
> no longer runs right in linux mint 13(sigh).

Try these, and see if it helps:

sudo sysctl vm.mmap_low_addr=0
sudo sesetbool -P mmap_low_allowed 1

--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bruce3

[bruce.bowman tds.net]

Bret -- I booted up my CD and ran your DRIVES program. Here's the output in
a small monospaced font, I hope you can read it:

DRIVES 0.01, (C) 2007-2009, Bret E. Johnson.
Shows details about all available disk drives in DOS.

   ATTRIBS
  Í A
D N N S C   PHYSICAL ATTRIBUTES
r e e P J U DRIVE   C 
i t t h O B  DEVICE DRVR  PARAMETER E   NUM   BYTES
v H w y I S Í   BLOCK   S FAT   ROOT  PER  NUM APPROX
e d k s N T  ADDRESS  UNT  ADDRESS  d TYPE  ENTRY SECT   SECTORS  CAPACITY
Í Í Í ÍÍÍ Í Í Í Í Í Í 
A . . Y . . 0070:060E   0 00D9:19FA Y FAT12   224   512 0B21h  1458 kB
B . . Y . . 0070:060E   1 00D9:1A37 . ? 0 0 Unknown   Unknown
C . . Y . . 0070:060E   2 00D9:1A74 Y FAT32 0   512 090A8A62h75 GB
D . . Y . . 0070:060E   3 00D9:1AB1 . ? 0 0 Unknown   Unknown
E . . Y . . 08E5:   0 0A3F: Y FAT32 0   512 00EFFFE0h  8051 MB
F . . . . . . ... : . . . . . 
G . . . . . . ... : . . . . . 
etc...
X . . . . . . ... : . . . . . 
Y Y Y Y . . . ... : . . . . . 
Z . . Y . . 1A88:   0 1A88:012C Y FAT16   512   512 00019004h 52430 kB

Something is definitely wrong with nonexistent drive D:, and I suspected
the source to be one or both of the USB device drivers usbaspi.sys or
di1000dd.sys. These drivers were the ones recommended by the DFSee live CD
that I've been hacking for this project.

Just for kicks, I disabled BOTH of the drivers. Not only did that take care
of the original problem, but FreeDOS still found the thumbdrive -- this
time at drive D:

DRIVES 0.01, (C) 2007-2009, Bret E. Johnson.
Shows details about all available disk drives in DOS.

   ATTRIBS
  Í A
D N N S C   PHYSICAL ATTRIBUTES
r e e P J U DRIVE   C 
i t t h O B  DEVICE DRVR  PARAMETER E   NUM   BYTES
v H w y I S Í   BLOCK   S FAT   ROOT  PER  NUM APPROX
e d k s N T  ADDRESS  UNT  ADDRESS  d TYPE  ENTRY SECT   SECTORS  CAPACITY
Í Í Í ÍÍÍ Í Í Í Í Í Í 
A . . Y . . 0070:060E   0 00D9:19FA Y FAT12   224   512 0B21h  1458 kB
B . . Y . . 0070:060E   1 00D9:1A37 . ? 0 0 Unknown   Unknown
C . . Y . . 0070:060E   2 00D9:1A74 Y FAT32 0   512 090A8A62h75 GB
D . . Y . . 0070:060E   3 00D9:1AB1 Y FAT32 0   512 00EFFFE0h  8051 MB
E . . . . . . ... : . . . . . 
F . . . . . . ... : . . . . . 
etc...
X . . . . . . ... : . . . . . 
Y Y Y Y . . . ... : . . . . . 
Z . . Y . . 163A:   0 163A:012C Y FAT16   512   512 00019004h 52430 kB

As an added benefit I'm also getting better mouse behavior. :^/

As the author of this program you apparently have some expertise regarding
USB drives and FreeDOS. If you could advise me as to whether loading either
of these drivers (or some other driver) would provide the most stable
configuration it would be appreciated on this end. For now, I'm leaving
both of them disabled.

Thanks for your help!

Bruce


On Tue, Nov 27, 2012 at 10:56 PM, bruce.bowman tds.net 
wrote:
>
> I'll give it a try later, thanks.
>
> It's important to understand that once I boot into FreeDOS there is no
physical disk partition corresponding to drive D:. My FAT32 partition
(which is drive D: under XP) gets mapped to drive C: in FreeDOS. However, I
do have a drive E:, which is the USB thumbdrive. Could it be that the
FreeDOS kernel sees a drive E: and therefore expects a drive D: to exist
too? Beats me...
>
> What I mainly need things to do in this situation is to fail gracefully.
Thanks again for the utility and I'll let you know what happens.
>
> Bruce
>
>
> On Tue, Nov 27, 2012 at 8:35 PM, Bret Johnson  wrote:
>>
>> You can look at the output of my DRIVES program for the D: drive when
using FreeDOS.  It will probably indicate that something is wrong in one or
more of DOS's internal tables.  DRIVES is not intended to be used in batch
files, but simply displays some information about all of the drive letters
from DOS's perspective.  It's usually a pretty good troubleshooting tool
for situations like this.
>>
>> DRIVES is one of the programs included in my USB driver package
available here:
>>
>> http://bretjohnson.us
>>
>>
--
>> Keep yourself connected to Go Parallel:
>> INSIGHTS What's next for parallel hardware, programming and related
areas?
>> Interviews and blogs by th

[Freedos-user] XP NTVDM

[kurt godel]

Believe it or not, the xp ntvdm allows the int33 for mouse calls; I wrote a
lite gui which mimics
dos, but in upper and lower bilateral windows, and lets you select the
entries with the mouse.
The thing is written in C(djgpp), but makes extensive use of dos batchfiles.
As touchy as xp ntvdm can be(oh!illegal instruction!), my little gui
runs flawlessly in the box or in
dos itself. In fact, with one teeny change in a parameter, it even ran in
dosemu, which by the way,
no longer runs right in linux mint 13(sigh).
--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS bootable CD image sought

[bruce.bowman tds.net]

Yeah, I still have the source. I get an itch to work on it every few years.

DosBox ain't gonna happen. If I decide to go the emulator route it will be
VM.

Bruce


On Tue, Nov 27, 2012 at 8:39 PM, Rugxulo  wrote:

> Hi,
>
> On Tue, Nov 27, 2012 at 2:01 PM, bruce.bowman tds.net
>  wrote:
> >
> > I think it was written in Turbo C++ 3.0. It's been awhile. I've
> uninstalled
> > it because I thought I had a backup around here. If not, I'm sure I can
> find
> > images of the install disks on the web somewhere. I probably have it on
> > floppies (ha ha).
>
> Embarcadero has Turbo C++ 1.01, but it's only "freeware" to registered
> users of their other (newer) products, oddly enough. And you can't
> redistribute it. And you've gotta give them lots of personal info for
> free registration.
>
> Long story short:  OpenWatcom is open source and supports 16-bit DOS
> targets and C++, so that's a better bet.
>
> http://www.openwatcom.org/index.php/Main_Page
>
>
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/c/openwatcom/1.9/
>
> > Back in the early 90s I had a shareware door "business" that was active
> in
> > FidoNet and DoorNet before the web took over and the dialup BBS became
> > passe'. It was called Dirt Cheap Software, and fully lived up to its
> name --
> > I didn't make any money, but it kept me out of trouble.
>
> I was pretty young in those days, so I only used BBSes for about two
> years or so before the Internet became ubiquitous. They were cool,
> though, definitely.
>
> > Palletized 640x480x256 colors requires VBE 3.0. I reserved certain
> entries
> > in the palette because those colors were used to draw other things on the
> > screen. Otherwise the status bar, text, etc would be constantly changing
> > colors as new images are put up.
>
> I don't know, I'm no graphics guru. Do you still have sources? If so,
> at least in theory you could fix it. (Or binary patch, heheh.)
>
> > Total storage is about 23 MB and growing, mainly because of the number of
> > images, and the fact that they use only RLE compression to help them
> display
> > quickly. The program itself is pretty small.
>
> Yikes.
>
> > I have an account on the Vogons site, in hopes they would help me get my
> > application running in DosBox. But the responses to the inquiries that
> I've
> > posted there have been universally abrupt. If people persist in
> "helping" by
> > talking over my head and acting intellectually superior then I prefer
> not to
> > play in their sandbox.
>
> I found the thread. It's not that abrupt. I think they might help more
> if you give them more details.
>
> http://vogons.zetafleet.com/viewtopic.php?t=33987
>
> 1). Try changing the video card setting in the dosbox-0.74.conf file
> (or similar copy). Mix and match, play with it a bit. Describe to them
> exactly what it's doing and what it "should" be doing. Take a
> screenshot (esp. since DOSBox supports this natively, Ctrl-F5, unless
> I'm remembering incorrectly, then check your Program
> Files\dosbox\captures subdir or whatever). Extra credit for
> screenshots of physical hardware running the game correctly.
> 2). Upload your game somewhere so they can test or debug it. (I know
> it's big, but ... if at all possible )
> 3). Ask them what specific files are needed (and where to get) S3 +
> BIOS add-ons and how to test it.
>
>
> --
> Keep yourself connected to Go Parallel:
> INSIGHTS What's next for parallel hardware, programming and related areas?
> Interviews and blogs by thought leaders keep you ahead of the curve.
> http://goparallel.sourceforge.net
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>



-- 
 Sent from my meager, humble desktop computer.
--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bruce3

[bruce.bowman tds.net]

I'll give it a try later, thanks.

It's important to understand that once I boot into FreeDOS there is no
physical disk partition corresponding to drive D:. My FAT32 partition
(which is drive D: under XP) gets mapped to drive C: in FreeDOS. However, I
do have a drive E:, which is the USB thumbdrive. Could it be that the
FreeDOS kernel sees a drive E: and therefore expects a drive D: to exist
too? Beats me...

What I mainly need things to do in this situation is to fail gracefully.
Thanks again for the utility and I'll let you know what happens.

Bruce

On Tue, Nov 27, 2012 at 8:35 PM, Bret Johnson  wrote:

> You can look at the output of my DRIVES program for the D: drive when
> using FreeDOS.  It will probably indicate that something is wrong in one or
> more of DOS's internal tables.  DRIVES is not intended to be used in batch
> files, but simply displays some information about all of the drive letters
> from DOS's perspective.  It's usually a pretty good troubleshooting tool
> for situations like this.
>
> DRIVES is one of the programs included in my USB driver package available
> here:
>
> http://bretjohnson.us
>
>
> --
> Keep yourself connected to Go Parallel:
> INSIGHTS What's next for parallel hardware, programming and related areas?
> Interviews and blogs by thought leaders keep you ahead of the curve.
> http://goparallel.sourceforge.net
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>



-- 
 Sent from my meager, humble desktop computer.
--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Possible problem with Turkish keyboard layouts

[Rugxulo]

Ho, ve, porkajhon mi sendis? Ververe ne! Kanajloj, kial hontigi min per
senbaza trompo? Forvishu viajn mensogojn!

On Nov 27, 2012 9:36 PM, "Rugxulo"  wrote:
>
> Saluton,
>
> On Nov 27, 2012 8:04 PM, "Henrique Peron"  wrote:
> >
> >
> > Em 27/11/2012 16:37, thraex escreveu:
> > > On 27/11/12 19:47, Henrique Peron wrote:
> > >> Em 27/11/2012 13:16, thraex escreveu:
> > >> Merhaba Thraex,
> > > Merhaba Henrique :)
> > Nasılsınız? :)
>
> Aaah, dotless i, Isildur's bane:-)
>
> > > Thanks for explaining, but how do I select these codepages?
> > Please check your AUTOEXEC.BAT file.
> >
> > Make sure there are lines like these:
> >
> > 
> > display con=(ega,,3)
> > mode con cp prepare=((853,857,858) c:\freedos\cpi\ega.cpx)
> > mode con cp select=xxx
> > keyb tr
> > 
> >
> > The four lines above prepare and select 3 codepages, all
> > available on EGA.CPX. You'll trade "xxx" in the third line for:
>
> Yes, but they don't have to be all in the same *.CPX, as you kindly told
me a while back. I just wanted to prove that.   :-)
>
> > • 853, if you need to type turkish — and/or esperanto. It is important
to mention, though, that codepage 853 seems to be considered obsolete on
what concerns the turkish language. (Codepage 853 is the only one which
handles esperanto.)
>
> 'Tis true. Though most E-o users are wise enough to use cx, jx, ktp. when
only 7-bit ASCII is available. So it's no huge loss unless you want to save
screen char usage or need to mix the two.
>
> > • 857, if you don't need esperanto. A good thing about codepage 857 is
that it not only seems to be the preferred codepage for turkish; you'll
have the Euro sign.
>
> Yes, we can't bear "EU", it's too painful.   :-)
>
> > Before I forget: Ruĝulo tried to help but his coordinates are meant for
the greek language. (codepages 737, 869...) (Thanks anyway, Ruĝulo! :))
>
> Yes, I know, it was just a better example than the MODE help gave, more
complex.
>
> P.S. If anyone has ideas or wants to help Mike Brutman add 8-bit / UTF-8
support to his (mTCP) IRCjr, feel free to whip up any patches or whatever,
he seems oddly interested! (Krokodilu inter malsamideanoj? Ho, ghoje!)
--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS bootable CD image sought

[Chris Evans]

I got turboc on my server at FTP://digitalatoll.com/PUB/ELITE/WAREZ/


On Tuesday, November 27, 2012, Rugxulo wrote:

> Hi,
>
> On Tue, Nov 27, 2012 at 2:01 PM, bruce.bowman tds.net
> > wrote:
> >
> > I think it was written in Turbo C++ 3.0. It's been awhile. I've
> uninstalled
> > it because I thought I had a backup around here. If not, I'm sure I can
> find
> > images of the install disks on the web somewhere. I probably have it on
> > floppies (ha ha).
>
> Embarcadero has Turbo C++ 1.01, but it's only "freeware" to registered
> users of their other (newer) products, oddly enough. And you can't
> redistribute it. And you've gotta give them lots of personal info for
> free registration.
>
> Long story short:  OpenWatcom is open source and supports 16-bit DOS
> targets and C++, so that's a better bet.
>
> http://www.openwatcom.org/index.php/Main_Page
>
>
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/c/openwatcom/1.9/
>
> > Back in the early 90s I had a shareware door "business" that was active
> in
> > FidoNet and DoorNet before the web took over and the dialup BBS became
> > passe'. It was called Dirt Cheap Software, and fully lived up to its
> name --
> > I didn't make any money, but it kept me out of trouble.
>
> I was pretty young in those days, so I only used BBSes for about two
> years or so before the Internet became ubiquitous. They were cool,
> though, definitely.
>
> > Palletized 640x480x256 colors requires VBE 3.0. I reserved certain
> entries
> > in the palette because those colors were used to draw other things on the
> > screen. Otherwise the status bar, text, etc would be constantly changing
> > colors as new images are put up.
>
> I don't know, I'm no graphics guru. Do you still have sources? If so,
> at least in theory you could fix it. (Or binary patch, heheh.)
>
> > Total storage is about 23 MB and growing, mainly because of the number of
> > images, and the fact that they use only RLE compression to help them
> display
> > quickly. The program itself is pretty small.
>
> Yikes.
>
> > I have an account on the Vogons site, in hopes they would help me get my
> > application running in DosBox. But the responses to the inquiries that
> I've
> > posted there have been universally abrupt. If people persist in
> "helping" by
> > talking over my head and acting intellectually superior then I prefer
> not to
> > play in their sandbox.
>
> I found the thread. It's not that abrupt. I think they might help more
> if you give them more details.
>
> http://vogons.zetafleet.com/viewtopic.php?t=33987
>
> 1). Try changing the video card setting in the dosbox-0.74.conf file
> (or similar copy). Mix and match, play with it a bit. Describe to them
> exactly what it's doing and what it "should" be doing. Take a
> screenshot (esp. since DOSBox supports this natively, Ctrl-F5, unless
> I'm remembering incorrectly, then check your Program
> Files\dosbox\captures subdir or whatever). Extra credit for
> screenshots of physical hardware running the game correctly.
> 2). Upload your game somewhere so they can test or debug it. (I know
> it's big, but ... if at all possible )
> 3). Ask them what specific files are needed (and where to get) S3 +
> BIOS add-ons and how to test it.
>
>
> --
> Keep yourself connected to Go Parallel:
> INSIGHTS What's next for parallel hardware, programming and related areas?
> Interviews and blogs by thought leaders keep you ahead of the curve.
> http://goparallel.sourceforge.net
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] [Spam] Re: [Spam] Possible problem with Turkish keyboard layouts

[Henrique Peron]

Em 27/11/2012 16:37, thraex escreveu:
> On 27/11/12 19:47, Henrique Peron wrote:
>> Em 27/11/2012 13:16, thraex escreveu:
>> Merhaba Thraex,
> Merhaba Henrique :)
Nasılsınız? :)
> Thanks for explaining, but how do I select these codepages? Also, please
> note that the case I reported happens right after a normal installation
> of FreeDOS, therefore I was wondering whether there's something that
> needs to be fixed or adjusted so that if the user chooses these layouts,
> things will work without additional configuration (or an information
> indicating that some additional configuration is needed will be displayed).
Please check your AUTOEXEC.BAT file.

Make sure there are lines like these:


display con=(ega,,3)
mode con cp prepare=((853,857,858) c:\freedos\cpi\ega.cpx)
mode con cp select=xxx
keyb tr


The four lines above prepare and select 3 codepages, all available on EGA.CPX. 
You'll trade "xxx" in the third line for:

• 853, if you need to type turkish — and/or esperanto. It is important to 
mention, though, that codepage 853 seems to be considered obsolete on what 
concerns the turkish language. (Codepage 853 is the only one which handles 
esperanto.)

• 857, if you don't need esperanto. A good thing about codepage 857 is that it 
not only seems to be the preferred codepage for turkish; you'll have the Euro 
sign.

• 858, highly recommended to type in "western european" languages. I say 
"recommended" instead of "needed" because you could perfectly use cp857 to type 
in, say, portuguese, spanish, italian, etc., however I don't advise you to do 
that. If you'd like to know why, just let me know.

Before I forget: Ruĝulo tried to help but his coordinates are meant for the 
greek language. (codepages 737, 869...) (Thanks anyway, Ruĝulo! :))

> If it's possible for you, IMHO the best mean to examine the "bug" is to
> install FreeDOS on your side with say VirtualBox and choose keyboard
> option 19, then do the same with option 59 and see if the installation
> process is OK for you. If not, the good news would be that things can be
> improved :)
I'll do that. I use VirtualBox. ;)
> Çok teşekkürler.
Birşey değil.

Should anything still not goes well as it should, please let me know.

Allahaısmarladık,
Henrique

--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bruce3

[Bret Johnson]

You can look at the output of my DRIVES program for the D: drive when using 
FreeDOS.  It will probably indicate that something is wrong in one or more of 
DOS's internal tables.  DRIVES is not intended to be used in batch files, but 
simply displays some information about all of the drive letters from DOS's 
perspective.  It's usually a pretty good troubleshooting tool for situations 
like this.

DRIVES is one of the programs included in my USB driver package available here:

http://bretjohnson.us

--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS bootable CD image sought

[Rugxulo]

Hi,

On Tue, Nov 27, 2012 at 2:01 PM, bruce.bowman tds.net
 wrote:
>
> I think it was written in Turbo C++ 3.0. It's been awhile. I've uninstalled
> it because I thought I had a backup around here. If not, I'm sure I can find
> images of the install disks on the web somewhere. I probably have it on
> floppies (ha ha).

Embarcadero has Turbo C++ 1.01, but it's only "freeware" to registered
users of their other (newer) products, oddly enough. And you can't
redistribute it. And you've gotta give them lots of personal info for
free registration.

Long story short:  OpenWatcom is open source and supports 16-bit DOS
targets and C++, so that's a better bet.

http://www.openwatcom.org/index.php/Main_Page

http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/c/openwatcom/1.9/

> Back in the early 90s I had a shareware door "business" that was active in
> FidoNet and DoorNet before the web took over and the dialup BBS became
> passe'. It was called Dirt Cheap Software, and fully lived up to its name --
> I didn't make any money, but it kept me out of trouble.

I was pretty young in those days, so I only used BBSes for about two
years or so before the Internet became ubiquitous. They were cool,
though, definitely.

> Palletized 640x480x256 colors requires VBE 3.0. I reserved certain entries
> in the palette because those colors were used to draw other things on the
> screen. Otherwise the status bar, text, etc would be constantly changing
> colors as new images are put up.

I don't know, I'm no graphics guru. Do you still have sources? If so,
at least in theory you could fix it. (Or binary patch, heheh.)

> Total storage is about 23 MB and growing, mainly because of the number of
> images, and the fact that they use only RLE compression to help them display
> quickly. The program itself is pretty small.

Yikes.

> I have an account on the Vogons site, in hopes they would help me get my
> application running in DosBox. But the responses to the inquiries that I've
> posted there have been universally abrupt. If people persist in "helping" by
> talking over my head and acting intellectually superior then I prefer not to
> play in their sandbox.

I found the thread. It's not that abrupt. I think they might help more
if you give them more details.

http://vogons.zetafleet.com/viewtopic.php?t=33987

1). Try changing the video card setting in the dosbox-0.74.conf file
(or similar copy). Mix and match, play with it a bit. Describe to them
exactly what it's doing and what it "should" be doing. Take a
screenshot (esp. since DOSBox supports this natively, Ctrl-F5, unless
I'm remembering incorrectly, then check your Program
Files\dosbox\captures subdir or whatever). Extra credit for
screenshots of physical hardware running the game correctly.
2). Upload your game somewhere so they can test or debug it. (I know
it's big, but ... if at all possible )
3). Ask them what specific files are needed (and where to get) S3 +
BIOS add-ons and how to test it.

--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bruce3

[bruce.bowman tds.net]

I'm not inclined to bash XP too much. Windoze ME was the Vista of its time.
You know what I'm talking about.

If Linux had someone doing marketing -- and bundling it with new PCs --
that's what everyone would be running today. Don't get me started.  :^)

Bruce

On Tue, Nov 27, 2012 at 8:29 PM, Rugxulo  wrote:

> Hi,
>
> On Tue, Nov 27, 2012 at 7:25 PM, bruce.bowman tds.net
>  wrote:
> > I've not written or edited a lot of files using the command line in XP
> but
> > it seems to be able to read and write to any supported file system
> without
> > problems. Hard to say exactly what is handling that but I seriously doubt
> > I'll be calling any interrupts in my batch program.  :^)
>
> I know, but it's important to know (barely). Win2000 was the first
> NT-based OS to support FAT32 and the Win9x LFN API (int 21h, 71xxh).
> NT 4.0 (1996) didn't. So my point is that XP (based upon 2000 but for
> now also for home users) was hacked together somewhat roughly to
> replace WinME, and after a while, MS stopped caring about fixing bugs.
> So we're left with buggy and incomplete DOS emulation in some ways.
> :-/
>
>
> --
> Keep yourself connected to Go Parallel:
> INSIGHTS What's next for parallel hardware, programming and related areas?
> Interviews and blogs by thought leaders keep you ahead of the curve.
> http://goparallel.sourceforge.net
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>



-- 
 Sent from my meager, humble desktop computer.
--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bruce3

[Rugxulo]

Hi,

On Tue, Nov 27, 2012 at 7:25 PM, bruce.bowman tds.net
 wrote:
> I've not written or edited a lot of files using the command line in XP but
> it seems to be able to read and write to any supported file system without
> problems. Hard to say exactly what is handling that but I seriously doubt
> I'll be calling any interrupts in my batch program.  :^)

I know, but it's important to know (barely). Win2000 was the first
NT-based OS to support FAT32 and the Win9x LFN API (int 21h, 71xxh).
NT 4.0 (1996) didn't. So my point is that XP (based upon 2000 but for
now also for home users) was hacked together somewhat roughly to
replace WinME, and after a while, MS stopped caring about fixing bugs.
So we're left with buggy and incomplete DOS emulation in some ways.
:-/

--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bruce3

[Rugxulo]

Hi,

On Tue, Nov 27, 2012 at 7:21 PM, bruce.bowman tds.net
>>
>> But usually you should (mostly) be able to know in advance what drive
>> letters you are choosing, and save that info for later.
>
> Having booted from a CD with an OS that probably can't read all his
> partitions, we can't assume the user knows what the new drive letters are
> going to be ahead of time. Wanting this process to be as transparent as
> possible, while probing for a writeable partition I'll have to store
> whatever information I can collect in the environment.

I know, but it's more difficult if you purposely don't choose specific
letters ahead of time. Often times it's not hard to know in advance
what drive you're loading to.

>> > Any installation program really needs to know three things:
>> > -- Does a drive exist
>>
>> If all your active drives have known volume labels, you can use Eric's
>> FINDDISK.
>>
>> > -- How much free space is present.
>>
>> Eric's FREETEST.
>
>
> Who is Eric and where can these utilities be obtained?

Eric Auer, FreeDOS guru extraordinaire! :-)

http://ericauer.cosmodata.virtuaserver.com.br/soft/specials/

--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bruce3

[bruce.bowman tds.net]

I've not written or edited a lot of files using the command line in XP but
it seems to be able to read and write to any supported file system without
problems. Hard to say exactly what is handling that but I seriously doubt
I'll be calling any interrupts in my batch program.  :^)

Thanks again for your thoughtful replies and responsiveness.

Bruce

On Tue, Nov 27, 2012 at 8:05 PM, Rugxulo  wrote:

> Hi,
>
> On Tue, Nov 27, 2012 at 6:50 PM, bruce.bowman tds.net
>  wrote:
> >
> > One correction: on my XP machine using the CMD command interpreter,
> whichfat
> > reports every existing drive as FAT16. I guess that kinda makes sense as
> > it's the native format for DOS and I guess Windows converts file formats
> > before doing disk i/o.
>
> No. I forgot that XP is fairly braindead. It's not a real DOS, it's
> just a buggy VM (NTVDM). It's not totally reliable, sadly. DOS is dead
> to them, so they don't fix bugs or even maintain the code.
>
> XP fails on a lot of FAT32 stuff, but I don't honestly know offhand
> what WHICHFAT tries to do. Presumably you can read the FAT partition
> directly (but maybe? Windows forbids it?). Or maybe it's checking the
> volume type, but I forget which int 21h call that is. (I guess I
> should look, but the point is that XP is unreliable for some DOS
> things, though admittedly nice when it does work.)
>
> P.S. Not 100% what I was thinking of, but check this:
>
> http://www.delorie.com/djgpp/doc/rbinter/id/23/32.html
>
>
> --
> Keep yourself connected to Go Parallel:
> INSIGHTS What's next for parallel hardware, programming and related areas?
> Interviews and blogs by thought leaders keep you ahead of the curve.
> http://goparallel.sourceforge.net
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>



-- 
 Sent from my meager, humble desktop computer.
--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bruce3

[bruce.bowman tds.net]

> > for %%d in (c d e f g h i j k l m n o p q r s t u v w x) do (
>
> for %%d in (c d e f g h i j k l m n o p q r s t u v w x) do call blah1.bat
>
> >   if exist %%d:\mygame\ (
>
> if exist %%d:\mygame\ call blah2.bat


Yeah, that's pretty much where I was headed.


> Perhaps you could run a subshell (%comspec% /f /c blah.bat) for that.
> "/f" should auto-fail.
>

That could work.


> But usually you should (mostly) be able to know in advance what drive
> letters you are choosing, and save that info for later.


Having booted from a CD with an OS that probably can't read all his
partitions, we can't assume the user knows what the new drive letters are
going to be ahead of time. Wanting this process to be as transparent as
possible, while probing for a writeable partition I'll have to store
whatever information I can collect in the environment.

> Any installation program really needs to know three things:
> > -- Does a drive exist
>
> If all your active drives have known volume labels, you can use Eric's
> FINDDISK.
>
> > -- Is it writeable
>
> Dunno


REM > c:\filename was a way to probe this in MS-DOS, nbt sure about FreeDOS.


>

> -- How much free space is present.
>
> Eric's FREETEST.


Who is Eric and where can these utilities be obtained?

Thanks,
Bruce
--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bruce3

[Rugxulo]

Hi,

On Tue, Nov 27, 2012 at 6:50 PM, bruce.bowman tds.net
 wrote:
>
> One correction: on my XP machine using the CMD command interpreter, whichfat
> reports every existing drive as FAT16. I guess that kinda makes sense as
> it's the native format for DOS and I guess Windows converts file formats
> before doing disk i/o.

No. I forgot that XP is fairly braindead. It's not a real DOS, it's
just a buggy VM (NTVDM). It's not totally reliable, sadly. DOS is dead
to them, so they don't fix bugs or even maintain the code.

XP fails on a lot of FAT32 stuff, but I don't honestly know offhand
what WHICHFAT tries to do. Presumably you can read the FAT partition
directly (but maybe? Windows forbids it?). Or maybe it's checking the
volume type, but I forget which int 21h call that is. (I guess I
should look, but the point is that XP is unreliable for some DOS
things, though admittedly nice when it does work.)

P.S. Not 100% what I was thinking of, but check this:

http://www.delorie.com/djgpp/doc/rbinter/id/23/32.html

--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bruce3

[Rugxulo]

Hi,

On Tue, Nov 27, 2012 at 6:43 PM, bruce.bowman tds.net
 wrote:
>
> My batch file seems to have two problems, one of which is that FreeDOS does
> not allow compound IFs and/or FOR nesting of any kind. I can work around
> that, but the second problem is the one that I'm really struggling with.

.BAT isn't really suitable for heavy scripting. But there are always
kludgy workarounds. Or you could just use 4DOS, AWK, REXX, BWBASIC,
etc.

Or the easiest is probably to put the "..." from "if blah ..." into
separate .BAT (and similarly for the "..." in "for %%a in (blah) do
...").

> for %%d in (c d e f g h i j k l m n o p q r s t u v w x) do (

for %%d in (c d e f g h i j k l m n o p q r s t u v w x) do call blah1.bat

>   if exist %%d:\mygame\ (

if exist %%d:\mygame\ call blah2.bat

> Some background: When I boot up using my new CD, the floppy drive image is
> assigned drive A:. The CD itself is assigned drive Y:. My computer has one
> physical hard drive with two partitions, the first being NTFS and the second
> FAT32. The FAT32 partition gets assigned drive letter C: while NTFS does not
> get a drive letter (of course). I also load a USB driver which assigns my
> thumb drive with the letter E:  So far, so good.
>
> So I'm trying to use some of the code below in a batch file to see which
> drives are present. Things go well until we try the following:
>
> IF EXIST D:\NUL ECHO Y
> Error reading from Drive D:  DOS area:  unknown command given to driver
>
> The same thing happens when I use WHICHFAT D:. I've read about similar
> problems happening using FreeDOS within DOSEMU in Linux. All versions of
> MS-DOS and the command line interpreter within Windows fail gracefully
> (i.e.: they don't report a drive), even for DOS 6.22.

Perhaps you could run a subshell (%comspec% /f /c blah.bat) for that.
"/f" should auto-fail.

But usually you should (mostly) be able to know in advance what drive
letters you are choosing, and save that info for later.

> Any installation program really needs to know three things:
> -- Does a drive exist

If all your active drives have known volume labels, you can use Eric's FINDDISK.

> -- Is it writeable

Dunno.

> -- How much free space is present.

Eric's FREETEST.

> If I can't meet these objectives then I'm pretty much at an impasse. If
> anyone can offer an alternative please advise.

Don't worry, it can't be too hard.

--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bruce3

[bruce.bowman tds.net]

And clarification:  I get the dreaded (A)bort (I)gnore (R)etry (F)ail
options along with the error message.

Bruce

On Tue, Nov 27, 2012 at 7:50 PM, bruce.bowman tds.net
wrote:

> One correction: on my XP machine using the CMD command interpreter,
> whichfat reports every existing drive as FAT16. I guess that kinda makes
> sense as it's the native format for DOS and I guess Windows converts file
> formats before doing disk i/o.
>
> Booting under DOS 6.22, whichfat reports FAT drive formats correctly and
> reports NTFS drives as missing. I haven't tried 7.1 yet.
>
> Bruce
>
>
> On Tue, Nov 27, 2012 at 7:43 PM, bruce.bowman tds.net <
> bruce.bow...@tds.net> wrote:
>
>> My batch file seems to have two problems, one of which is that FreeDOS
>> does not allow compound IFs and/or FOR nesting of any kind. I can work
>> around that, but the second problem is the one that I'm really struggling
>> with.
>>
>> Some background: When I boot up using my new CD, the floppy drive image
>> is assigned drive A:. The CD itself is assigned drive Y:. My computer has
>> one physical hard drive with two partitions, the first being NTFS and the
>> second FAT32. The FAT32 partition gets assigned drive letter C: while NTFS
>> does not get a drive letter (of course). I also load a USB driver which
>> assigns my thumb drive with the letter E:  So far, so good.
>>
>> So I'm trying to use some of the code below in a batch file to see which
>> drives are present. Things go well until we try the following:
>>
>> IF EXIST D:\NUL ECHO Y
>> Error reading from Drive D:  DOS area:  unknown command given to driver
>>
>> The same thing happens when I use WHICHFAT D:. I've read about similar
>> problems happening using FreeDOS within DOSEMU in Linux. All versions of
>> MS-DOS and the command line interpreter within Windows fail gracefully
>> (i.e.: they don't report a drive), even for DOS 6.22.
>>
>> Any installation program really needs to know three things:
>> -- Does a drive exist
>> -- Is it writeable
>> -- How much free space is present.
>>
>> If I can't meet these objectives then I'm pretty much at an impasse. If
>> anyone can offer an alternative please advise.
>>
>> Thanks,
>> Bruce
>>
>>
>>
>> On Tue, Nov 27, 2012 at 2:30 PM, bruce.bowman tds.net <
>> bruce.bow...@tds.net> wrote:
>>
>>> Right now I have something like this going on.
>>>
>>> A: is the floppy bootup image.
>>> B: could be a floppy so I don't want that to be probed
>>> Y: is the drive letter assigned to the CD that I booted from.
>>> Z: is a ramdrive.
>>>
>>> for %%d in (c d e f g h i j k l m n o p q r s t u v w x) do (
>>>   if exist %%d:\mygame\ (
>>>  cls
>>>  echo.
>>>  echo.
>>>  echo.
>>>  echo A previous installation of MYGAME was found on drive %%d:
>>>  choice /B /N /C:YN /T:Y,10 Should I run the game from this location
>>> [recommended]
>>>  if not errorlevel 2 (
>>>swsubst %progdisk% %%d:\mygame\
>>>goto finish
>>>  )
>>>   )
>>> )
>>>
>>> REM either didn't find an installation, or didn't want to use it
>>> set progdisk = z:
>>> copy Y:\mygame\*.*  %progdisk% > nul
>>>
>>> :finish
>>> %progdisk%
>>> rungame
>>>
>>> FreeDOS doesn't seem to like the compound IF very much. Thoughts
>>> appreciated.
>>>
>>> Bruce
>>>
>>>
>>> On Tue, Nov 27, 2012 at 1:49 PM, Bernd Blaauw  wrote:
>>>
 Op 27-11-2012 6:45, bruce.bowman tds.net schreef:

 > In fact I am essentially done with my project but still want
 something I
 > can throw in a batch file to probe for writeable drive letters so I
 can
 > give the user an opportunity to save a game and resume later (like
 they
 > used to).

 DOS kernels only assign driveletters to FAT filesystems. For (emulated?)
 floppy drives A: and B: get assigned, thus C: till Z: get assigned to
 everything else.

 A FAT filesystem contains the NUL blockdevice, making it easy to test:

 @echo off
 IF EXIST C:\NUL echo Driveletter C: points to a FAT filesystem.

 Testing if you can store files on the drive is a different issue
 altogether, as it involves:
 * checking if the drive isn't full yet
 * checking if the drive isn't write-protected (read-only)
 * checking if there's enough free diskspace

 Bernd


 --
 Monitor your physical, virtual and cloud infrastructure from a single
 web console. Get in-depth insight into apps, servers, databases, vmware,
 SAP, cloud infrastructure, etc. Download 30-day Free Trial.
 Pricing starts from $795 for 25 servers or applications!
 http://p.sf.net/sfu/zoho_dev2dev_nov
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user

>>>
>>>
>>>
>>> --
>>>  Sent from my meager, humble desktop computer.
>>>
>>>
>>
>>
>> --
>>  Sent fr

Re: [Freedos-user] Bruce3

[bruce.bowman tds.net]

One correction: on my XP machine using the CMD command interpreter,
whichfat reports every existing drive as FAT16. I guess that kinda makes
sense as it's the native format for DOS and I guess Windows converts file
formats before doing disk i/o.

Booting under DOS 6.22, whichfat reports FAT drive formats correctly and
reports NTFS drives as missing. I haven't tried 7.1 yet.

Bruce

On Tue, Nov 27, 2012 at 7:43 PM, bruce.bowman tds.net
wrote:

> My batch file seems to have two problems, one of which is that FreeDOS
> does not allow compound IFs and/or FOR nesting of any kind. I can work
> around that, but the second problem is the one that I'm really struggling
> with.
>
> Some background: When I boot up using my new CD, the floppy drive image is
> assigned drive A:. The CD itself is assigned drive Y:. My computer has one
> physical hard drive with two partitions, the first being NTFS and the
> second FAT32. The FAT32 partition gets assigned drive letter C: while NTFS
> does not get a drive letter (of course). I also load a USB driver which
> assigns my thumb drive with the letter E:  So far, so good.
>
> So I'm trying to use some of the code below in a batch file to see which
> drives are present. Things go well until we try the following:
>
> IF EXIST D:\NUL ECHO Y
> Error reading from Drive D:  DOS area:  unknown command given to driver
>
> The same thing happens when I use WHICHFAT D:. I've read about similar
> problems happening using FreeDOS within DOSEMU in Linux. All versions of
> MS-DOS and the command line interpreter within Windows fail gracefully
> (i.e.: they don't report a drive), even for DOS 6.22.
>
> Any installation program really needs to know three things:
> -- Does a drive exist
> -- Is it writeable
> -- How much free space is present.
>
> If I can't meet these objectives then I'm pretty much at an impasse. If
> anyone can offer an alternative please advise.
>
> Thanks,
> Bruce
>
>
>
> On Tue, Nov 27, 2012 at 2:30 PM, bruce.bowman tds.net <
> bruce.bow...@tds.net> wrote:
>
>> Right now I have something like this going on.
>>
>> A: is the floppy bootup image.
>> B: could be a floppy so I don't want that to be probed
>> Y: is the drive letter assigned to the CD that I booted from.
>> Z: is a ramdrive.
>>
>> for %%d in (c d e f g h i j k l m n o p q r s t u v w x) do (
>>   if exist %%d:\mygame\ (
>>  cls
>>  echo.
>>  echo.
>>  echo.
>>  echo A previous installation of MYGAME was found on drive %%d:
>>  choice /B /N /C:YN /T:Y,10 Should I run the game from this location
>> [recommended]
>>  if not errorlevel 2 (
>>swsubst %progdisk% %%d:\mygame\
>>goto finish
>>  )
>>   )
>> )
>>
>> REM either didn't find an installation, or didn't want to use it
>> set progdisk = z:
>> copy Y:\mygame\*.*  %progdisk% > nul
>>
>> :finish
>> %progdisk%
>> rungame
>>
>> FreeDOS doesn't seem to like the compound IF very much. Thoughts
>> appreciated.
>>
>> Bruce
>>
>>
>> On Tue, Nov 27, 2012 at 1:49 PM, Bernd Blaauw  wrote:
>>
>>> Op 27-11-2012 6:45, bruce.bowman tds.net schreef:
>>>
>>> > In fact I am essentially done with my project but still want something
>>> I
>>> > can throw in a batch file to probe for writeable drive letters so I can
>>> > give the user an opportunity to save a game and resume later (like they
>>> > used to).
>>>
>>> DOS kernels only assign driveletters to FAT filesystems. For (emulated?)
>>> floppy drives A: and B: get assigned, thus C: till Z: get assigned to
>>> everything else.
>>>
>>> A FAT filesystem contains the NUL blockdevice, making it easy to test:
>>>
>>> @echo off
>>> IF EXIST C:\NUL echo Driveletter C: points to a FAT filesystem.
>>>
>>> Testing if you can store files on the drive is a different issue
>>> altogether, as it involves:
>>> * checking if the drive isn't full yet
>>> * checking if the drive isn't write-protected (read-only)
>>> * checking if there's enough free diskspace
>>>
>>> Bernd
>>>
>>>
>>> --
>>> Monitor your physical, virtual and cloud infrastructure from a single
>>> web console. Get in-depth insight into apps, servers, databases, vmware,
>>> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>>> Pricing starts from $795 for 25 servers or applications!
>>> http://p.sf.net/sfu/zoho_dev2dev_nov
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>>
>>
>>
>> --
>>  Sent from my meager, humble desktop computer.
>>
>>
>
>
> --
>  Sent from my meager, humble desktop computer.
>
>


-- 
 Sent from my meager, humble desktop computer.
--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
ht

Re: [Freedos-user] [Spam] Possible problem with Turkish keyboard layouts

[Rugxulo]

Hi,

On Tue, Nov 27, 2012 at 1:37 PM, thraex  wrote:
> On 27/11/12 19:47, Henrique Peron wrote:
>
> Thanks for explaining, but how do I select these codepages? Also, please
> note that the case I reported happens right after a normal installation
> of FreeDOS, therefore I was wondering whether there's something that
> needs to be fixed or adjusted so that if the user chooses these layouts,
> things will work without additional configuration (or an information
> indicating that some additional configuration is needed will be displayed).

The installer is just a "best guess" type of thing, not perfect by any
stretch. It may be trite to assume users are already familiar with
DOS, but that's somewhat implied.

http://help.fdos.org/en/hhstndrd/base/mode.htm

But here's a partial (better?) solution:

===
set CPIDIR=%DOSDIR%\cpi
display con=(ega,,3)
mode con cp prep=((853) %CPIDIR%\ega.cpx)
mode con cp prep=((,737,869) %CPIDIR%\ega5.cpx)
mode con cp sel=%DEFAULT%
set CPIDIR=

if "%DEFAULT%"=="853" keyb us,,%DOSDIR%\keyboard.sys
if not "%DEFAULT%"=="853" keyb gk,,%DOSDIR%\keybrd2.sys
echo.
echo KEYB: Ctrl-Alt-F1 to disable or Ctrl-Alt-F2 to re-enable!
echo.
===

P.S. More specifically, it would be nice to know which codepage(s) and
keyboard layouts you personally intend to use for your language. (Or
did I miss that part?)   :-)

--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bruce3

[bruce.bowman tds.net]

My batch file seems to have two problems, one of which is that FreeDOS does
not allow compound IFs and/or FOR nesting of any kind. I can work around
that, but the second problem is the one that I'm really struggling with.

Some background: When I boot up using my new CD, the floppy drive image is
assigned drive A:. The CD itself is assigned drive Y:. My computer has one
physical hard drive with two partitions, the first being NTFS and the
second FAT32. The FAT32 partition gets assigned drive letter C: while NTFS
does not get a drive letter (of course). I also load a USB driver which
assigns my thumb drive with the letter E:  So far, so good.

So I'm trying to use some of the code below in a batch file to see which
drives are present. Things go well until we try the following:

IF EXIST D:\NUL ECHO Y
Error reading from Drive D:  DOS area:  unknown command given to driver

The same thing happens when I use WHICHFAT D:. I've read about similar
problems happening using FreeDOS within DOSEMU in Linux. All versions of
MS-DOS and the command line interpreter within Windows fail gracefully
(i.e.: they don't report a drive), even for DOS 6.22.

Any installation program really needs to know three things:
-- Does a drive exist
-- Is it writeable
-- How much free space is present.

If I can't meet these objectives then I'm pretty much at an impasse. If
anyone can offer an alternative please advise.

Thanks,
Bruce


On Tue, Nov 27, 2012 at 2:30 PM, bruce.bowman tds.net
wrote:

> Right now I have something like this going on.
>
> A: is the floppy bootup image.
> B: could be a floppy so I don't want that to be probed
> Y: is the drive letter assigned to the CD that I booted from.
> Z: is a ramdrive.
>
> for %%d in (c d e f g h i j k l m n o p q r s t u v w x) do (
>   if exist %%d:\mygame\ (
>  cls
>  echo.
>  echo.
>  echo.
>  echo A previous installation of MYGAME was found on drive %%d:
>  choice /B /N /C:YN /T:Y,10 Should I run the game from this location
> [recommended]
>  if not errorlevel 2 (
>swsubst %progdisk% %%d:\mygame\
>goto finish
>  )
>   )
> )
>
> REM either didn't find an installation, or didn't want to use it
> set progdisk = z:
> copy Y:\mygame\*.*  %progdisk% > nul
>
> :finish
> %progdisk%
> rungame
>
> FreeDOS doesn't seem to like the compound IF very much. Thoughts
> appreciated.
>
> Bruce
>
>
> On Tue, Nov 27, 2012 at 1:49 PM, Bernd Blaauw  wrote:
>
>> Op 27-11-2012 6:45, bruce.bowman tds.net schreef:
>>
>> > In fact I am essentially done with my project but still want something I
>> > can throw in a batch file to probe for writeable drive letters so I can
>> > give the user an opportunity to save a game and resume later (like they
>> > used to).
>>
>> DOS kernels only assign driveletters to FAT filesystems. For (emulated?)
>> floppy drives A: and B: get assigned, thus C: till Z: get assigned to
>> everything else.
>>
>> A FAT filesystem contains the NUL blockdevice, making it easy to test:
>>
>> @echo off
>> IF EXIST C:\NUL echo Driveletter C: points to a FAT filesystem.
>>
>> Testing if you can store files on the drive is a different issue
>> altogether, as it involves:
>> * checking if the drive isn't full yet
>> * checking if the drive isn't write-protected (read-only)
>> * checking if there's enough free diskspace
>>
>> Bernd
>>
>>
>> --
>> Monitor your physical, virtual and cloud infrastructure from a single
>> web console. Get in-depth insight into apps, servers, databases, vmware,
>> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>> Pricing starts from $795 for 25 servers or applications!
>> http://p.sf.net/sfu/zoho_dev2dev_nov
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>
>
>
> --
>  Sent from my meager, humble desktop computer.
>
>


-- 
 Sent from my meager, humble desktop computer.
--
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Oberon; was Re (2): Re (2): FreeDOS bootable CD image sought

[peasthope]

From:   Rugxulo 
Date:   Mon, 26 Nov 2012 18:53:13 -0600
> Which version would you recommend?

I've used the last "alpha" release since it became available.
ftp://ftp.ethoberon.ethz.ch/ETHOberon/Native/Update/Alpha/

It has a few bugs.  Some solved.  
http://carnot.yi.org/OberonPage.html  Server is down 
temporarily.  Check in a day or two.

None of the bugs are serious enough to deter use of the 
system.

> My minimal attempts to boot OberonOS were unsuccessful. 

It's the most trouble free and efficient installation process 
I've ever tried.

> It's kind of bitrotted over the years ...

What problems do you find?

> Also emulators always have trouble with
> less-popular OSes.Any further discussion will fit better here.

The release cited above runs on bare hardware.  Hence "native".  
If you don't have an old PC already, one should be easily 
found. Check the disposal area of any educational institution, 
flea markets, garage sales & etc.

Further discussion will fit better here.
https://lists.inf.ethz.ch/mailman/listinfo/oberon

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 "


--
Keep yourself connected to Go Parallel: 
DESIGN Expert tips on starting your parallel project right.
http://goparallel.sourceforge.net
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS bootable CD image sought

[bruce.bowman tds.net]

It's true that a lot of developers just quit supporting their products.

I once figured out how much I was making for all the time I was spending on
Dirt Cheap Software. It came to about 15 cents per hour. But I wasn't doing
it for the money -- it was more of a hobby than a business.

I still have a file in my desk of the registration forms that some BBS
sysops sent in, and it remains gratifying to know that somebody found my
efforts to be worthwhile.

Bruce


On Tue, Nov 27, 2012 at 3:09 PM, Chris Evans  wrote:

> The possible reason you didn't make any money off our shareware biz is
> that people back then were
> Not sure if they would receive the full version for the money sent,  scams
>
>
--
Keep yourself connected to Go Parallel: 
DESIGN Expert tips on starting your parallel project right.
http://goparallel.sourceforge.net___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS bootable CD image sought

[Chris Evans]

The possible reason you didn't make any money off our shareware biz is that
people back then were
Not sure if they would receive the full version for the money sent,  scams

On Tuesday, November 27, 2012, bruce.bowman tds.net wrote:

> Just a few replies...
>
> I think it was written in Turbo C++ 3.0. It's been awhile. I've
> uninstalled it because I thought I had a backup around here. If not, I'm
> sure I can find images of the install disks on the web somewhere. I
> probably have it on floppies (ha ha).
>
> Back in the early 90s I had a shareware door "business" that was active in
> FidoNet and DoorNet before the web took over and the dialup BBS became
> passe'. It was called Dirt Cheap Software, and fully lived up to its name
> -- I didn't make any money, but it kept me out of trouble.
>
> Palletized 640x480x256 colors requires VBE 3.0. I reserved certain entries
> in the palette because those colors were used to draw other things on the
> screen. Otherwise the status bar, text, etc would be constantly changing
> colors as new images are put up.
>
> Total storage is about 23 MB and growing, mainly because of the number of
> images, and the fact that they use only RLE compression to help them
> display quickly. The program itself is pretty small.
>
> I have an account on the Vogons site, in hopes they would help me get my
> application running in DosBox. But the responses to the inquiries that I've
> posted there have been universally abrupt. If people persist in "helping"
> by talking over my head and acting intellectually superior then I prefer
> not to play in their sandbox.
>
> Back to the coal mine...
>
> Bruce
>
>
> On Mon, Nov 26, 2012 at 7:47 PM, Rugxulo  wrote:
>
> Hi,
>Just a few answers:
>
> On Mon, Nov 26, 2012 at 4:51 PM, bruce.bowman tds.net
>  wrote:
>
> (part one)
>
> > My program is a fairly simple role-playing game. It was originally
> written
> > in Turbo C for DOS, and reads/writes to disk using DOS (not BIOS) calls.
>
> (BTW, which Turbo C version? Some here still use it.)
>
> So it's not NTFS that is bothering you, nor 32-bit NTVDM, just the
> lack of VESA support?
>
> > It runs in 256 palletized colors on a 640x480 console.
>
> I don't know jack about graphics, honestly. But IIRC the "normal" BIOS
> only supports 640x480x16 (16 colors?) or some such. It couldn't be too
> too hard to adjust to running in fewer colors (although not ideal)
> e.g. under WinXP. And/or you could just resize your .PCX image files,
> etc.
>
> > While running, it
> > frequently reads image files off disk, and for that reason won't fit on
> (or
> > reliably run from) a floppy. I want to share it with friends such that
> all
> > they have to do is insert a CD and boot up.
>
> But how much total storage do you need? More than 1.4 MB? You could
> uncompress it from physical floppy to RAM disk if speed is an issue.
> It's not that floppies are so great, but they've been around forever
> and have fairly good support and are fairly simple to use, modify,
> emulate, etc.
>
> > Having said that, I've tried DosBox, just for my own purposes. My
> > program runs very slowly in it, no matter what settings I use;
>
> notepad dosbox-0.74.conf
> (change memsize=16 to memsize=32 if desired)
> (change core=auto to core=dynamic)
> (try again)
> (revert changes or use a separate .conf for certain projects)
>
> I'll admit it can be fairly slow, but it's mostly for popular games.
> In fact, it's "only" for games, as the devs often admit. But Doom and
> Quake (mostly) run perfectly fine under it, etc. etc.
>
> Since your game is an actual game, you could always post on the DOSBox
> forum (Vogons / ZetaFleet or whatever) and bug the devs to fix it for
> you. Assuming you're willing to share with them also.
>
> I know you don't like emulators (who does?), but when they work, they
> work well. And DOSBox is small and easy to use (and GPL).
>
> > and
> > for some reason the graphics palette does not get reset properly.
> > I've downloaded VM too, but haven't tried that yet, and for
> > reasons already mentioned I probably won't.
>
> Well, the point is that DOSBox is a natural solution for DOS gaming.
> Of course, it's not a "real" DOS, per se, but it works pretty well.
> However, if you're unwilling to hack at it some more in cooperation
> with DOSBox devs, then you'll have to find another way.
>
> It's not that booting a CD is bad, but sometimes people like not
> having to reboot (and lose network access, background processes, etc.)
> just to play a game.
>
> > The DFSee CD image that someone else recommended looks like
> > something I can modify for my purposes. I've already booted off
> > of that and confirmed that the game runs well...here at home,
> > anyway. And it seems to detect and do i/o on my FAT32 partition
> > just fine. NTFS? I'll worry about that later.
>
> The problem with NTFS is moreso in the overhead, both memory and
> storage, not to mention its inherent security that is underdocumented
> on purpose (and of co

Re: [Freedos-user] FreeDOS bootable CD image sought

[bruce.bowman tds.net]

Just a few replies...

I think it was written in Turbo C++ 3.0. It's been awhile. I've uninstalled
it because I thought I had a backup around here. If not, I'm sure I can
find images of the install disks on the web somewhere. I probably have it
on floppies (ha ha).

Back in the early 90s I had a shareware door "business" that was active in
FidoNet and DoorNet before the web took over and the dialup BBS became
passe'. It was called Dirt Cheap Software, and fully lived up to its name
-- I didn't make any money, but it kept me out of trouble.

Palletized 640x480x256 colors requires VBE 3.0. I reserved certain entries
in the palette because those colors were used to draw other things on the
screen. Otherwise the status bar, text, etc would be constantly changing
colors as new images are put up.

Total storage is about 23 MB and growing, mainly because of the number of
images, and the fact that they use only RLE compression to help them
display quickly. The program itself is pretty small.

I have an account on the Vogons site, in hopes they would help me get my
application running in DosBox. But the responses to the inquiries that I've
posted there have been universally abrupt. If people persist in "helping"
by talking over my head and acting intellectually superior then I prefer
not to play in their sandbox.

Back to the coal mine...

Bruce


On Mon, Nov 26, 2012 at 7:47 PM, Rugxulo  wrote:

> Hi,
>Just a few answers:
>
> On Mon, Nov 26, 2012 at 4:51 PM, bruce.bowman tds.net
>  wrote:
>
> (part one)
>
> > My program is a fairly simple role-playing game. It was originally
> written
> > in Turbo C for DOS, and reads/writes to disk using DOS (not BIOS) calls.
>
> (BTW, which Turbo C version? Some here still use it.)
>
> So it's not NTFS that is bothering you, nor 32-bit NTVDM, just the
> lack of VESA support?
>
> > It runs in 256 palletized colors on a 640x480 console.
>
> I don't know jack about graphics, honestly. But IIRC the "normal" BIOS
> only supports 640x480x16 (16 colors?) or some such. It couldn't be too
> too hard to adjust to running in fewer colors (although not ideal)
> e.g. under WinXP. And/or you could just resize your .PCX image files,
> etc.
>
> > While running, it
> > frequently reads image files off disk, and for that reason won't fit on
> (or
> > reliably run from) a floppy. I want to share it with friends such that
> all
> > they have to do is insert a CD and boot up.
>
> But how much total storage do you need? More than 1.4 MB? You could
> uncompress it from physical floppy to RAM disk if speed is an issue.
> It's not that floppies are so great, but they've been around forever
> and have fairly good support and are fairly simple to use, modify,
> emulate, etc.
>
> > Having said that, I've tried DosBox, just for my own purposes. My
> > program runs very slowly in it, no matter what settings I use;
>
> notepad dosbox-0.74.conf
> (change memsize=16 to memsize=32 if desired)
> (change core=auto to core=dynamic)
> (try again)
> (revert changes or use a separate .conf for certain projects)
>
> I'll admit it can be fairly slow, but it's mostly for popular games.
> In fact, it's "only" for games, as the devs often admit. But Doom and
> Quake (mostly) run perfectly fine under it, etc. etc.
>
> Since your game is an actual game, you could always post on the DOSBox
> forum (Vogons / ZetaFleet or whatever) and bug the devs to fix it for
> you. Assuming you're willing to share with them also.
>
> I know you don't like emulators (who does?), but when they work, they
> work well. And DOSBox is small and easy to use (and GPL).
>
> > and
> > for some reason the graphics palette does not get reset properly.
> > I've downloaded VM too, but haven't tried that yet, and for
> > reasons already mentioned I probably won't.
>
> Well, the point is that DOSBox is a natural solution for DOS gaming.
> Of course, it's not a "real" DOS, per se, but it works pretty well.
> However, if you're unwilling to hack at it some more in cooperation
> with DOSBox devs, then you'll have to find another way.
>
> It's not that booting a CD is bad, but sometimes people like not
> having to reboot (and lose network access, background processes, etc.)
> just to play a game.
>
> > The DFSee CD image that someone else recommended looks like
> > something I can modify for my purposes. I've already booted off
> > of that and confirmed that the game runs well...here at home,
> > anyway. And it seems to detect and do i/o on my FAT32 partition
> > just fine. NTFS? I'll worry about that later.
>
> The problem with NTFS is moreso in the overhead, both memory and
> storage, not to mention its inherent security that is underdocumented
> on purpose (and of course several internal revisions). XP is the last
> Windows to boot natively off of a FAT file system. Newer ones only
> boot off of NTFS, but at least those newer ones have built-in
> capabilities to resize the main NTFS partition, if desired (which XP
> lacks, sadly, hence the need for GPar

Re: [Freedos-user] [Spam] Possible problem with Turkish keyboard layouts

[thraex]

On 27/11/12 19:47, Henrique Peron wrote:
> Em 27/11/2012 13:16, thraex escreveu:
> Merhaba Thraex,

Merhaba Henrique :)

> I was impulsive on replying and didn't notice the links you sent; sorry.
> 
> I have read the error message on the "TR" layout.

Er, which one? When I choose option 19 during the install process, the
keyboard layout is an English QWERTY, when I choose 59, although what
seemed like error messages to me get displayed, the keyboard layout is
correct (Turkish QWERTY) without selecting a codepage.

> You've tried to use the turkish QWERTY layout with codepage 437. It 
> seems you forgot to prepare and select one of the codepages available 
> for that layout, of which two being particularly suitable both for the 
> turkish and kurdish languages: 857 and 853.

Thanks for explaining, but how do I select these codepages? Also, please
note that the case I reported happens right after a normal installation
of FreeDOS, therefore I was wondering whether there's something that
needs to be fixed or adjusted so that if the user chooses these layouts,
things will work without additional configuration (or an information
indicating that some additional configuration is needed will be displayed).

If it's possible for you, IMHO the best mean to examine the "bug" is to
install FreeDOS on your side with say VirtualBox and choose keyboard
option 19, then do the same with option 59 and see if the installation
process is OK for you. If not, the good news would be that things can be
improved :)

Çok teşekkürler.

-- 



--
Keep yourself connected to Go Parallel: 
DESIGN Expert tips on starting your parallel project right.
http://goparallel.sourceforge.net
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bruce3

[bruce.bowman tds.net]

Right now I have something like this going on.

A: is the floppy bootup image.
B: could be a floppy so I don't want that to be probed
Y: is the drive letter assigned to the CD that I booted from.
Z: is a ramdrive.

for %%d in (c d e f g h i j k l m n o p q r s t u v w x) do (
  if exist %%d:\mygame\ (
 cls
 echo.
 echo.
 echo.
 echo A previous installation of MYGAME was found on drive %%d:
 choice /B /N /C:YN /T:Y,10 Should I run the game from this location
[recommended]
 if not errorlevel 2 (
   swsubst %progdisk% %%d:\mygame\
   goto finish
 )
  )
)

REM either didn't find an installation, or didn't want to use it
set progdisk = z:
copy Y:\mygame\*.*  %progdisk% > nul

:finish
%progdisk%
rungame

FreeDOS doesn't seem to like the compound IF very much. Thoughts
appreciated.

Bruce


On Tue, Nov 27, 2012 at 1:49 PM, Bernd Blaauw  wrote:

> Op 27-11-2012 6:45, bruce.bowman tds.net schreef:
>
> > In fact I am essentially done with my project but still want something I
> > can throw in a batch file to probe for writeable drive letters so I can
> > give the user an opportunity to save a game and resume later (like they
> > used to).
>
> DOS kernels only assign driveletters to FAT filesystems. For (emulated?)
> floppy drives A: and B: get assigned, thus C: till Z: get assigned to
> everything else.
>
> A FAT filesystem contains the NUL blockdevice, making it easy to test:
>
> @echo off
> IF EXIST C:\NUL echo Driveletter C: points to a FAT filesystem.
>
> Testing if you can store files on the drive is a different issue
> altogether, as it involves:
> * checking if the drive isn't full yet
> * checking if the drive isn't write-protected (read-only)
> * checking if there's enough free diskspace
>
> Bernd
>
>
> --
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>



-- 
 Sent from my meager, humble desktop computer.
--
Keep yourself connected to Go Parallel: 
DESIGN Expert tips on starting your parallel project right.
http://goparallel.sourceforge.net___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bruce3

[Bernd Blaauw]

Op 27-11-2012 6:45, bruce.bowman tds.net schreef:

> In fact I am essentially done with my project but still want something I
> can throw in a batch file to probe for writeable drive letters so I can
> give the user an opportunity to save a game and resume later (like they
> used to).

DOS kernels only assign driveletters to FAT filesystems. For (emulated?) 
floppy drives A: and B: get assigned, thus C: till Z: get assigned to 
everything else.

A FAT filesystem contains the NUL blockdevice, making it easy to test:

@echo off
IF EXIST C:\NUL echo Driveletter C: points to a FAT filesystem.

Testing if you can store files on the drive is a different issue 
altogether, as it involves:
* checking if the drive isn't full yet
* checking if the drive isn't write-protected (read-only)
* checking if there's enough free diskspace

Bernd

--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] [Spam] Possible problem with Turkish keyboard layouts

[Henrique Peron]

Em 27/11/2012 13:16, thraex escreveu:
> Hi there,
>
> I recently gave FreeDOS a try on VirtualBox (which was running on Ubuntu
> 12.04). The installation went almost entirely fine, but I think I
> spotted a problem when the user chooses Turkish layouts for his or her
> keyboard.
>
> In fact two Turkish layouts are offered. One is the number 19 and is
> simply mentioned as Turkish, the other is the number 59 and is mentioned
> as Turkish (Qwerty). Here are some links to relevant parts of the
> installation process, firstly for the "number 19" and then for 59. Sorry
> for posting screenshots for plain text screens, but I couldn't find an
> easy way to copy&paste their content.
> 
> 
> 
> 
>
> You can see the error messages, on the first screenshot of each series
> you have "could not find country info for country ID 1" and on the
> second image you have different errors. If the user chooses 19, the
> result seems to be a good old *English* QWERTY keyboard. If the choice
> is 59, things seem to work fine despite the error messages (the layout
> is OK).
>
> I can't say much more than this but since I use the Turkish QWERTY
> layout, I wanted to bring this to your attention. If I can do something
> more, feel free to say it.
>
> PS: One more thing: if the first layout (19) was supposed to be the
> Turkish F, I think it should be swapped with the QWERTY (59). In Turkey,
> roughly around 90% of keyboards are the Turkish QWERTY variant, and the
> remaining 10% is the Turkish F variant which is supposed to fit the
> language better. Most operating systems consider "Turkish" with no
> additional precision as the Turkish QWERTY, the F keyboard is often an
> option, not the default. Therefore, the first choice should probably be
> the Turkish QWERTY.
>
>
Merhaba Thraex,

I was impulsive on replying and didn't notice the links you sent; sorry.

I have read the error message on the "TR" layout.

You've tried to use the turkish QWERTY layout with codepage 437. It 
seems you forgot to prepare and select one of the codepages available 
for that layout, of which two being particularly suitable both for the 
turkish and kurdish languages: 857 and 853.

Henrique


--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] [Spam] Possible problem with Turkish keyboard layouts

[Henrique Peron]

Em 27/11/2012 13:16, thraex escreveu:
> Hi there,
>
> I recently gave FreeDOS a try on VirtualBox (which was running on Ubuntu
> 12.04). The installation went almost entirely fine, but I think I
> spotted a problem when the user chooses Turkish layouts for his or her
> keyboard.
>
> In fact two Turkish layouts are offered. One is the number 19 and is
> simply mentioned as Turkish, the other is the number 59 and is mentioned
> as Turkish (Qwerty). Here are some links to relevant parts of the
> installation process, firstly for the "number 19" and then for 59. Sorry
> for posting screenshots for plain text screens, but I couldn't find an
> easy way to copy&paste their content.
> 
> 
> 
> 
>
> You can see the error messages, on the first screenshot of each series
> you have "could not find country info for country ID 1" and on the
> second image you have different errors. If the user chooses 19, the
> result seems to be a good old *English* QWERTY keyboard. If the choice
> is 59, things seem to work fine despite the error messages (the layout
> is OK).
>
> I can't say much more than this but since I use the Turkish QWERTY
> layout, I wanted to bring this to your attention. If I can do something
> more, feel free to say it.
>
> PS: One more thing: if the first layout (19) was supposed to be the
> Turkish F, I think it should be swapped with the QWERTY (59). In Turkey,
> roughly around 90% of keyboards are the Turkish QWERTY variant, and the
> remaining 10% is the Turkish F variant which is supposed to fit the
> language better. Most operating systems consider "Turkish" with no
> additional precision as the Turkish QWERTY, the F keyboard is often an
> option, not the default. Therefore, the first choice should probably be
> the Turkish QWERTY.
>
>
Merhaba Thraex,

please try this, on the command prompt: "KEYB TR".
That should load the turkish QWERTY layout; if you're familiar with 
editting AUTOEXEC.BAT, I suggest you include "KEYB TR" (without quotes) 
there.

You mentioned error messages; could you please tell me what are they?

Thanks,
Henrique

--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Possible problem with Turkish keyboard layouts

[thraex]

Hi there,

I recently gave FreeDOS a try on VirtualBox (which was running on Ubuntu
12.04). The installation went almost entirely fine, but I think I
spotted a problem when the user chooses Turkish layouts for his or her
keyboard.

In fact two Turkish layouts are offered. One is the number 19 and is
simply mentioned as Turkish, the other is the number 59 and is mentioned
as Turkish (Qwerty). Here are some links to relevant parts of the
installation process, firstly for the "number 19" and then for 59. Sorry
for posting screenshots for plain text screens, but I couldn't find an
easy way to copy&paste their content.





You can see the error messages, on the first screenshot of each series
you have "could not find country info for country ID 1" and on the
second image you have different errors. If the user chooses 19, the
result seems to be a good old *English* QWERTY keyboard. If the choice
is 59, things seem to work fine despite the error messages (the layout
is OK).

I can't say much more than this but since I use the Turkish QWERTY
layout, I wanted to bring this to your attention. If I can do something
more, feel free to say it.

PS: One more thing: if the first layout (19) was supposed to be the
Turkish F, I think it should be swapped with the QWERTY (59). In Turkey,
roughly around 90% of keyboards are the Turkish QWERTY variant, and the
remaining 10% is the Turkish F variant which is supposed to fit the
language better. Most operating systems consider "Turkish" with no
additional precision as the Turkish QWERTY, the F keyboard is often an
option, not the default. Therefore, the first choice should probably be
the Turkish QWERTY.


-- 
Goebbels was in favor of free speech for views he liked. So was Stalin.
If you’re in favor of free speech, then you’re in favor of freedom of
speech precisely for views you despise. Otherwise, you’re not in favor
of free speech - Noam Chomsky.

--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bruce

[Rugxulo]

Hi,

On Tue, Nov 27, 2012 at 1:49 AM, dmccunney  wrote:
> On Tue, Nov 27, 2012 at 2:32 AM, Rugxulo  wrote:
>>
>> http://www.cgsecurity.org/wiki/TestDisk
>
> TestDisk is wonderful, but it's a partition recovery program.  It uses
> low-level disk reads to find partition data, and doesn't care what the
> file system on the drive is.
>
> There's a companion program called Photorec that can be used to
> recover image files from damaged disks.

Okay, but in fairness, both .EXEs are inside the same .ZIP!;-)

--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user