[Freedos-user] Use of MSDOS on XP Computer

2009-08-27 Thread MELVIN FRIEDLANDER
I use Quick Basic for many of my scientific programs. Quick Basic is on a MSDOS 
system which I have on a computer using Windows 98. Would it be possible to 
transfer my DOS program to a computer using Windows XP?

Melvin M. Friedlander
mail...@verizon.net
(951) 301-4152
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] Use of MSDOS on XP Computer

2009-08-27 Thread Mateusz Viste
On Thursday 27 August 2009 20:20 (CEST), MELVIN FRIEDLANDER wrote:
 I use Quick Basic for many of my scientific programs. Quick Basic is on a 
 MSDOS system which I have on a computer using Windows 98. Would it be 
 possible to transfer my DOS program to a computer using Windows XP?

Hi,

As far as I know, QuickBasic run just fine on Windows XP...
However, you could also check out the FreeBASIC compiler. FreeBASIC is very 
similar to QuickBasic (but *much* more powerful), and allows to compile 
programs for DOS, Windows (XP, Vista, etc) and Linux.

Best regards,
Mateusz Viste
-- 
You'll find my public OpenPGP key at http://www.viste-family.net/mateusz/pub_key


signature.asc
Description: This is a digitally signed message part.
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


[Freedos-user] Driver development

2009-08-27 Thread bray

Hello;

I have an Atheros pci-x 802.11 wireless card in my Asus EEEpc laptop and
there is no driver available for the card! Does anyone have some links and
resources pertaining to driver/packet driver development for DOS? I'm not
looking for a quick fix, but a project!

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] Use of MSDOS on XP Computer

2009-08-27 Thread Alexandru Fira
  Yes, indeed, Qbasic runs nicely on Windows XP. It can also be run very well 
in Dosbox or Dosemu under Linux.

Alex

Phone number: 004-0364412643
Mobile phone number: 004-0770607699
Messenger ID: firaalexandru
Skype ID: alexfiracluj




  

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] Driver development

2009-08-27 Thread Eric Auer

Hi Bray,

 I have an Atheros pci-x 802.11 wireless card in my Asus EEEpc laptop and
 there is no driver available for the card! Does anyone have some links and
 resources pertaining to driver/packet driver development for DOS? I'm not
 looking for a quick fix, but a project!

Expect a big project here... You can see many examples of open
source DOS network card packet drivers on the CRYNWR homepage:

www.crynwr.com/drivers/

Atheros.com says they actively support the Linux driver:

http://madwifi-project.org/
http://sourceforge.net/projects/madwifi/
http://madwifi-project.org/wiki/Chipsets

There are actually THREE variants of the driver:

http://wireless.kernel.org/en/users/Drivers/ath9k
http://madwifi-project.org/wiki/About/ath5k
...and a third based on a non-portable binary blob

The drivers will depend on Linux infrastructure so you will probably
have to add many other bits and pieces. You can probably get an easier
start by only porting their info tool first:

http://madwifi-project.org/browser/ath_info/trunk

A good compiler for porting Linux stuff to DOS is DJGPP:

www.delorie.com/djgpp/

Of course with Wireless things are usually much worse
than with normal network cards, because you will have
to have some software which takes care of setting up
wireless connection details. In many networks, you will
also need something which does WEP, WPA or WPA2 security.

But of course I understand that you do not want to carry
a cable which is heavier than your tiny netbook laptop :-)

Eric



PS: Maybe you can also check whether the EEE PC supports
int 15.87 and if not whether some HIMEMX / JEMM386 combo
or similar could be used to make FDAPM ACPIDUMP work ;-)



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


[Freedos-user] XST Basic

2009-08-27 Thread Eric Auer

Hi everybody, Angelo Rosina writes about a BASIC for DOS,
forwarding some info from him :-) Should we add XST to our
freedos.org software collection and/or the distro? :-)

Eric


 
Since XST is compiled with DJGPP, it's hardware requirements are almost
the same of FreeBasic
 
FreeBasic (FB) and XST Basic are different products, with different targets.
 
FB is a true compiler; XST is an interpreter + a C emitter (it cannot
directly compile, but can convert the source into a C code that can be
compiled)
 
FB has a QB compatible mode; XST is more based on AMOS and STOS Basic
(for Amiga and Atari ST)
 
FB is a generic, all-purposes language; XST is focused on multimedia and
game development (even a very good Doom clone is available in demos)
 
FB can be extended with external libraries; XST already has graphic,
sprites, 3D and sound support.
 
FB can only compile, you have to use an external editor (i.e. RHIDE);
XST has its own IDE, where you can write and instantly run your program.
 
If you have any more questions, feel free to ask.

 The XST Basic, written by Rodney Mc Connell, is now open source.
 Source code is at: http://sourceforge.net/projects/xstbasic/
 Original site was at: http://www.geocities.com/snakessoft/vault.html


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] Driver development

2009-08-27 Thread Braden C. Roberson-Mailloux
http://standards.ieee.org/getieee802/802.11.html

[QUOTE]
Expect a big project here...
[/QUOTE]

With over 1200 pages of IEEE standards information, I'm not suprised!

[QUOTE]
PS: Maybe you can also check whether the EEE PC supports
 int 15.87 and if not whether some HIMEMX / JEMM386 combo
 or similar could be used to make FDAPM ACPIDUMP work ;-)
[/QUOTE]

Sure, do you have a template written in C for testing interrupts?
That or ASM, I can read both of them!

[QUOTE]
You can see many examples of open
 source DOS network card packet drivers on the CRYNWR homepage
[/QUOTE]

http://www.crynwr.com/packet_driver.html

This seems to be a specification for interrogating any of those drivers.
It may help!

I have a dedicated FDOS box at home with a 3COM 3C905CX, I think...
I'll check when I get home. Perhaps some experiments with this card
will also help...? Do you have any recommendations?

I'm more than willing to undertake what may seem a daunting project. I
need something to do which keeps me occupied for those cold Fall
and Winter nights. Plus, I just picked up my amateur radio license, and
this seems like a good, rewarding and education project as far as that
realm of technology is concerned.

73!
Bray.

- Original Message - 
From: Eric Auer e.a...@jpberlin.de
To: b...@vom.com; freedos-user@lists.sourceforge.net
Sent: Thursday, August 27, 2009 2:16 PM
Subject: Re: [Freedos-user] Driver development



 Hi Bray,

 I have an Atheros pci-x 802.11 wireless card in my Asus EEEpc laptop and
 there is no driver available for the card! Does anyone have some links 
 and
 resources pertaining to driver/packet driver development for DOS? I'm not
 looking for a quick fix, but a project!

 Expect a big project here... You can see many examples of open
 source DOS network card packet drivers on the CRYNWR homepage:

 www.crynwr.com/drivers/

 Atheros.com says they actively support the Linux driver:

 http://madwifi-project.org/
 http://sourceforge.net/projects/madwifi/
 http://madwifi-project.org/wiki/Chipsets

 There are actually THREE variants of the driver:

 http://wireless.kernel.org/en/users/Drivers/ath9k
 http://madwifi-project.org/wiki/About/ath5k
 ...and a third based on a non-portable binary blob

 The drivers will depend on Linux infrastructure so you will probably
 have to add many other bits and pieces. You can probably get an easier
 start by only porting their info tool first:

 http://madwifi-project.org/browser/ath_info/trunk

 A good compiler for porting Linux stuff to DOS is DJGPP:

 www.delorie.com/djgpp/

 Of course with Wireless things are usually much worse
 than with normal network cards, because you will have
 to have some software which takes care of setting up
 wireless connection details. In many networks, you will
 also need something which does WEP, WPA or WPA2 security.

 But of course I understand that you do not want to carry
 a cable which is heavier than your tiny netbook laptop :-)

 Eric



 PS: Maybe you can also check whether the EEE PC supports
 int 15.87 and if not whether some HIMEMX / JEMM386 combo
 or similar could be used to make FDAPM ACPIDUMP work ;-)


 


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] Freedos-user Digest, Vol 302, Issue 1

2009-08-27 Thread MELVIN FRIEDLANDER
Hello Mateusz and Alex,

Thank you both for your very quick response on the question of using QBasic on 
my XP. However, I am somewhat computer ignorant and need to know the specifics 
on how this can be done. What do I download or buy or get through my email or 
phone?

Mel

Melvin M. Friedlander
mail...@verizon.net
(951) 301-4152

- Original Message - 
From: freedos-user-requ...@lists.sourceforge.net 
To: freedos-user@lists.sourceforge.net 
Sent: Thursday, August 27, 2009 2:32 PM
Subject: Freedos-user Digest, Vol 302, Issue 1


Send Freedos-user mailing list submissions to
freedos-user@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/freedos-user
or, via email, send a message with subject or body 'help' to
freedos-user-requ...@lists.sourceforge.net

You can reach the person managing the list at
freedos-user-ow...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than Re: Contents of Freedos-user digest...


Today's Topics:

   1. Re: [Fwd:  Full Screen Sized Screen-Dumps] (Robert J. Thompson)
   2.  Driver Problems (ron3090)
   3. Re: Driver Problems (pcdos2k)
   4. Use of MSDOS on XP Computer (MELVIN FRIEDLANDER)
   5. Re: Use of MSDOS on XP Computer (Mateusz Viste)
   6. Driver development (b...@vom.com)
   7. Re: Use of MSDOS on XP Computer (Alexandru Fira)
   8. Re: Driver development (Eric Auer)
   9. XST Basic (Eric Auer)


--

Message: 1
Date: Wed, 26 Aug 2009 14:18:54 -0600
From: Robert J. Thompson the_drb...@earthlink.net
Subject: Re: [Freedos-user] [Fwd:  Full Screen Sized Screen-Dumps]
To: freedos-user@lists.sourceforge.net
Message-ID: 4a9598ae.1020...@earthlink.net
Content-Type: text/plain; charset=us-ascii; format=flowed

Eric Auer wrote:
 Hi Robert,

 to find my GRAPHICS for DOS, check our list:

 http://www.freedos.org/freedos/software/ - base - graphics

 Maybe I should have mentioned the names graphpin, graph-hp
 and graph-ps, as graphics is just a wrapper for the tree :-)

   

Eric: Found the '.dosemurc' file as '/etc/.dosemu/dosemu.conf'. Am 
working on that now. Thanks - Bob T.



--

Message: 2
Date: Wed, 26 Aug 2009 16:38:14 -0700 (PDT)
From: ron3090 onua...@gmail.com
Subject: [Freedos-user]  Driver Problems
To: freedos-user@lists.sourceforge.net
Message-ID: 25163496.p...@talk.nabble.com
Content-Type: text/plain; charset=us-ascii


I have an old Dell Latitude CPi A Laptop that has Puppy and FreeDOS installed
on it. Puppy works fine, sound and full video. But FreeDOS has problems.
First, there is no sound, which I've heard is common. According to the Dell
website, the sound controller is a NeoMagic 2200 AC97 Codec which is of
the type Sound Blaster Emulation. Yet the sound doesn't work. I don't know
the first thing about FreeDOS, other than how to navigate to my games. How
do I get sound working?
Second, but not as important, is that the video does not fill up the whole
screen. Once again, I'm assuming this has something to do with the drivers.
It is a NeoMagic 2200.
Lastly, I'd like to be able to use my USB drive with FreeDOS. I installed
DosUSB, and the drive lights up after I run the program. How do I access
the drive?
Hoping for an answer,
ron3090
-- 
View this message in context: 
http://www.nabble.com/Driver-Problems-tp25163496p25163496.html
Sent from the FreeDOS - User mailing list archive at Nabble.com.




--

Message: 3
Date: Thu, 27 Aug 2009 05:49:27 -0700 (PDT)
From: pcdos2k pcdo...@yahoo.com
Subject: Re: [Freedos-user] Driver Problems
To: freedos-user@lists.sourceforge.net
Message-ID: 741970.78470...@web39601.mail.mud.yahoo.com
Content-Type: text/plain; charset=us-ascii

--- On Wed, 8/26/09, ron3090 onua...@gmail.com wrote:

 According to the Dell
 website, the sound controller is a NeoMagic 2200 AC97
 Codec which is of
 the type Sound Blaster Emulation. Yet the sound doesn't
 work. I don't know
 the first thing about FreeDOS, other than how to navigate
 to my games. How
 do I get sound working?


try this generic SB audio enabler:
http://www.multimediaware.com/qv/sbdetect.zip

or this ac97 dos driver by via (viafmstr):
http://schneegans.de/computer/dos-soundtreiber/




  



--

Message: 4
Date: Thu, 27 Aug 2009 11:20:58 -0700
From: MELVIN FRIEDLANDER mail...@verizon.net
Subject: [Freedos-user] Use of MSDOS on XP Computer
To: freedos-user@lists.sourceforge.net
Message-ID: 084e638743c74d33b75557b31222f...@d11wdb71
Content-Type: text/plain; charset=windows-1252

I use Quick Basic for many of my scientific programs. Quick Basic is on a MSDOS 
system which I have on a computer using Windows 98. Would it be possible to 
transfer my DOS program to a computer using Windows XP?

Melvin M. Friedlander
mail...@verizon.net
(951) 301-4152
-- next part --
An HTML attachment was 

Re: [Freedos-user] Freedos-user Digest, Vol 302, Issue 1

2009-08-27 Thread Alexandru Fira
  Just copy the qbasic.exe interpreter anywhere in your Windows XP computer, 
for example on the desktop. For running it just double click on qbasic.exe and 
off it goes. Windows XP has NTVDM (New Technology Virtual DOS Machine) that can 
run a lot of DOS programs, including Qbasic.
  There is no need to download or buy anything. It is easy and simple.
  When you program and you save some .bas files these are saved in the folder 
where Qbasic is. For example, if Qbasic sits on the desktop, the .bas files 
will be saved on the desktop. If you copy it to another folder, it will save 
the .bas files into that folder.
  It is good to set your OS so that when you double click on a .bas file it is 
opened with Qbasic, in case you have some folders with qbasic programs 
scattered around, so as to be easier to open them. But I used to have several 
copies of Qbasic in my PC. 


 Alex

Phone number: 004-0364412643
Mobile phone number: 004-0770607699
Messenger ID: firaalexandru
Skype ID: alexfiracluj




  

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


[Freedos-user] Disk checking and defragmentation

2009-08-27 Thread Marcos Favero Florence de Barros
Hi Eric, Christian and Geraldo,

Thanks for your interest.

Here is what I have observed about CHKDSK, DOSFSCK and DEFRAG.
As I'm writing from memory, this is not very accurate. In the
future I'll take notes in order to report more reliably.

After several crashes in my early days with FreeDOS two years
ago, I have learned to prevent most of them.

One exception is DOSLFN, which I occasionally used in
combination with the file managers NDN or File Wizard to
decompress files with InfoZip.

Whenever DOSLFN was used, CHKDSK would find dozens or even
hundreds of damaged files. In addition, strange folders or files
appeared which could not be deleted. To get rid of them I had to
copy the usable files to a second hard disk and reformat the
first. This happened three or four times, in two different
computers.

Don't worry about DOSLFN -- I hardly ever need it. The only
reason I mentioned it is because it was involved in disk damage
which CHKDSK and DOSFSCK tried to repair.

To do disk ckecking I now use DOSFSCK, which in my experience is 
safer than CHKDSK. My impression was that, in attempting to 
correct damage (such as that caused by DOSLFN), CHKDSK actually 
made matters worse. DOSFSCK seemed to do the same, but to a 
lesser extent. In those cases, both programs would report on the 
screen huge amounts (hundreds or perhaps thousands) of file 
names which were supposedly being fixed. If there were indeed so 
many damaged files before checking the disk, I would probably 
have noticed them by just using the computer.

I still experience file damage or loss occasionally, but have no
idea what is causing it. One instance happened a few months ago
when I ran DOSFSCK and then DEFRAG. I noticed that DOSFSCK took
an unusually long time -- about 15 min instead of the usual 2
min -- to scan the disk. I do not remember whether DEFRAG ran or
crashed, but the end result was a messed up hard drive. Some
files were lost, others were truncated to a multiple of 16384
bytes, and still others had bytes appended to them making their
size also a multiple of 16384. Hundreds of files were lost or
damaged, and had to be recovered from backups.

I downloaded DEFRAG version 1.32 last June but it does not run
at all in my computer. It either issues a Get fixed file
failed message or simply freezes, depending on the hard drive
to be defragmented. This happens both with the full-screen
interface and the command line version. The previous version of
DEFRAG worked only in the command line version; the full-screen
interface would give an error message undefined error or
something similar.

One possibility, of course, is that I'm doing something wrong.
I'm quite good at following instructions, but in some cases the
manual seems to be too brief, perhaps because it assumes that
the reader is familiar with, say, similar programs in Linux.

For instance, I have not been able to understand how to use the
DOSFSCK with the -V perform a verification pass option. The
logic behind it is clear: let's have a look at things before
changing them. But when the program runs, it just writes:

  dosfsck 2.11.DOS3, 8 Aug 2007, FAT32, LFN
  Starting check/repair pass.
  Starting verification pass.
  c:: 33412 files, 42820/65505 clusters

That confused me. Does it mean the disk is OK? Is there anything
else to be done?

To first-time users it may not be obvious what is supposed to
happen when a program runs. Most of the instructions in FreeDOS
are good, but some of them could be a bit more explicit.
Examples of frequently used command lines are always welcome too.

In a way, instructions are a form of software too, which runs in
our minds, and perhaps they also need testing and debugging :-)

Included below is some information about the hardware of my main
computer. And here is a summary of the above comments.

DEFRAG  Current version does not work in my computers;
previous version worked only in command line
option.

CHKDSK  Occasionally seems to make matters worse.

DOSFSCK Apparently safer than CHKDSK, but not
completely.

Let me repeat that all the above are just 'remembrances of 
things past'. I hope to contribute more accurately in the future.

Regards and thanks,

Marcos Florence
Sao Paulo, Brazil

--

   Navrátil Software System Information
  Version 0.60.32
Report File
Thursday, 2009-08-27 23:40

===General Information
 Computer   PC-AT or compatible, ISA + PCI
 Processor  Intel Pentium, 100 MHz, Real mode, 2/5/28/18
 Co-Processor   Internal, 100 MHz, 3/3/100/28
 BIOS   AMI, American Megatrends, Inc., PnP, 07/15/95
 Video  Trident SVGA 4 MB, VESA VBE 2.0, Secondary: None
 Memory 32 MB, 639 KB, 31744 KB, no XMS, no EMS
 Drives