Re: [Freedos-user] which mpxplay?

[Björn Morell]

Hi, In the docs ,i sndcard.txt you will find what to do with different 
sound cards, either with switches or in the ini file, just download 
1.66d or g (g needs dos4gw, d has dos32a).


Den 2022-02-09 kl. 03:36, skrev Karen Lewellen:

Hi bear,
Thanks for this.  sorry needed to check.
it seems I have mpxplay 147 156 157   and 159.
I have not tried 166 but will seek that out.
I am not running freedos, but a ms dos 7.1  package on a Pentium 3 
machine.

 the best news for me here is that I can perhaps manipulate the ini file?
This specific machine has the sound card on a different IRQ so I will 
need to adjust that if possible.

Thanks for providing your additions for me,
Karen



On Mon, 7 Feb 2022, Björn Morell wrote:

 I run ver. 166d on my freedos 1.3 RC5 installation on an IBM 486 100 
mhz It may take some tweaking in the ini file I can run it with 
graphics as well (and scroll, pick and start works with cutemouse /O 
but starting with the -f0 switch "mpxplay -f0 song.mp3" no gui gives 
the best sound on this machine, on what are you running yours ? I 
have a bunch of versions from 1.47 which does not take all switches 
but runs easy, 1.534 is made for 486:s, 1.56d, 1.65d ,1.65g (needs 
dos4gw)  and 1.66. Read the text files and the ini file and you will 
have the info you need.


Bear

Den 2022-02-06 kl. 23:04, skrev Karen Lewellen:

 Hi folks,
 I am asking for specifics, as I believe? Eric noted when the 
program was

 last updated that for simple DOS usage things may be less flexible.
 so, if one is not running graphics, which edition of mpxplay is best?
 I have several older ones, if upgrading is unwise.
 still, because this DOS machine uses a different IRQ, I will need 
to tell

 the program where to find my soundcard.
 Alternatively, has  anyone here used the 2012 DOS compile of mplayer?
 I got the package, but there is no DOS focused documentation.
 Thanks,
 Karen




 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user





___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] which mpxplay?

[Karen Lewellen]

Hi bear,
Thanks for this.  sorry needed to check.
it seems I have mpxplay 147 156 157   and 159.
I have not tried 166 but will seek that out.
I am not running freedos, but a ms dos 7.1  package on a Pentium 3 machine.
 the best news for me here is that I can perhaps manipulate the ini file?
This specific machine has the sound card on a different IRQ so I will 
need to adjust that if possible.

Thanks for providing your additions for me,
Karen



On Mon, 7 Feb 2022, Björn Morell wrote:

 I run ver. 166d on my freedos 1.3 RC5 installation on an IBM 486 100 mhz It 
may take some tweaking in the ini file I can run it with graphics as well 
(and scroll, pick and start works with cutemouse /O but starting with the -f0 
switch "mpxplay -f0 song.mp3" no gui gives the best sound on this machine, on 
what are you running yours ? I have a bunch of versions from 1.47 which does 
not take all switches but runs easy, 1.534 is made for 486:s, 1.56d, 1.65d 
,1.65g (needs dos4gw)  and 1.66. Read the text files and the ini file and 
you will have the info you need.


Bear

Den 2022-02-06 kl. 23:04, skrev Karen Lewellen:

 Hi folks,
 I am asking for specifics, as I believe? Eric noted when the program was
 last updated that for simple DOS usage things may be less flexible.
 so, if one is not running graphics, which edition of mpxplay is best?
 I have several older ones, if upgrading is unwise.
 still, because this DOS machine uses a different IRQ, I will need to tell
 the program where to find my soundcard.
 Alternatively, has  anyone here used the 2012 DOS compile of mplayer?
 I got the package, but there is no DOS focused documentation.
 Thanks,
 Karen




 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] which mpxplay?

[Björn Morell]

 I run ver. 166d on my freedos 1.3 RC5 installation on an IBM 486 100 
mhz It may take some tweaking in the ini file I can run it with graphics 
as well (and scroll, pick and start works with cutemouse /O but starting 
with the -f0 switch "mpxplay -f0 song.mp3" no gui gives the best sound 
on this machine, on what are you running yours ? I have a bunch of 
versions from 1.47 which does not take all switches but runs easy, 1.534 
is made for 486:s, 1.56d, 1.65d ,1.65g (needs dos4gw)  and 1.66. Read 
the text files and the ini file and you will have the info you need.


Bear

Den 2022-02-06 kl. 23:04, skrev Karen Lewellen:

Hi folks,
I am asking for specifics, as I believe? Eric noted when the program 
was last updated that for simple DOS usage things may be less flexible.

so, if one is not running graphics, which edition of mpxplay is best?
I have several older ones, if upgrading is unwise.
still, because this DOS machine uses a different IRQ, I will need to 
tell the program where to find my soundcard.

Alternatively, has  anyone here used the 2012 DOS compile of mplayer?
I got the package, but there is no DOS focused documentation.
Thanks,
Karen




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which paint programs and image viewers for DOS do you prefer?

[Lukas Satin]

I came across source code of Deluxe Paint 1 by Electronic Arts, but it is
not for distribution (just for your personal interest):
https://computerhistory.org/blog/electronic-arts-deluxepaint-early-source-code/

On Sun, Jun 20, 2021 at 11:26 AM Bryan Kilgallin 
wrote:

> Eric:
>
> > I wonder what
> > YOUR impressions are regarding those, because I
> > would suggest to add at least 1 paint and 1 image
> > viewer app to our "full" collection of applications.
>
> A Wacom graphics-tablet is a USB device. Anything would have to support
> that!
> --
> members.iinet.net.au/~kilgallin/
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which paint programs and image viewers for DOS do you prefer?

[Bryan Kilgallin]

Eric:


I wonder what
YOUR impressions are regarding those, because I
would suggest to add at least 1 paint and 1 image
viewer app to our "full" collection of applications.


A Wacom graphics-tablet is a USB device. Anything would have to support 
that!

--
members.iinet.net.au/~kilgallin/


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which paint programs and image viewers for DOS do you prefer?

[Jim Hall]

On Fri, Jun 11, 2021 at 1:59 PM Robert Riebisch  wrote:
>
> Hi Eric,
>[..]
> > I also recommend to include MPXPLAY, the versatile media
> > player with support for modern sound cards, in FreeDOS!
>
> +1
>
> mpxplay.c says:
> ###
> This program is distributed in the hope that it will be useful,
> but WITHOUT ANY WARRANTY; without even the implied warranty of
> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> Please contact with the author (with me) if you want to use
> or modify this source.
> ###
>
> Not free enough?
>


Ouch. "Contact me if you want to use or modify" the source code is not
very "open source."

If you were a hobby developer, you would need to contact the author
and request permission to experiment with the source code. The author
would probably grant permission for a hobby developer - assuming the
author is responding to email (for example, hasn't changed email
addresses, etc). Would the author grant permission if a company (even
a small company) wanted to modify mpxplay to add some neat feature,
with the intention to re-release their patches & updated source code
for others to use?

As written, it's unclear if this allowed others to share or
redistribute the source code. "Ask permission to use" suggests that
redistributing the source code requires permission.

It would be better for mpxplay to use an accepted, recognized "open
source" license like the MIT license or Apache license.


As an aside, we don't list this on the FreeDOS 1.3 "Packages" list,
and it's not included in FreeDOS 1.3 RC4 either:

http://wiki.freedos.org/wiki/index.php/Releases/1.3/Packages#Sound


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which paint programs and image viewers for DOS do you prefer?

[Rafael Angel Campos Vargas]

I generally use pictview for some tasks.

El 11 jun. 2021 12:43 PM, "Eric Auer"  escribió:

>
> Hi everybody,
>
> http://www.bttr-software.de/freesoft/graphics.htm
>
> lists a number of free and/or open source painting
> and image viewer programs for DOS. I wonder what
> YOUR impressions are regarding those, because I
> would suggest to add at least 1 paint and 1 image
> viewer app to our "full" collection of applications.
>
> GrafX2 and OGE are two possible choices for paint
> applications listed on the BTTR page.
>
> PAINT2 is still listed as open source in the LSM:
>
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/
> repositories/1.3/pkg-html/paint2.html
>
> However, as has been mentioned in the WIKI, it has
> a number of closed source OBJ files. The LSM should
> be updated to reflect that.
>
> http://www.bttr-software.de/products/vp386/
>
> VGA Paint 386 is a Deluxe Paint clone and, according
> to https://www.bttr-software.de/products/divt/ causes
> instability on exit (in certain cases?) by not properly
> restoring interrupt vectors.
>
> The list on BTTR only has closed source freeware image
> viewers, but maybe one of the authors would be willing
> to release sources. Which ones should be asked and is
> any of you feeling like doing that?
>
>  # PictView (Jan Patera)
>  # LXPIC (Stefan Peichl)
>  # QPV and QPNG (Oliver Fromme)
>
> I guess PictView and maybe LXpic are most interesting.
>
> I also recommend to include MPXPLAY, the versatile media
> player with support for modern sound cards, in FreeDOS!
>
> Regards, Eric
>
> PS: Nice that DOS versions of TESTDISK and PHOTOREC exist.
>
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which paint programs and image viewers for DOS do you prefer?

[Robert Riebisch]

Hi Eric,

> The list on BTTR only has closed source freeware image
> viewers, but maybe one of the authors would be willing
> to release sources. Which ones should be asked and is
> any of you feeling like doing that?

I will do that, as I already mentioned via PM.

>  # PictView (Jan Patera)
>  # LXPIC (Stefan Peichl)
>  # QPV and QPNG (Oliver Fromme)
> 
> I guess PictView and maybe LXpic are most interesting.

Yes.

> I also recommend to include MPXPLAY, the versatile media
> player with support for modern sound cards, in FreeDOS!

+1

mpxplay.c says:
###
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Please contact with the author (with me) if you want to use
or modify this source.
###

Not free enough?

Cheers,
Robert
-- 
  +++ BTTR Software +++
 Home page: https://www.bttr-software.de/
DOS ain't dead: https://www.bttr-software.de/forum/


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which C compiler for targeting DOS?

[Robert Riebisch]

Hi Mateusz,

>> Can anyone recommend a good C compiler for DOS?
> 
> Turbo C 2.01 (gratis, very good software) and OpenWatcom (open-source, 
> tend to produce heavier binaries than OW, but comes with a more complete 
> libc).

AFAIK Turbo C++ 1.01 has less bugs than Turbo C 2.01, because it's newer
(1991 vs 1989).

Cheers,
Robert
-- 
  +++ BTTR Software +++
 Home page: https://www.bttr-software.de/
DOS ain't dead: https://www.bttr-software.de/forum/


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which C compiler for targeting DOS?

[Jim Hall]

On Sun, Jan 24, 2021 at 1:56 AM Adam Nielsen via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> Hi all,
>
> Can anyone recommend a good C compiler for DOS?
>
> I thought there was only DJGPP and had issues with it when I last tried
> years ago (CWSDPMI), but looking at the FreeDOS build process it seems
> there are quite a number of workable C compilers for DOS now - so much
> so I am not sure which one to use!
> [...]



For what it's worth, I boot FreeDOS using QEMU on FreeDOS. I use OpenWatcom
C or the IA-16 GCC to compile my programs.

It's not as easy as DOSEMU, which actually creates a virtual C: drive from
a folder on your Linux $HOME. Instead, QEMU uses a virtual disk image. To
copy files, I just mount the QEMU image *qemu.img* from Linux, and mount it
someplace like */tmp/freedos*

guestmount -a *qemu.img* -m /dev/sda1 */tmp/freedos*


(the */dev/sda1* in this case tells guestmount to mount the first hard
drive partition)

Jim
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which C compiler for targeting DOS?

[tom ehlert]

>  * I would like to be able to automate the build process as much as
>possible, avoiding complex install requirements as are often the
>case with cross compilers.  This means automatically downloading the
>compiler would be great, so it knocks out something like Borland
>Turbo C which although free, doesn't allow redistribution.  So a
>compiler with a more open licence would be better.

that' s easy, and has been around xxDOS for about 35 years.

distribute the binary PROGRAM.EXE

almost no xxDOS user expects to have to build executables by
themselves. that's a linux concept (which is ok) but for many years
amounted to something like

to build this,
  point the path to xxx
  set environment to yy=xxx\bin
  ...
  ...
  ...
  now
  configure
  build

  might actually build a binary.

in addition, net connectivity of a new DOS machine is much less then
guaranteed. so downloading a compiler (franework) is not guaranteed,
and probably not a good idea about software distribution.

Tom



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which C compiler for targeting DOS?

[TK Chia]

Hello Adam,


  * I would like to be able to produce a native DOS real-mode .exe file
that will run in an emulator like DOSBox and on a real 8086 PC
running DOS (i.e. without protected mode or extended memory).  It
looks like there is an "ia16" port of GCC but this seems to produce
ELF files rather than .exe?


gcc-ia16 (which I had been working on) does indeed produce 16-bit .exe
(and .com) programs which can run on MS-DOS.  It uses ELF mainly as an
intermediate object file format.

In terms of support for DOS programming idioms --- e.g. huge pointers
--- I would say Open Watcom is superior to gcc-ia16.  But you might
still find gcc-ia16 useful, depending on your needs.

Both gcc-ia16 and OW allow for "native" compilation (the toolchains run
on MS-DOS + 32-bit DPMI, and will produce 16-bit DOS programs), and for
cross-compiling from Linux to MS-DOS.  You can find pre-compiled binary
packages for gcc-ia16 and OW, for both these use cases.

Thank you!

--
https://github.com/tkchia :: https://gitlab.com/tkchia


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which C compiler for targeting DOS?

[Mateusz Viste]

On 24/01/2021 08:54, Adam Nielsen via Freedos-user wrote:

Hi all,

Can anyone recommend a good C compiler for DOS?


Turbo C 2.01 (gratis, very good software) and OpenWatcom (open-source, 
tend to produce heavier binaries than OW, but comes with a more complete 
libc).



  * I would like to be able to cross-compile from a Linux machine, but
without having to install a complex cross-compilation environment -
meaning the two options I can think of are running a Linux platform
cross-compiler from within a Docker container, or running a native
DOS compiler from within a virtual environment like QEMU.


Use DOSEMU. You get a little "DOS in a window" that sees your native 
Linux files. No need to copy source files back and forth - write them 
with your usual Linux IDE/notepad, compile and test in the DOSEMU window.



Do they all target protected mode architectures
now or do they still support 8086-compatible real mode?


Both TC and OW produce 8086 code (OW needs the extra -0 argument for that).

Mateusz


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which DOS is "better/best" as the underlying DOS oper. sys. for Win FW 3.1.1. in a mult-boot PC ?

[Dan Scott]

I’m not nearly as knowledgeable as the others who have responds but from what 
I’ve heard and experienced, Windows 3.11 for Workgroups works quite well with 
MS-DOS 6.22. 

Sent from my iPhone

> On Nov 1, 2020, at 7:30 PM, Karen Lewellen  wrote:
> 
> Hi there,
> Interesting question.
> Is there a reason why, if you intend running windows 3.11, that you do not 
> want to use the MS dos closely associated with that windows at the time? 5.0 
> 6.0, or 6.22?
> My guess about ms dos 7.1 is that it  draws from a much later infrastructure.
> I run that edition of DOS, but I do not use windows in any form.
> Just starting the conversation,
> Karen
> 
> 
> 
>> On Sun, 1 Nov 2020, TheBigBlue Guard wrote:
>> 
>> Hello FreeDOSers,
>> 
>> How was your Halloween ? Mine was okay... No tricks yet !
>> 
>> My Q and Problem :
>> 
>> I understand you need a DOS oper sys underlying Win For Workgroups 3.1.1 OS
>> in a mult-boot native environment (no boxes / no emulators).Which DOS
>> OS do you strongly recommend ? and why ?  I have MS-DOS 7.1 install CD and
>> was told NOT to rely on it for Win FW 3.1.1. - is this accurate and correct
>> ?  Can you use FreeDOS as the underlying  OS ?
>> 
>> Big Blue
>> 
> 
> 
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which DOS is "better/best" as the underlying DOS oper. sys. for Win FW 3.1.1. in a mult-boot PC ?

[Karen Lewellen]

Hi there,
Interesting question.
Is there a reason why, if you intend running windows 3.11, that you do not 
want to use the MS dos closely associated with that windows at the time? 
5.0 6.0, or 6.22?
My guess about ms dos 7.1 is that it  draws from a much later 
infrastructure.

I run that edition of DOS, but I do not use windows in any form.
Just starting the conversation,
Karen



On Sun, 1 Nov 2020, TheBigBlue Guard wrote:


Hello FreeDOSers,

How was your Halloween ? Mine was okay... No tricks yet !

My Q and Problem :

I understand you need a DOS oper sys underlying Win For Workgroups 3.1.1 OS
in a mult-boot native environment (no boxes / no emulators).Which DOS
OS do you strongly recommend ? and why ?  I have MS-DOS 7.1 install CD and
was told NOT to rely on it for Win FW 3.1.1. - is this accurate and correct
?  Can you use FreeDOS as the underlying  OS ?

Big Blue




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which DOS is "better/best" as the underlying DOS oper. sys. for Win FW 3.1.1. in a mult-boot PC ?

[Eric Auer]

Hey!

Windows for Workgroups always runs in 386enhanced mode,
unless you run it in what Win95/Win98 called safe mode
and which has limited features.

This mode is VERY picky about interactions with DOS, as
it moves the running DOS into a virtual task and even
is able to clone it when you open multiple DOS windows.

If you can run your apps in classic Windows 3.0 or 3.1,
without 386enh mode, you can do that with FreeDOS. But
if you want to run WfW 3.11, you will have to spend a
LOT of effort to convince DOS and Windows to cooperate.

You could find verbose discussions of the issue online,
but http://wiki.freedos.org/wiki/index.php/Windows is
unfortunately not what you need.

By "a lot of effort" I mean "brave people have been able
to run it for them at some time in the past". This is not
the type of feature which works with a fixed howto, alas.

What you call MS DOS 7.1 is the built-in DOS of Windows
95 or Windows 98. So if you have that, simply use your
Windows 9x without bothering to replace the DOS. But if
you want exactly WfW 3.11, you should use older versions
of MS DOS or PC DOS or similar, those without FAT32 and
without long file names, because WfW does not understand
those and you would have to explicitly tell it to only
access files through DOS and not directly.

You could probably also use DR DOS. In any case, it will
be necessary to make careful driver choices - maybe even
use those shipped with WfW, which in turn leads to the
problem that old MS HIMEM or EMM386 know very little
about modern hardware.

An obvious way to avoid the whole mess completely would
be to run your Windows apps in Wine in Linux. Both Wine
and Linux are free and you can tell Wine to pretend to
be ANY Windows version from Windows 2.0 to Windows 10 :-)

Note that dosemu2, also available for Linux (but planned
to be available for Windows, too) makes it easier to use
Windows and FreeDOS together even in advanced situations,
because dosemu2 already does some of the protected mode
work, which makes Windows relax and be a bit less picky.

I hope this helps :-) And I am curious what your Wfw 3.11
apps and context are at the moment.

Regards, Eric




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which DOS is "better/best" as the underlying DOS oper. sys. for Win FW 3.1.1. in a mult-boot PC ?

[Roderick Klein]

A simple google search gives you an answer.

Search for windows 3.1 freedos in Google.

Presto:

http://wiki.freedos.org/wiki/index.php/Windows

On  2-11-20 00:28, TheBigBlue Guard wrote:

Hello FreeDOSers,

How was your Halloween ? Mine was okay... No tricks yet !

My Q and Problem :

I understand you need a DOS oper sys underlying Win For Workgroups 3.1.1
OS in a mult-boot native environment (no boxes / no emulators).Which
DOS  OS do you strongly recommend ? and why ?  I have MS-DOS 7.1 install
CD and was told NOT to rely on it for Win FW 3.1.1. - is this accurate
and correct ?  Can you use FreeDOS as the underlying  OS ?

Big Blue




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user





___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which

[DIMITRIS ZILASKOS]

From: Dimitris Zilaskos 

--===6423063471355840179==
Content-Type: multipart/alternative; boundary=001a114b0aa0a1dfff0539a74401

--001a114b0aa0a1dfff0539a74401
Content-Type: text/plain; charset=UTF-8

Hi,

I had some more time to spend on this project today. I reinstalled Freedos
on a 2 GB disk-on-module. Again after installation I had to do a sys from
2031 bootdisk and then copy kernel.sys to get a bootable freedos 1.2
system. I can use my CDROM connected to the IDE interface on the Sound
Blaster card. So all is fine here apart from past 2031 bootdisks requiring
the workaround to boot from hard drive.

The issue I am facing now is that the mechanical drives I connected to the
secondary IDE channel of my Vesa Local Bus controller are not detected.
Windows 98 SE bootdisk does not detect them either, The BIOS of my system
only supports 2 hard drives. Last time I had this setup working with Linux,
so I will try to dig some old bootdisk to see if Linux can detect the
secondary IDE hard drives. Is there anything I can try from FreeDOS?

Best regards,

Dimitris

On Wed, Jul 20, 2016 at 11:31 PM, Dimitris Zilaskos 
wrote:

> Hi Eric,
>
> I have tried the /FORCE:CHS and it did not help.
>
> Cheers,
>
> Dimitris
>
> On Wed, Jul 20, 2016 at 7:19 PM, Eric Auer  wrote:
>
>>
>> Hi Dimitris,
>>
>> > I retried sys c: from the 2031 bootdisk and it failed to boot, hanging
>> at
>> > Loading FreeDOS, hard drive working like mad, I rebooted with the same
>> > floppy, did the same thing, and it booted. Tried again with sys 3.6e,
>> > hang again, tried again with sys 2.6, was able to boot again.
>>
>> This is a bit confusing but it sounds like a problem with the way
>> that our FAT32 boot sector uses LBA. So with the new SYS 3.6e, you
>> should be able to boot with /FORCE:CHS (explicitly selecting the
>> CHS FAT32 boot sector: SYS 2.6 does not even have a LBA version).
>>
>> This will probably work with various, including newer (and better)
>> versions of the kernel.sys file: In earlier tests, you mentioned
>> that using SYS CONFIG to require pure LBA or pure CHS mode from a
>> kernel did not affect the ability of the kernel to use the drive.
>>
>> Regards, Eric
>>
>>
>>
>> 
>> --
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>> traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols
>> are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning
>> reports.http://sdm.link/zohodev2dev
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>
>

--001a114b0aa0a1dfff0539a74401
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,I had some more time to spend on this
project today. I reinstalled Freedos on a 2 GB disk-on-module. Again after
installation I had to do a sys from 2031 bootdisk and then copy kernel.sys to
get a bootable freedos 1.2 system. I can use my CDROM connected to the IDE
interface on the Sound Blaster card. So all is fine here apart from past 2031
bootdisks requiring the workaround to boot from hard
drive.The issue I am facing now is that the
mechanical drives I connected to the secondary IDE channel of my Vesa Local Bus
controller are not detected. Windows 98 SE bootdisk does not detect them
either, The BIOS of my system only supports 2 hard drives. Last time I had this
setup working with Linux, so I will try to dig some old bootdisk to see if
Linux can detect the secondary IDE hard drives. Is there anything I can try
from FreeDOS?Best
regards,DimitrisOn Wed, Jul 20, 2016 at 11:31
PM, Dimitris Zilaskos mailto:dimitr...@gmail.com;
target="_blank">dimitr...@gmail.com wrote:Hi Eric,I have tried
the /FORCE:CHS and it did not
help.-aCheers,Dimitris
/div>On Wed, Jul 20, 2016 at 7:19 PM, Eric Auer mailto:e.a...@jpberlin.de;
target="_blank">e.a...@jpberlin.de wrote:
Hi Dimitris,

 I retried sys c: from the 2031 bootdisk and it failed to boot, hanging
at
 Loading FreeDOS, hard drive working like mad, I rebooted with the
same
 floppy, did the same thing, and it booted. Tried again with sys 3.6e,
 hang again, tried again with sys 2.6, was able to boot again.

This is a bit confusing but it sounds like a problem with the way
that our FAT32 boot sector uses LBA. So with the new SYS 3.6e, you
should be able to boot with /FORCE:CHS (explicitly selecting the
CHS FAT32 boot sector: SYS 2.6 does not even have a LBA version).

This will probably work with various, including newer (and better)
versions of the kernel.sys file: In earlier tests, you mentioned
that using SYS CONFIG to require pure LBA or pure CHS mode from a
kernel did not affect the ability of the kernel 

Re: [Freedos-user] Which

[TJ EDMISTER]

From: "TJ Edmister" 

On Tue, 09 Aug 2016 13:57:35 -0400, Dimitris Zilaskos
 wrote:

> The issue I am facing now is that the mechanical drives I connected to
> the
> secondary IDE channel of my Vesa Local Bus controller are not detected.
> Windows 98 SE bootdisk does not detect them either, The BIOS of my system
> only supports 2 hard drives.

IIRC, if your motherboard BIOS only supports two drives, you could use a
controller card with its own onboard ROM for additional drives to be
recognized under DOS (or Win9x). Depending on what chipset the card uses,
there might also be a driver which can enable the second channel.

Not sure if the various DMA DOS drivers would detect and add drives on the
second channel (in fact, I don't know if they work on ISA/VL IDE
controllers or if PCI is required)


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99)

---
 * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which

[DIMITRIS ZILASKOS]

From: Dimitris Zilaskos 

--===5997703658926392847==
Content-Type: multipart/alternative; boundary=001a1141173ef8ad59053ad6c161

--001a1141173ef8ad59053ad6c161
Content-Type: text/plain; charset=UTF-8

Hi,

After lots of testing and lots of help from Jack Ellis and Eric, I was able
more or less to overcome the roadblocks:

a) Gibberish after boot: use only JEMMEX, and/or replace HIMEMX with XMGR
/T0 (or /B /T0 and then /T0 per documentation)

b)Freedos 1.2 pre22 not booting after installation, requiring sys c: from
2031 bootdisks (sys 2.6) to workaround
see next point

c) Lack of BIOS support for secondary IDE
I installed EZ-BIOS using the hard drive manufacturer's tools found at
http://members.shaw.ca/rinocanada/hdutils.htm
Though aimed to address BIOS drive size limitations, in my cases it added
support for the secondary IDE, and removed the need for workaround after
freedos installation failed to boot

c)rawrite3/hard drive manufacturer's tools complaining about crossing 64K
DMA barrier while wring to floppy:

workaround 1 (only for rawrite3, fails for larger programs such as hard
drive tools): load lowdma.sys early on in config.sys, then lh rawrite3
(slow)
workaround 2 (for both): patched lowdma.sys from Eric that removed the
requirement to use lh (also slow)
workaround 3: boot from windows 98 bootdisk (considerably faster)

d)after rawrite3/hard drive tools writing to disk, dir a: still slows the
old files/directories

this caused some confusion if the tools did the job right with the
workarounds, but reboot proved they work. Windows 98 bootdisk does not
suffer from this issue

e)SB16 IDE CDROMs not being detected by UIDE/UDVD2

Probably I did something wrong the card jumpers or the cabling, as I failed
to replicate the problem. Once it is configured to use the tertiary IDE
channel, it worked fine. This is with a CT 2290 "plug-n-play" card that
needs to be configured from software for sound related settings with the
diagnose.exe tool - IDE IRQ and channel still need jumpers. I failed to get
it to work with a similar CT2910 according to PCB, CT2291 according to the
sticker SB16 card with a very similar but not identical layout, and with
jumpers for everything. Perhaps the card IDE is problematic as sound works
- I did not have time to test if Linux performs better (Windows bootdisk
and creative IDE drivers also fail).

f)UMC8672 dos driver support

I found dos drivers for my VLB controller (PM-67B, UMC8672 based) at
http://driverzone.com/drivers/umc/control/um8672.htm. Unfortunately they do
not work - complain about UM8672 not being detected. Supposedly they would
enable the secondary IDE channel. Perhaps they need the BIOS chip add on on
the card judging from README talking about pressing F10 during boot and a
BIOS style menu which I do not have. In any case, EZ-BIOS removed the need
for such a driver.

Thanks everyone for the help!

Cheers,

Dimitris

On Tue, Aug 9, 2016 at 10:51 PM, TJ Edmister 
wrote:

> On Tue, 09 Aug 2016 13:57:35 -0400, Dimitris Zilaskos
>  wrote:
>
> > The issue I am facing now is that the mechanical drives I connected to
> > the
> > secondary IDE channel of my Vesa Local Bus controller are not detected.
> > Windows 98 SE bootdisk does not detect them either, The BIOS of my system
> > only supports 2 hard drives.
>
> IIRC, if your motherboard BIOS only supports two drives, you could use a
> controller card with its own onboard ROM for additional drives to be
> recognized under DOS (or Win9x). Depending on what chipset the card uses,
> there might also be a driver which can enable the second channel.
>
> Not sure if the various DMA DOS drivers would detect and add drives on the
> second channel (in fact, I don't know if they work on ISA/VL IDE
> controllers or if PCI is required)
>
>
> 
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. http://sdm.link/zohodev2dev
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>

--001a1141173ef8ad59053ad6c161
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,After lots of testing and lots of help
from Jack Ellis and Eric, I was able more or less to overcome the
roadblocks:a) Gibberish after boot: use only JEMMEX,
and/or replace HIMEMX with XMGR /T0 (or /B /T0 and then /T0 per
documentation)b)Freedos 1.2 pre22 not booting after
installation, requiring sys c: from 2031 bootdisks (sys 2.6) to
workaroundsee next pointc) Lack of BIOS
support for secondary 

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,

After lots of testing and lots of help from Jack Ellis and Eric, I was able
more or less to overcome the roadblocks:

a) Gibberish after boot: use only JEMMEX, and/or replace HIMEMX with XMGR
/T0 (or /B /T0 and then /T0 per documentation)

b)Freedos 1.2 pre22 not booting after installation, requiring sys c: from
2031 bootdisks (sys 2.6) to workaround
see next point

c) Lack of BIOS support for secondary IDE
I installed EZ-BIOS using the hard drive manufacturer's tools found at
http://members.shaw.ca/rinocanada/hdutils.htm
Though aimed to address BIOS drive size limitations, in my cases it added
support for the secondary IDE, and removed the need for workaround after
freedos installation failed to boot

c)rawrite3/hard drive manufacturer's tools complaining about crossing 64K
DMA barrier while wring to floppy:

workaround 1 (only for rawrite3, fails for larger programs such as hard
drive tools): load lowdma.sys early on in config.sys, then lh rawrite3
(slow)
workaround 2 (for both): patched lowdma.sys from Eric that removed the
requirement to use lh (also slow)
workaround 3: boot from windows 98 bootdisk (considerably faster)

d)after rawrite3/hard drive tools writing to disk, dir a: still slows the
old files/directories

this caused some confusion if the tools did the job right with the
workarounds, but reboot proved they work. Windows 98 bootdisk does not
suffer from this issue

e)SB16 IDE CDROMs not being detected by UIDE/UDVD2

Probably I did something wrong the card jumpers or the cabling, as I failed
to replicate the problem. Once it is configured to use the tertiary IDE
channel, it worked fine. This is with a CT 2290 "plug-n-play" card that
needs to be configured from software for sound related settings with the
diagnose.exe tool - IDE IRQ and channel still need jumpers. I failed to get
it to work with a similar CT2910 according to PCB, CT2291 according to the
sticker SB16 card with a very similar but not identical layout, and with
jumpers for everything. Perhaps the card IDE is problematic as sound works
- I did not have time to test if Linux performs better (Windows bootdisk
and creative IDE drivers also fail).

f)UMC8672 dos driver support

I found dos drivers for my VLB controller (PM-67B, UMC8672 based) at
http://driverzone.com/drivers/umc/control/um8672.htm. Unfortunately they do
not work - complain about UM8672 not being detected. Supposedly they would
enable the secondary IDE channel. Perhaps they need the BIOS chip add on on
the card judging from README talking about pressing F10 during boot and a
BIOS style menu which I do not have. In any case, EZ-BIOS removed the need
for such a driver.

Thanks everyone for the help!

Cheers,

Dimitris

On Tue, Aug 9, 2016 at 10:51 PM, TJ Edmister 
wrote:

> On Tue, 09 Aug 2016 13:57:35 -0400, Dimitris Zilaskos
>  wrote:
>
> > The issue I am facing now is that the mechanical drives I connected to
> > the
> > secondary IDE channel of my Vesa Local Bus controller are not detected.
> > Windows 98 SE bootdisk does not detect them either, The BIOS of my system
> > only supports 2 hard drives.
>
> IIRC, if your motherboard BIOS only supports two drives, you could use a
> controller card with its own onboard ROM for additional drives to be
> recognized under DOS (or Win9x). Depending on what chipset the card uses,
> there might also be a driver which can enable the second channel.
>
> Not sure if the various DMA DOS drivers would detect and add drives on the
> second channel (in fact, I don't know if they work on ISA/VL IDE
> controllers or if PCI is required)
>
>
> 
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. http://sdm.link/zohodev2dev
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[TJ Edmister]

On Tue, 09 Aug 2016 13:57:35 -0400, Dimitris Zilaskos  
 wrote:

> The issue I am facing now is that the mechanical drives I connected to  
> the
> secondary IDE channel of my Vesa Local Bus controller are not detected.
> Windows 98 SE bootdisk does not detect them either, The BIOS of my system
> only supports 2 hard drives.

IIRC, if your motherboard BIOS only supports two drives, you could use a  
controller card with its own onboard ROM for additional drives to be  
recognized under DOS (or Win9x). Depending on what chipset the card uses,  
there might also be a driver which can enable the second channel.

Not sure if the various DMA DOS drivers would detect and add drives on the  
second channel (in fact, I don't know if they work on ISA/VL IDE  
controllers or if PCI is required)


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,

I had some more time to spend on this project today. I reinstalled Freedos
on a 2 GB disk-on-module. Again after installation I had to do a sys from
2031 bootdisk and then copy kernel.sys to get a bootable freedos 1.2
system. I can use my CDROM connected to the IDE interface on the Sound
Blaster card. So all is fine here apart from past 2031 bootdisks requiring
the workaround to boot from hard drive.

The issue I am facing now is that the mechanical drives I connected to the
secondary IDE channel of my Vesa Local Bus controller are not detected.
Windows 98 SE bootdisk does not detect them either, The BIOS of my system
only supports 2 hard drives. Last time I had this setup working with Linux,
so I will try to dig some old bootdisk to see if Linux can detect the
secondary IDE hard drives. Is there anything I can try from FreeDOS?

Best regards,

Dimitris

On Wed, Jul 20, 2016 at 11:31 PM, Dimitris Zilaskos 
wrote:

> Hi Eric,
>
> I have tried the /FORCE:CHS and it did not help.
>
> Cheers,
>
> Dimitris
>
> On Wed, Jul 20, 2016 at 7:19 PM, Eric Auer  wrote:
>
>>
>> Hi Dimitris,
>>
>> > I retried sys c: from the 2031 bootdisk and it failed to boot, hanging
>> at
>> > Loading FreeDOS, hard drive working like mad, I rebooted with the same
>> > floppy, did the same thing, and it booted. Tried again with sys 3.6e,
>> > hang again, tried again with sys 2.6, was able to boot again.
>>
>> This is a bit confusing but it sounds like a problem with the way
>> that our FAT32 boot sector uses LBA. So with the new SYS 3.6e, you
>> should be able to boot with /FORCE:CHS (explicitly selecting the
>> CHS FAT32 boot sector: SYS 2.6 does not even have a LBA version).
>>
>> This will probably work with various, including newer (and better)
>> versions of the kernel.sys file: In earlier tests, you mentioned
>> that using SYS CONFIG to require pure LBA or pure CHS mode from a
>> kernel did not affect the ability of the kernel to use the drive.
>>
>> Regards, Eric
>>
>>
>>
>> 
>> --
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>> traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols
>> are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning
>> reports.http://sdm.link/zohodev2dev
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>
>
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486 (digression)

[Eric Auer]

Hi JAS,

indeed I am trying to motivate people to use TLS/SSL ;-)
There must be SOME browsers for DOS which can handle it!

Note that I was talking about Google Drive, not the basic
search engine. The Drive needs a lot of heavy JavaScript.

Eric

>  https://www.auersoft.eu/soft/specials/




--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi Eric,

I have tried the /FORCE:CHS and it did not help.

Cheers,

Dimitris

On Wed, Jul 20, 2016 at 7:19 PM, Eric Auer  wrote:

>
> Hi Dimitris,
>
> > I retried sys c: from the 2031 bootdisk and it failed to boot, hanging at
> > Loading FreeDOS, hard drive working like mad, I rebooted with the same
> > floppy, did the same thing, and it booted. Tried again with sys 3.6e,
> > hang again, tried again with sys 2.6, was able to boot again.
>
> This is a bit confusing but it sounds like a problem with the way
> that our FAT32 boot sector uses LBA. So with the new SYS 3.6e, you
> should be able to boot with /FORCE:CHS (explicitly selecting the
> CHS FAT32 boot sector: SYS 2.6 does not even have a LBA version).
>
> This will probably work with various, including newer (and better)
> versions of the kernel.sys file: In earlier tests, you mentioned
> that using SYS CONFIG to require pure LBA or pure CHS mode from a
> kernel did not affect the ability of the kernel to use the drive.
>
> Regards, Eric
>
>
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,

So now I have only the master HDD on primary IDE connected and the floppy.
It did not change anything.

I was able to confirm the CHS/settings - BIOS has a menu called IDE HDD
AUTO DETECTION. When all the jumpers etc are correct, it will detect the
drive and offer 3 options - LBA, LARGE, NORMAL, each with different CHS
settings but same size. Only LBA results in fdisk detecting the HDD and
proceeding, other modes cause FreeDOS to spit error messages about non LBA
partition upon boot, and fdisk does not detect the HDD at all.

Cheers,

Dimitris

On Wed, Jul 20, 2016 at 10:39 PM, Jerome E. Shidel Jr. 
wrote:

>
> On Jul 20, 2016, at 5:23 PM, Dimitris Zilaskos 
> wrote:
>
> Hi,
>
> On Wed, Jul 20, 2016 at 9:50 PM, Jerome E. Shidel Jr. 
> wrote:
>
>> On Jul 20, 2016, at 12:56 PM, Dimitris Zilaskos 
>> wrote:
>> […]
>>
>> Dimitris
>>
>>
>> I have a few silly questions.
>>
>> You have verified the drive has the correct jumpers set?
>>
>
> Correct, master / slave
>
>
> :-)
>
>
>> You are not trying to use cable select mode?
>>
>
> Nope
>
>
> :-)
>
>
>
>>
>> You are using the correct position on the IDE cable?
>>
>
> Yes
>
>
> :-)
>
>
>> You are plugged into the primary controller?
>>
>
> Yes
>
>
> :-)
>
>
>
>>
>> Is the BIOS configuration for the drive being set manually or using
>> "auto" mode?
>>
>
> This is actually a good question. It is user mode which would qualify as
> manually, but I can't remember if the values for CHS were actually entered
> manually by copying them from the labels, or using the auto detect BIOS
> feature. I do recall it look a lot of effort to figure this out, as any
> mistake and the system would not detect the hdds or boot altogether.
>
>>
>> You mentioned “tertiary” at one point. How many drives? How many
>> controllers?
>>
>
> The sound blaster card has one IDE port that currently has 2 CD-ROM drives
> connected in master/slave setup
>
>>
>> Is the drive partitioned as a single disk or multiple partitions?
>>
>
> single partition
>
> :-)
>
>
>> It is not inside an extended partition?
>>
>
> No
>
> :-)
>
>
>
>>
>> If there are any other drives, are they partitioned and formatted for DOS?
>>
>
> Yes, the slave drive is an old windows98 system with a fat32  partition.
>
> I can simplify the setup - remove all CDROM drives and the slave hard
> drive and leave only one hdd and the floppy to see if there is any change.
>
>
> It probably won’t help. But, It wouldn’t hurt to try.
>
>
> Cheers,
>
> Dimitris
>
>
> Mostly, I wanted to verify you weren’t using cable select. I’ve seen it
> work great and I’ve seen it cause weird issues.
> There are some strange jumper settings on some drives. Most just
> master/slave. But others that plus single or multiple, LBA or not…
> Sometimes you just remove all the jumpers, sometimes you hunt around in
> you desk for an hour because you need just one more.
> Oh, IDE was some much fun. Especially, when adding extra cards and raids.
>
> Anyhow, I figured I might as well play “20 questions” and rule out some of
> the simple but often overlooked items.
>
> Jerome
>
>
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,

On Wed, Jul 20, 2016 at 7:56 PM,  wrote:

> On Jul 20, 2016 12:57 PM, "Dimitris Zilaskos"  wrote:
> >
> > Hi
> >
> 
> >
> > Since I now have a bootable C: drive, can't we just compare the working
> MBR/boot sector with the non working one?
> >
> > Cheers,
> >
> > Dimitris
> >
>
> Would you please copy kernel.sys from the 2042 release to your C drive and
> see if it boots.  Do not run sys or anything else, just a simple copy.
> This will help confirm if the issue is with the kernel or sys.  It should
> work.
>

Yes this works perfectly! I just copied kernel.sys from 1.2 boot floppy
over the kernel.sys from 2031 and it worked! I was able to boot from C:
with 2042 kernel.


> If possible I would also appreciate if you could recap for me which
> version of sys you ran and options that provided a booting system (kernels
> don't necessarily relate to sys versions).  E.g.  sys 2.6 with command of
> sys C:
>

sys c: , with sys version 2.6, works.

> I may ask you to send me your boot sector privately.  Latest sys can
> easily save it.
>

Sure, this is no problem.

Cheers,

Dimitris
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Jerome E. Shidel Jr.]

> On Jul 20, 2016, at 5:23 PM, Dimitris Zilaskos  wrote:
> 
> Hi,
> 
> On Wed, Jul 20, 2016 at 9:50 PM, Jerome E. Shidel Jr.  > wrote:
>> On Jul 20, 2016, at 12:56 PM, Dimitris Zilaskos > > wrote:
>> […]
>> Dimitris
> 
> I have a few silly questions.
> 
> You have verified the drive has the correct jumpers set?
> 
> Correct, master / slave 

:-)

> 
> 
> You are not trying to use cable select mode?
> 
> Nope

:-)

>  
> 
> You are using the correct position on the IDE cable?
> 
> Yes 

:-)

> 
> You are plugged into the primary controller?
> 
> Yes

:-)

>  
> 
> Is the BIOS configuration for the drive being set manually or using "auto" 
> mode?
> 
> This is actually a good question. It is user mode which would qualify as 
> manually, but I can't remember if the values for CHS were actually entered 
> manually by copying them from the labels, or using the auto detect BIOS 
> feature. I do recall it look a lot of effort to figure this out, as any 
> mistake and the system would not detect the hdds or boot altogether. 
> 
> You mentioned “tertiary” at one point. How many drives? How many controllers? 
> 
> The sound blaster card has one IDE port that currently has 2 CD-ROM drives 
> connected in master/slave setup 
> 
> Is the drive partitioned as a single disk or multiple partitions?
> 
> single partition 
:-)
> 
> It is not inside an extended partition?
> 
> No
:-)
>  
> 
> If there are any other drives, are they partitioned and formatted for DOS?
> 
> Yes, the slave drive is an old windows98 system with a fat32  partition.
> 
> I can simplify the setup - remove all CDROM drives and the slave hard drive 
> and leave only one hdd and the floppy to see if there is any change.

It probably won’t help. But, It wouldn’t hurt to try. 

> 
> Cheers,
> 
> Dimitris

Mostly, I wanted to verify you weren’t using cable select. I’ve seen it work 
great and I’ve seen it cause weird issues. 
There are some strange jumper settings on some drives. Most just master/slave. 
But others that plus single or multiple, LBA or not…
Sometimes you just remove all the jumpers, sometimes you hunt around in you 
desk for an hour because you need just one more.
Oh, IDE was some much fun. Especially, when adding extra cards and raids. 

Anyhow, I figured I might as well play “20 questions” and rule out some of the 
simple but often overlooked items. 

Jerome


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,

On Wed, Jul 20, 2016 at 9:50 PM, Jerome E. Shidel Jr. 
wrote:

> On Jul 20, 2016, at 12:56 PM, Dimitris Zilaskos 
> wrote:
> […]
>
> Dimitris
>
>
> I have a few silly questions.
>
> You have verified the drive has the correct jumpers set?
>

Correct, master / slave

>
> You are not trying to use cable select mode?
>

Nope


>
> You are using the correct position on the IDE cable?
>

Yes

>
> You are plugged into the primary controller?
>

Yes


>
> Is the BIOS configuration for the drive being set manually or using "auto"
> mode?
>

This is actually a good question. It is user mode which would qualify as
manually, but I can't remember if the values for CHS were actually entered
manually by copying them from the labels, or using the auto detect BIOS
feature. I do recall it look a lot of effort to figure this out, as any
mistake and the system would not detect the hdds or boot altogether.

>
> You mentioned “tertiary” at one point. How many drives? How many
> controllers?
>

The sound blaster card has one IDE port that currently has 2 CD-ROM drives
connected in master/slave setup

>
> Is the drive partitioned as a single disk or multiple partitions?
>

single partition

>
> It is not inside an extended partition?
>


No


>
> If there are any other drives, are they partitioned and formatted for DOS?
>

Yes, the slave drive is an old windows98 system with a fat32  partition.

I can simplify the setup - remove all CDROM drives and the slave hard drive
and leave only one hdd and the floppy to see if there is any change.

Cheers,

Dimitris
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Jerome E. Shidel Jr.]

> On Jul 20, 2016, at 12:56 PM, Dimitris Zilaskos  wrote:
> […]
> Dimitris

I have a few silly questions.

You have verified the drive has the correct jumpers set?


You are not trying to use cable select mode?

You are using the correct position on the IDE cable?

You are plugged into the primary controller?

Is the BIOS configuration for the drive being set manually or using "auto" mode?

You mentioned “tertiary” at one point. How many drives? How many controllers? 

Is the drive partitioned as a single disk or multiple partitions?

It is not inside an extended partition?

If there are any other drives, are they partitioned and formatted for DOS?


Jerome--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Eric Auer]

Hi Dimitris,

> I retried sys c: from the 2031 bootdisk and it failed to boot, hanging at
> Loading FreeDOS, hard drive working like mad, I rebooted with the same
> floppy, did the same thing, and it booted. Tried again with sys 3.6e,
> hang again, tried again with sys 2.6, was able to boot again.

This is a bit confusing but it sounds like a problem with the way
that our FAT32 boot sector uses LBA. So with the new SYS 3.6e, you
should be able to boot with /FORCE:CHS (explicitly selecting the
CHS FAT32 boot sector: SYS 2.6 does not even have a LBA version).

This will probably work with various, including newer (and better)
versions of the kernel.sys file: In earlier tests, you mentioned
that using SYS CONFIG to require pure LBA or pure CHS mode from a
kernel did not affect the ability of the kernel to use the drive.

Regards, Eric



--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi

On Wed, Jul 20, 2016 at 2:09 PM, Eric Auer  wrote:

>
> Hi Dimitris,
>
> > So I did, with sys 3.6e - FreeDOS 1.2 pre floppy:
> >
> > sys c: /FORCE:CHS - system hangs on reboot
> > sys c: /FORCE:LBA , followed by sys CONFIG c:\kernel.sys FORCELBA=1
> > GLOBALENABLELBA=1
> >
> > - system tries to BOOT, hangs at Loading FreeDOS , the hard drive
> > works like mad until I hit control-alt-delete
>
> (and the same with SYS 2.6 and kernel 2042 with DISabled LBA)
>
> What if you use /FORCE:LBA but without any SYS CONFIG?
>

Hangs right after Loading FreeDOS, hard drive works like mad

>
> And of course: What if you use SYS 3.6e but with some
> older version of the kernel?


sys 3.6e with kernel 2031 hangs at BIOS summary


>
> If the system hangs on reboot with the CHS boot sector,
> it is possible that your FAT32 boot partition either is
> outside the CHS-reachable area or that the MBR, BIOS and
> DOS disagree about what the CHS geometry should be. But:
>
> On the other hand, you wrote that kernel 2031 boots for
> you with SYS 2.6, while SYS 2.6 always uses CHS on FAT32!
>
> Note that SYS 3.6e also lets you use force options for
> the BIOS disk number. In case something gets confused
> by your relatively large collection of connected disks.
>
>
>
I retried sys c: from the 2031 bootdisk and it failed to boot, hanging at
Loading FreeDOS, hard drive working like mad, I rebooted with the same
floppy, did the same thing, and it booted. Tried again with sys 3.6e, hang
again, tried again with sys 2.6, was able to boot again.

Since I now have a bootable C: drive, can't we just compare the working
MBR/boot sector with the non working one?

Cheers,

Dimitris
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Eric Auer]

Hi Dimitris,

> So I did, with sys 3.6e - FreeDOS 1.2 pre floppy:
> 
> sys c: /FORCE:CHS - system hangs on reboot
> sys c: /FORCE:LBA , followed by sys CONFIG c:\kernel.sys FORCELBA=1
> GLOBALENABLELBA=1
> 
> - system tries to BOOT, hangs at Loading FreeDOS , the hard drive
> works like mad until I hit control-alt-delete

(and the same with SYS 2.6 and kernel 2042 with DISabled LBA)

What if you use /FORCE:LBA but without any SYS CONFIG?

And of course: What if you use SYS 3.6e but with some
older version of the kernel?

If the system hangs on reboot with the CHS boot sector,
it is possible that your FAT32 boot partition either is
outside the CHS-reachable area or that the MBR, BIOS and
DOS disagree about what the CHS geometry should be. But:

On the other hand, you wrote that kernel 2031 boots for
you with SYS 2.6, while SYS 2.6 always uses CHS on FAT32!

Note that SYS 3.6e also lets you use force options for
the BIOS disk number. In case something gets confused
by your relatively large collection of connected disks.

Cheers, Eric



--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,

I have tried sys 2.6 with 2042, I checked and sys CONFIG reported both
FORCELBA and GLOBALENABLELBA were set to 0. Reboot resuts in a hang at
Loading FreeDOS, hard drive and the floppy leds are lit up and hard drive
works like mad.

Cheers,

Dimitris

On Wed, Jul 20, 2016 at 1:25 PM, Dimitris Zilaskos 
wrote:

> Hi,
>
>
> On Wed, Jul 20, 2016 at 12:58 PM, Eric Auer  wrote:
>
>>
>> Hi Dimitris,
>>
>> long analysis follows, some suggestions at the bottom of this mail :-)
>>
>> > Thank you for your reply. I tried few kernel and here are the results:
>>
>> I gather you mean "you tried the SYS of a few kernels together with
>> the corresponding KERNEL versions"? My focus is on the SYS activity,
>> as the kernel should at least show a version message before hanging
>> as long as the boot sector put by SYS has done the correct stuff.
>>
>
> I downloaded the zip file, extracted the contents of BIN on a floppy,
> executed install.bat from the floppy inserted in the 486 system. Sometimes
> I modified install.bat, others just ran sys c: from within the BIN folder,
> sometimes I copied the bin folder to the 486 hdd, ran install.bat, rebooted
> from floppy and then sys c:, reboot. I was not very consistent.
>
>>
>> > 2041_86f16 : floppy boots but no hard drives detected
>>
>> If you only have FAT32 partitions, then using a kernel without
>> FAT32 support would lead to that expected result, yes ;-)
>>
>
> Ok, makes sense.
>
>
>>
>> Other versions, sorted (2020 is anycient anyway) from old to new:
>>
>> > 2030: BOOTS!
>> > 2031_32: BOOTS!
>>
>> > 2032: hangs
>> > 2032a: hangs
>>
>> > 2035a: boots, detects HDD, sys [...] hard drive fails to boot
>> > 2039_86f32: as above
>> > 2041_[3]86f32: as above
>>
>> In short, we introduced a bug in the SYS of version 2032?
>> That would be 2003-09-21 while version 2031 is 2003-07-19.
>>
>> But your pictures on Google seem to say that version 2032
>> still is okay, while newer versions are not okay?
>>
>
> I do not think this is correct. 2031 is the latest version that was able
> to boot my system from hard drive. I am using the version referring both to
> kernel.sys and the accompanying sys in the zip file where I got the kernel
> from - probably this is confusing.
>
>
>>
>> > And that one results in a hang:
>> >
>> > https://drive.google.com/open?id=0B2zW1ur6Z_WedkQtSXBYMS1YN0U
>>
>> As Google is a pain for DOS users, a summary of what it says...
>>
>> SYS 2.8 detects FAT32, FAT at sector 3f+20, 0 root dir entries,
>> FAT at sector 63+32, root dir at PREVIOUS + 0*2, kernel.sys has
>> 45884 bytes, command.com has 92109 bytes... (date 2003-09-21)
>>
>> > This is a successfully sys c: output
>> >
>> > https://drive.google.com/open?id=0B2zW1ur6Z_WeX1pZSXktNTd3SFE
>>
>> SYS 2.6 (unknown date) kernel.sys 44900 bytes, FAT at sector 5f
>> which is 3f+20, data at sector 603f, 0 root dir entries, 255 root
>> dir sectors (really???), FAT at sector 487060009 = 63+32 (???),
>> root dir at sector 1313429276 = PREVIOUS + 0*2, data starts at
>> sector 1163081785 = PREVIOUS + 255, command.com is 92109 bytes.
>>
>> Note that the displayed numbers look very wrong, so SYS might be
>> calculating bogus FAT32 parameters... Or maybe it only displays
>> wrong values, while internally using correct values. This can be
>> a side effect of compiling SYS with the "wrong" compiler in case
>> of incomplete portability. The weird thing is that SYS works for
>> you in version 2.6 :-)
>>
>> Checking the source code...
>>
>> >
>> https://sourceforge.net/p/freedos/svn/1744/log/?path=/kernel/trunk/sys/sys.c
>>
>> 2009: Jeremy introduced a command line option to force CHS / LBA.
>>
>> 2004, 2009, 2010, 2011: Fixes to make things work for all compilers?
>>
>> 2007: Faster file copy, update FAT32 backup boot sector if needed.
>>
>> 2007: Fixes for FAT32
>>
>> 2003-09-21: Metakern compatibility r702
>>
>> 2003-08-08: Support for other sector sizes on FAT16, SYS 2.7
>> (note that the kernel itself only works for 512 byte sectors)
>>
>> 2003-06-16: This is version SYS 2.6 here.
>>
>> >
>> https://sourceforge.net/p/freedos/svn/607/tree/kernel/trunk/boot/boot32.asm
>>
>> > https://sourceforge.net/p/freedos/svn/607/tree/kernel/trunk/sys/sys.c
>>
>> etc. Note that SYS 2.6 only supports CHS style boot for FAT32!
>>
>> I suggest the following: Apparently the FAT32 boot sectors have
>> not changed since 2004, but SYS itself has evolved further. In
>> particular, try the newest SYS 3.6e which has two options for
>> /FORCE:LBA and /FORCE:CHS with obvious effects. Please try with
>> /VERBOSE and with > output.txt so you can paste results into a
>> mail, without Javascript-heavy DOS-unfriendly Google Drive pics.
>>
>> I see two possible problems: Either your BIOS supports LBA but
>> our FAT32 LBA boot sector is incompatible with it. In that case,
>> the /FORCE:CHS option for SYS will help you. Or SYS itself has
>> errors in calculating FAT32 parameters. Then both LBA and CHS
>> might be 

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,


On Wed, Jul 20, 2016 at 12:58 PM, Eric Auer  wrote:

>
> Hi Dimitris,
>
> long analysis follows, some suggestions at the bottom of this mail :-)
>
> > Thank you for your reply. I tried few kernel and here are the results:
>
> I gather you mean "you tried the SYS of a few kernels together with
> the corresponding KERNEL versions"? My focus is on the SYS activity,
> as the kernel should at least show a version message before hanging
> as long as the boot sector put by SYS has done the correct stuff.
>

I downloaded the zip file, extracted the contents of BIN on a floppy,
executed install.bat from the floppy inserted in the 486 system. Sometimes
I modified install.bat, others just ran sys c: from within the BIN folder,
sometimes I copied the bin folder to the 486 hdd, ran install.bat, rebooted
from floppy and then sys c:, reboot. I was not very consistent.

>
> > 2041_86f16 : floppy boots but no hard drives detected
>
> If you only have FAT32 partitions, then using a kernel without
> FAT32 support would lead to that expected result, yes ;-)
>

Ok, makes sense.


>
> Other versions, sorted (2020 is anycient anyway) from old to new:
>
> > 2030: BOOTS!
> > 2031_32: BOOTS!
>
> > 2032: hangs
> > 2032a: hangs
>
> > 2035a: boots, detects HDD, sys [...] hard drive fails to boot
> > 2039_86f32: as above
> > 2041_[3]86f32: as above
>
> In short, we introduced a bug in the SYS of version 2032?
> That would be 2003-09-21 while version 2031 is 2003-07-19.
>
> But your pictures on Google seem to say that version 2032
> still is okay, while newer versions are not okay?
>

I do not think this is correct. 2031 is the latest version that was able to
boot my system from hard drive. I am using the version referring both to
kernel.sys and the accompanying sys in the zip file where I got the kernel
from - probably this is confusing.


>
> > And that one results in a hang:
> >
> > https://drive.google.com/open?id=0B2zW1ur6Z_WedkQtSXBYMS1YN0U
>
> As Google is a pain for DOS users, a summary of what it says...
>
> SYS 2.8 detects FAT32, FAT at sector 3f+20, 0 root dir entries,
> FAT at sector 63+32, root dir at PREVIOUS + 0*2, kernel.sys has
> 45884 bytes, command.com has 92109 bytes... (date 2003-09-21)
>
> > This is a successfully sys c: output
> >
> > https://drive.google.com/open?id=0B2zW1ur6Z_WeX1pZSXktNTd3SFE
>
> SYS 2.6 (unknown date) kernel.sys 44900 bytes, FAT at sector 5f
> which is 3f+20, data at sector 603f, 0 root dir entries, 255 root
> dir sectors (really???), FAT at sector 487060009 = 63+32 (???),
> root dir at sector 1313429276 = PREVIOUS + 0*2, data starts at
> sector 1163081785 = PREVIOUS + 255, command.com is 92109 bytes.
>
> Note that the displayed numbers look very wrong, so SYS might be
> calculating bogus FAT32 parameters... Or maybe it only displays
> wrong values, while internally using correct values. This can be
> a side effect of compiling SYS with the "wrong" compiler in case
> of incomplete portability. The weird thing is that SYS works for
> you in version 2.6 :-)
>
> Checking the source code...
>
> >
> https://sourceforge.net/p/freedos/svn/1744/log/?path=/kernel/trunk/sys/sys.c
>
> 2009: Jeremy introduced a command line option to force CHS / LBA.
>
> 2004, 2009, 2010, 2011: Fixes to make things work for all compilers?
>
> 2007: Faster file copy, update FAT32 backup boot sector if needed.
>
> 2007: Fixes for FAT32
>
> 2003-09-21: Metakern compatibility r702
>
> 2003-08-08: Support for other sector sizes on FAT16, SYS 2.7
> (note that the kernel itself only works for 512 byte sectors)
>
> 2003-06-16: This is version SYS 2.6 here.
>
> >
> https://sourceforge.net/p/freedos/svn/607/tree/kernel/trunk/boot/boot32.asm
>
> > https://sourceforge.net/p/freedos/svn/607/tree/kernel/trunk/sys/sys.c
>
> etc. Note that SYS 2.6 only supports CHS style boot for FAT32!
>
> I suggest the following: Apparently the FAT32 boot sectors have
> not changed since 2004, but SYS itself has evolved further. In
> particular, try the newest SYS 3.6e which has two options for
> /FORCE:LBA and /FORCE:CHS with obvious effects. Please try with
> /VERBOSE and with > output.txt so you can paste results into a
> mail, without Javascript-heavy DOS-unfriendly Google Drive pics.
>
> I see two possible problems: Either your BIOS supports LBA but
> our FAT32 LBA boot sector is incompatible with it. In that case,
> the /FORCE:CHS option for SYS will help you. Or SYS itself has
> errors in calculating FAT32 parameters. Then both LBA and CHS
> might be broken in certain versions of SYS, but should at least
> be fixed again in newest versions.
>
> >
> https://sourceforge.net/p/freedos/svn/1744/log/?path=/kernel/trunk/boot/boot32.asm
>
> >
> https://sourceforge.net/p/freedos/svn/1744/log/?path=/kernel/trunk/boot/boot32lb.asm
>
> This tells me that the FAT32 boot sectors changed at those dates:
>
> 2004-01-24 different load seg and stack handling, no int 13.0
> (SYS 3.1, kernel 2.0.33, claims to improve FAT parameter 

Re: [Freedos-user] Which freedos on 486

[Eric Auer]

Hi Dimitris,

long analysis follows, some suggestions at the bottom of this mail :-)

> Thank you for your reply. I tried few kernel and here are the results:

I gather you mean "you tried the SYS of a few kernels together with
the corresponding KERNEL versions"? My focus is on the SYS activity,
as the kernel should at least show a version message before hanging
as long as the boot sector put by SYS has done the correct stuff.

> 2041_86f16 : floppy boots but no hard drives detected

If you only have FAT32 partitions, then using a kernel without
FAT32 support would lead to that expected result, yes ;-)

Other versions, sorted (2020 is anycient anyway) from old to new:

> 2030: BOOTS!
> 2031_32: BOOTS!

> 2032: hangs
> 2032a: hangs

> 2035a: boots, detects HDD, sys [...] hard drive fails to boot
> 2039_86f32: as above
> 2041_[3]86f32: as above

In short, we introduced a bug in the SYS of version 2032?
That would be 2003-09-21 while version 2031 is 2003-07-19.

But your pictures on Google seem to say that version 2032
still is okay, while newer versions are not okay?

> And that one results in a hang:
> 
> https://drive.google.com/open?id=0B2zW1ur6Z_WedkQtSXBYMS1YN0U

As Google is a pain for DOS users, a summary of what it says...

SYS 2.8 detects FAT32, FAT at sector 3f+20, 0 root dir entries,
FAT at sector 63+32, root dir at PREVIOUS + 0*2, kernel.sys has
45884 bytes, command.com has 92109 bytes... (date 2003-09-21)

> This is a successfully sys c: output
>
> https://drive.google.com/open?id=0B2zW1ur6Z_WeX1pZSXktNTd3SFE

SYS 2.6 (unknown date) kernel.sys 44900 bytes, FAT at sector 5f
which is 3f+20, data at sector 603f, 0 root dir entries, 255 root
dir sectors (really???), FAT at sector 487060009 = 63+32 (???),
root dir at sector 1313429276 = PREVIOUS + 0*2, data starts at
sector 1163081785 = PREVIOUS + 255, command.com is 92109 bytes.

Note that the displayed numbers look very wrong, so SYS might be
calculating bogus FAT32 parameters... Or maybe it only displays
wrong values, while internally using correct values. This can be
a side effect of compiling SYS with the "wrong" compiler in case
of incomplete portability. The weird thing is that SYS works for
you in version 2.6 :-)

Checking the source code...

> https://sourceforge.net/p/freedos/svn/1744/log/?path=/kernel/trunk/sys/sys.c

2009: Jeremy introduced a command line option to force CHS / LBA.

2004, 2009, 2010, 2011: Fixes to make things work for all compilers?

2007: Faster file copy, update FAT32 backup boot sector if needed.

2007: Fixes for FAT32

2003-09-21: Metakern compatibility r702

2003-08-08: Support for other sector sizes on FAT16, SYS 2.7
(note that the kernel itself only works for 512 byte sectors)

2003-06-16: This is version SYS 2.6 here.

> https://sourceforge.net/p/freedos/svn/607/tree/kernel/trunk/boot/boot32.asm

> https://sourceforge.net/p/freedos/svn/607/tree/kernel/trunk/sys/sys.c

etc. Note that SYS 2.6 only supports CHS style boot for FAT32!

I suggest the following: Apparently the FAT32 boot sectors have
not changed since 2004, but SYS itself has evolved further. In
particular, try the newest SYS 3.6e which has two options for
/FORCE:LBA and /FORCE:CHS with obvious effects. Please try with
/VERBOSE and with > output.txt so you can paste results into a
mail, without Javascript-heavy DOS-unfriendly Google Drive pics.

I see two possible problems: Either your BIOS supports LBA but
our FAT32 LBA boot sector is incompatible with it. In that case,
the /FORCE:CHS option for SYS will help you. Or SYS itself has
errors in calculating FAT32 parameters. Then both LBA and CHS
might be broken in certain versions of SYS, but should at least
be fixed again in newest versions.

> https://sourceforge.net/p/freedos/svn/1744/log/?path=/kernel/trunk/boot/boot32.asm

> https://sourceforge.net/p/freedos/svn/1744/log/?path=/kernel/trunk/boot/boot32lb.asm

This tells me that the FAT32 boot sectors changed at those dates:

2004-01-24 different load seg and stack handling, no int 13.0
(SYS 3.1, kernel 2.0.33, claims to improve FAT parameter calculation)

2003-09-21 different padding, a:\metakern.sys detect & use (SYS 2.8)
(not sure if SYS really copies metakern.sys to the target drive??)

2003-08-08 new CHS and LBA FAT32 boot sectors (patches: Jon & me)
and new CHS-LBA-auto-detect FAT12 FAT16 boot sector (by Tom) (SYS 2.7)

Note that SYS 2.6 and older did not support LBA for FAT32 at all
and the CHS FAT32 and CHS or LBA FAT12 FAT16 boot were different.

The different versions of the kernel download (which include SYS)
can be found in our Sourceforge file area:

https://sourceforge.net/projects/freedos/files/Kernel/

Thanks! Cheers, Eric



--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 

Re: [Freedos-user] Which freedos on 486

[Eric Auer]

By the way, Rugxulo... :-)

https://www.auersoft.eu/soft/specials/

After only a few years, my domain should be up more often again :-)
So in case you have hidden it in LSM links, it can be shown again.

Cheers, Eric

> Heck, since you say you have Debian (but is that separate machine?),
> you could try Eric's Sys-FreeDOS-Linux (Perl + NASM) there.
> 
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/sys/sys-freedos-linux/



--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,

Thank you for your reply. I tried few kernel and here are the results:

2041_86f16 : floppy boots but no hard drives detected
2041_86f32: boots, detects HDD, sys is successfull but hard drive fails to
boot
2041_386f32: as above
2039_86f32: as above
2035a: as above
2020: fails to boot even from floppy-hangs at unable to open c:\freedos.log
2030: BOOTS!
2032a32:hangs
2032:hangs
2031_32: BOOTS!

This is a successfully sys c: output

https://drive.google.com/open?id=0B2zW1ur6Z_WeX1pZSXktNTd3SFE

And that one results in a hang:

https://drive.google.com/open?id=0B2zW1ur6Z_WedkQtSXBYMS1YN0U

Cheers,

Dimitris

On Wed, Jul 20, 2016 at 12:04 AM, Rugxulo  wrote:

> Hi,
>
> On Tue, Jul 19, 2016 at 8:26 AM, Dimitris Zilaskos 
> wrote:
> >
> > I have LBA configured in the BIOS for the hard drives, mostly because it
> > keeps BIOS boot and Windows 98 working. I was unable so far to find a
> > working combination with different non LBA modes. I will retry sys c: on
> a
> > new FAT32 installation.
>
> Try different SYSs from different kernels (e.g. 2039, 2041). You
> already tried 2042 and 2036, yes? Who knows, it's a long shot, but it
> could be a rare bug / regression.
>
> https://sourceforge.net/projects/freedos/files/Kernel/
>
> Heck, since you say you have Debian (but is that separate machine?),
> you could try Eric's Sys-FreeDOS-Linux (Perl + NASM) there.
>
>
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/sys/sys-freedos-linux/
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Rugxulo]

Hi,

On Tue, Jul 19, 2016 at 8:26 AM, Dimitris Zilaskos  wrote:
>
> I have LBA configured in the BIOS for the hard drives, mostly because it
> keeps BIOS boot and Windows 98 working. I was unable so far to find a
> working combination with different non LBA modes. I will retry sys c: on a
> new FAT32 installation.

Try different SYSs from different kernels (e.g. 2039, 2041). You
already tried 2042 and 2036, yes? Who knows, it's a long shot, but it
could be a rare bug / regression.

https://sourceforge.net/projects/freedos/files/Kernel/

Heck, since you say you have Debian (but is that separate machine?),
you could try Eric's Sys-FreeDOS-Linux (Perl + NASM) there.

http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/sys/sys-freedos-linux/

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,

No EDD here: ERROR: Your BIOS/INT13h doesn't support EDD extension.

Cheers,

Dimitris

On Tue, Jul 19, 2016 at 7:16 AM, Louis Santillan  wrote:

> Dimitris,
>
> What does EDDINFO [0] display?
>
>
> [0] http://rayer.g6.cz/programm/eddinfo.exe
>
> On Mon, Jul 18, 2016 at 10:56 PM, Mateusz Viste  wrote:
> > I might be missing the boat here, but what you describe vaguely look
> > like a problem I had in some distant past, when I misconfigured my HDD
> > in the BIOS.
> >
> > Perhaps you could check whether your drive's geometry is 100% correct in
> > your BIOS?
> >
> > Mateusz
> >
> >
> >
> >
> > On 19/07/2016 07:12, Dimitris Zilaskos wrote:
> >> Hi,
> >>
> >> I was able to reinstall and boot successfully by performing an fdisk
> >> without FAT32 support, and creating a FAT16 2GB partition. At least with
> >> JEMM386, that is. So FAT32 support being the issue may be the case.
> >>
> >> Let me know if I can try anything else to confirm that.
> >>
> >> Cheers,
> >>
> >> Dimitris
> >>
> >> On Tue, Jul 19, 2016 at 6:03 AM, Dimitris Zilaskos  >> > wrote:
> >>
> >> Hi,
> >>
> >> On Tue, Jul 19, 2016 at 1:58 AM, Rugxulo  >> > wrote:
> >>
> >> Hi,
> >>
> >> On Mon, Jul 18, 2016 at 7:21 PM, Dimitris Zilaskos
> >> > wrote:
> >> >
> >> > Thank you for following up. fdisk reports that C: drive is
> already active. I
> >> > did run mbrzap it completed successfully but there has been
> no change,
> >> > system gets stuck right after BIOS summary table.
> >>
> >> What filesystem(s) are you using? FAT32, presumably. You said
> >> you had
> >> 4 GB and 6 GB HDDs, right?
> >>
> >> Sometimes it has been noticed that a FAT32 partition is created
> with
> >> plain type 0xB instead of 0xC (LBA), so you may have to change
> that.
> >>
> >> http://help.fdos.org/en/hhstndrd/base/fdisk.htm
> >>
> >> I'm not entirely sure what is most informative or useful here:
> >> "/STATUS"? "/XO"? "/SPEC"?
> >>
> >> Honestly, I think I just used BootMgr to change it:
> >>
> >> http://www.freedos.org/software/?prog=bootmgr
> >>
> >> (This may not be your problem, I'm just grasping at straws.)
> >>
> >>
> >>
> >> Indeed the partition type is 11. I have used fdisk to change that to
> >> 12 but there was no change. I did a re-installation after the change
> >> too.
> >>
> >> Cheers,
> >>
> >> Dimitris
> >>
> >>
> >>
> >
> >
> >
> >
> --
> > What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> > patterns at an interface-level. Reveals which users, apps, and protocols
> are
> > consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> > J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> > reports.http://sdm.link/zohodev2dev
> > ___
> > Freedos-user mailing list
> > Freedos-user@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,

I will try to double check. It was difficult for me to find a working
combination of CHS and mode. However Windows98 had no issues with identical
settings.

Best regards,

Dimitris

On Tue, Jul 19, 2016 at 6:56 AM, Mateusz Viste  wrote:

> I might be missing the boat here, but what you describe vaguely look
> like a problem I had in some distant past, when I misconfigured my HDD
> in the BIOS.
>
> Perhaps you could check whether your drive's geometry is 100% correct in
> your BIOS?
>
> Mateusz
>
>
>
>
> On 19/07/2016 07:12, Dimitris Zilaskos wrote:
> > Hi,
> >
> > I was able to reinstall and boot successfully by performing an fdisk
> > without FAT32 support, and creating a FAT16 2GB partition. At least with
> > JEMM386, that is. So FAT32 support being the issue may be the case.
> >
> > Let me know if I can try anything else to confirm that.
> >
> > Cheers,
> >
> > Dimitris
> >
> > On Tue, Jul 19, 2016 at 6:03 AM, Dimitris Zilaskos  > > wrote:
> >
> > Hi,
> >
> > On Tue, Jul 19, 2016 at 1:58 AM, Rugxulo  > > wrote:
> >
> > Hi,
> >
> > On Mon, Jul 18, 2016 at 7:21 PM, Dimitris Zilaskos
> > > wrote:
> > >
> > > Thank you for following up. fdisk reports that C: drive is
> already active. I
> > > did run mbrzap it completed successfully but there has been no
> change,
> > > system gets stuck right after BIOS summary table.
> >
> > What filesystem(s) are you using? FAT32, presumably. You said
> > you had
> > 4 GB and 6 GB HDDs, right?
> >
> > Sometimes it has been noticed that a FAT32 partition is created
> with
> > plain type 0xB instead of 0xC (LBA), so you may have to change
> that.
> >
> > http://help.fdos.org/en/hhstndrd/base/fdisk.htm
> >
> > I'm not entirely sure what is most informative or useful here:
> > "/STATUS"? "/XO"? "/SPEC"?
> >
> > Honestly, I think I just used BootMgr to change it:
> >
> > http://www.freedos.org/software/?prog=bootmgr
> >
> > (This may not be your problem, I'm just grasping at straws.)
> >
> >
> >
> > Indeed the partition type is 11. I have used fdisk to change that to
> > 12 but there was no change. I did a re-installation after the change
> > too.
> >
> > Cheers,
> >
> > Dimitris
> >
> >
> >
>
>
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Eric Auer]

Hi Dimitris and others,

as I received some (aggressive) corrections from Jack and Johnson:

Yes of course I can read manuals myself. The XMGR option /T0 means
'No "E820h" nor "E801h" requests.' so please try if the two HIMEMX
options /X (no int 15.e820 requests) and /NOABOVE16 (no int 15.e801
requests) options make things work even with HIMEMX :-) Remember to
update both the installer boot config and config on C: afterwards.

My excuses for guessing that A20 issues might be the problem here.
Jack's implicit suggestion that the BIOS has int 15 bugs is better.

Next topic: I do NOT claim that FDISK /MBR should help you. I only
replied to the other posting where somebody suggested that. I have
no opinion about which DOS brands should benefit from updating MBR.
But I wanted to warn about possible side effects of FDISK /MBR ...

Third topic: 486 often can NOT boot from CD-ROM, but the Smart Boot
Manager is pretty cool! It can be installed to a boot floppy which
then helps you to boot from CD-ROM, even without full BIOS support:

http://btmgr.sourceforge.net/about.html



Now to reply to the other 486 related reactions on the mailing list:

I see that you have not been able to make SBM work on your 486 yet,
but there could still be some trick to make it work even there :-)

Also interesting that booting failed from FAT32 but not from FAT16:
It may also make a difference whether you use LBA or non-LBA for the
partition type. There also is a small chance that DOS and BIOS are
not agreeing about CHS geometry, although this should not happen. It
can be an idea to manually use SYS command line options to get boot
sectors for FAT32-LBA instead of FAT32-CHS or vice versa.

As far as I remember, our FAT16 boot sector auto-selects CHS or LBA.
As Louis wrote, the default FAT32 boot sector may need LBA and your
BIOS may be without LBA or with LBA bugs. Try SYS-ing FAT32 to CHS.

Cheers, Eric



--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Louis Santillan]

Dimitris,

What does EDDINFO [0] display?


[0] http://rayer.g6.cz/programm/eddinfo.exe

On Mon, Jul 18, 2016 at 10:56 PM, Mateusz Viste  wrote:
> I might be missing the boat here, but what you describe vaguely look
> like a problem I had in some distant past, when I misconfigured my HDD
> in the BIOS.
>
> Perhaps you could check whether your drive's geometry is 100% correct in
> your BIOS?
>
> Mateusz
>
>
>
>
> On 19/07/2016 07:12, Dimitris Zilaskos wrote:
>> Hi,
>>
>> I was able to reinstall and boot successfully by performing an fdisk
>> without FAT32 support, and creating a FAT16 2GB partition. At least with
>> JEMM386, that is. So FAT32 support being the issue may be the case.
>>
>> Let me know if I can try anything else to confirm that.
>>
>> Cheers,
>>
>> Dimitris
>>
>> On Tue, Jul 19, 2016 at 6:03 AM, Dimitris Zilaskos > > wrote:
>>
>> Hi,
>>
>> On Tue, Jul 19, 2016 at 1:58 AM, Rugxulo > > wrote:
>>
>> Hi,
>>
>> On Mon, Jul 18, 2016 at 7:21 PM, Dimitris Zilaskos
>> > wrote:
>> >
>> > Thank you for following up. fdisk reports that C: drive is already 
>> active. I
>> > did run mbrzap it completed successfully but there has been no 
>> change,
>> > system gets stuck right after BIOS summary table.
>>
>> What filesystem(s) are you using? FAT32, presumably. You said
>> you had
>> 4 GB and 6 GB HDDs, right?
>>
>> Sometimes it has been noticed that a FAT32 partition is created with
>> plain type 0xB instead of 0xC (LBA), so you may have to change that.
>>
>> http://help.fdos.org/en/hhstndrd/base/fdisk.htm
>>
>> I'm not entirely sure what is most informative or useful here:
>> "/STATUS"? "/XO"? "/SPEC"?
>>
>> Honestly, I think I just used BootMgr to change it:
>>
>> http://www.freedos.org/software/?prog=bootmgr
>>
>> (This may not be your problem, I'm just grasping at straws.)
>>
>>
>>
>> Indeed the partition type is 11. I have used fdisk to change that to
>> 12 but there was no change. I did a re-installation after the change
>> too.
>>
>> Cheers,
>>
>> Dimitris
>>
>>
>>
>
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports.http://sdm.link/zohodev2dev
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Mateusz Viste]

I might be missing the boat here, but what you describe vaguely look 
like a problem I had in some distant past, when I misconfigured my HDD 
in the BIOS.

Perhaps you could check whether your drive's geometry is 100% correct in 
your BIOS?

Mateusz




On 19/07/2016 07:12, Dimitris Zilaskos wrote:
> Hi,
>
> I was able to reinstall and boot successfully by performing an fdisk
> without FAT32 support, and creating a FAT16 2GB partition. At least with
> JEMM386, that is. So FAT32 support being the issue may be the case.
>
> Let me know if I can try anything else to confirm that.
>
> Cheers,
>
> Dimitris
>
> On Tue, Jul 19, 2016 at 6:03 AM, Dimitris Zilaskos  > wrote:
>
> Hi,
>
> On Tue, Jul 19, 2016 at 1:58 AM, Rugxulo  > wrote:
>
> Hi,
>
> On Mon, Jul 18, 2016 at 7:21 PM, Dimitris Zilaskos
> > wrote:
> >
> > Thank you for following up. fdisk reports that C: drive is already 
> active. I
> > did run mbrzap it completed successfully but there has been no 
> change,
> > system gets stuck right after BIOS summary table.
>
> What filesystem(s) are you using? FAT32, presumably. You said
> you had
> 4 GB and 6 GB HDDs, right?
>
> Sometimes it has been noticed that a FAT32 partition is created with
> plain type 0xB instead of 0xC (LBA), so you may have to change that.
>
> http://help.fdos.org/en/hhstndrd/base/fdisk.htm
>
> I'm not entirely sure what is most informative or useful here:
> "/STATUS"? "/XO"? "/SPEC"?
>
> Honestly, I think I just used BootMgr to change it:
>
> http://www.freedos.org/software/?prog=bootmgr
>
> (This may not be your problem, I'm just grasping at straws.)
>
>
>
> Indeed the partition type is 11. I have used fdisk to change that to
> 12 but there was no change. I did a re-installation after the change
> too.
>
> Cheers,
>
> Dimitris
>
>
>



--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,

I was able to reinstall and boot successfully by performing an fdisk
without FAT32 support, and creating a FAT16 2GB partition. At least with
JEMM386, that is. So FAT32 support being the issue may be the case.

Let me know if I can try anything else to confirm that.

Cheers,

Dimitris

On Tue, Jul 19, 2016 at 6:03 AM, Dimitris Zilaskos 
wrote:

> Hi,
>
> On Tue, Jul 19, 2016 at 1:58 AM, Rugxulo  wrote:
>
>> Hi,
>>
>> On Mon, Jul 18, 2016 at 7:21 PM, Dimitris Zilaskos 
>> wrote:
>> >
>> > Thank you for following up. fdisk reports that C: drive is already
>> active. I
>> > did run mbrzap it completed successfully but there has been no change,
>> > system gets stuck right after BIOS summary table.
>>
>> What filesystem(s) are you using? FAT32, presumably. You said you had
>> 4 GB and 6 GB HDDs, right?
>>
>> Sometimes it has been noticed that a FAT32 partition is created with
>> plain type 0xB instead of 0xC (LBA), so you may have to change that.
>>
>> http://help.fdos.org/en/hhstndrd/base/fdisk.htm
>>
>> I'm not entirely sure what is most informative or useful here:
>> "/STATUS"? "/XO"? "/SPEC"?
>>
>> Honestly, I think I just used BootMgr to change it:
>>
>> http://www.freedos.org/software/?prog=bootmgr
>>
>> (This may not be your problem, I'm just grasping at straws.)
>>
>>
>>
> Indeed the partition type is 11. I have used fdisk to change that to 12
> but there was no change. I did a re-installation after the change too.
>
> Cheers,
>
> Dimitris
>
>
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,

On Tue, Jul 19, 2016 at 1:58 AM, Rugxulo  wrote:

> Hi,
>
> On Mon, Jul 18, 2016 at 7:21 PM, Dimitris Zilaskos 
> wrote:
> >
> > Thank you for following up. fdisk reports that C: drive is already
> active. I
> > did run mbrzap it completed successfully but there has been no change,
> > system gets stuck right after BIOS summary table.
>
> What filesystem(s) are you using? FAT32, presumably. You said you had
> 4 GB and 6 GB HDDs, right?
>
> Sometimes it has been noticed that a FAT32 partition is created with
> plain type 0xB instead of 0xC (LBA), so you may have to change that.
>
> http://help.fdos.org/en/hhstndrd/base/fdisk.htm
>
> I'm not entirely sure what is most informative or useful here:
> "/STATUS"? "/XO"? "/SPEC"?
>
> Honestly, I think I just used BootMgr to change it:
>
> http://www.freedos.org/software/?prog=bootmgr
>
> (This may not be your problem, I'm just grasping at straws.)
>
>
>
Indeed the partition type is 11. I have used fdisk to change that to 12 but
there was no change. I did a re-installation after the change too.

Cheers,

Dimitris
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Rugxulo]

Hi,

On Mon, Jul 18, 2016 at 7:21 PM, Dimitris Zilaskos  wrote:
>
> Thank you for following up. fdisk reports that C: drive is already active. I
> did run mbrzap it completed successfully but there has been no change,
> system gets stuck right after BIOS summary table.

What filesystem(s) are you using? FAT32, presumably. You said you had
4 GB and 6 GB HDDs, right?

Sometimes it has been noticed that a FAT32 partition is created with
plain type 0xB instead of 0xC (LBA), so you may have to change that.

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

I'm not entirely sure what is most informative or useful here:
"/STATUS"? "/XO"? "/SPEC"?

Honestly, I think I just used BootMgr to change it:

http://www.freedos.org/software/?prog=bootmgr

(This may not be your problem, I'm just grasping at straws.)

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,

Thank you for following up. fdisk reports that C: drive is already active.
I did run mbrzap it completed successfully but there has been no change,
system gets stuck right after BIOS summary table.

Cheers,

Dimitris

On Tue, Jul 19, 2016 at 12:29 AM, Jerome Shidel  wrote:

>
>
> On Jul 18, 2016, at 6:52 PM, Dimitris Zilaskos 
> wrote:
>
> Dear Jerome,
>
> From what I can tell I never get past the boot loader to be struck by
> himemx.
>
>
> Ok try this:
>
> Boot your modified FDI floppy.
> It should detect FreeDOS has been already installed and go straight to the
> command prompt.
>
> Run "MBRZAP"
> This will launch a special part of FDI in advanced mode to force update
> your MBR with the FreeDOS boot loader.
>
> ---
> During investigations of systems that had boot loader issues not being
> updated, I discovered that there is no way to force the sys command to
> updated the MBR. Sometimes, it just won't do it regardless of what you tell
> it to do. It can be forced using fdisk.
>
> There is another possible issue. Your MBR may be fine. However, FDI may
> have not been able to identify the drive or partition that FreeDOS was
> installed onto. You should run fdisk and verify that the FreeDOS partition
> is set as ACTIVE.
>
> Jerome
>
> Sent from my iPhone, ignore bad sentence structures, grammatical errors
> and incorrect spell-corrected words.
>
> Cheers,
>
> Dimitris
>
> On Mon, Jul 18, 2016 at 10:49 PM, Jerome Shidel  wrote:
>
>> Did you change the installed config?
>>
>> It uses himemx as well.
>>
>> Sent from my iPhone, ignore bad sentence structures, grammatical errors
>> and incorrect spell-corrected words.
>>
>> On Jul 18, 2016, at 3:46 PM, Dimitris Zilaskos 
>> wrote:
>>
>> Thank you all for your suggestions. What I have tried so far:
>>
>>* Getting rid of himemx: this works - the boot process continues and
>> the installer tries to start. However the floppy drive works continuously
>> like mad, screen updates are slow, and I the installation appears to be
>> stuck in the 'Gathering information..' stage forever
>>* Replacing himemx with XMGR.SYS /T0 (kudos to Jack): Boot process
>> continues, everything is light speed fast compared to just getting rid of
>> himemx.
>>* Although installation of 1.2 finishes successfully, system fails to
>> boot, hangs right after BIOS system summary is displayed.
>>* sys c: does not help
>>* UDVD2 is able to detect the CDROM connected to the SB16 IDE
>> interface. Unfortunately only the CDROM drive that was supplied with sound
>> card appears to work there (MATSHITA CR-581-M), connecting other CDROMs
>> that can actually read modern CD-R causes the system to get stuck after
>> memory test. So I have to use a 1998 HITACHI CDR-8435 attached to the
>> secondary VESA Local Bus IDE for the installation. UDVD2 reports the SB16
>> CDROM drive in IDE1 - I would expect that to be IDE2 for tertiary IDE so I
>> may need to play with jumpers.
>>
>> I will try to sort out why the boot loader fails.
>>
>> Thanks!
>>
>> Dimitris
>>
>>
>> On Mon, Jul 18, 2016 at 5:04 PM, Don Flowers  wrote:
>>
>>> Your driver is the problem this might be a case for the XCDROM.SYS
>>> driver combined with SHCDX86.COM - A quick way to find out download
>>> this file
>>>
>>> https://sourceforge.net/projects/xosl-ow/files/xosl-ow116/BootMedia/BootFloppy/
>>> and see if you have clean drive access.
>>>
>>>
>>> On Mon, Jul 18, 2016 at 9:02 AM, Dimitris Zilaskos 
>>> wrote:
>>>
 Hi,

 Thanks for the followup. Hitting F8 reveals HIMEMX triggering this
 problem: https://drive.google.com/open?id=0B2zW1ur6Z_WeSWtGNXN0NmxxaU0

 ​​I have observed that the gibberish stops given sufficient time:
 https://drive.google.com/open?id=0B2zW1ur6Z_WeVjVMalF6M2YtMTA

 Let me know what else I can try - I will recheck the floppies for
 starters in case they went bad and check the rest of your suggestions.

 Best regards,

 Dimitris


 On Mon, Jul 18, 2016 at 1:02 PM, Jerome E. Shidel Jr. <
 jer...@shidel.net> wrote:

>
> On Jul 18, 2016, at 7:51 AM, Dimitris Zilaskos 
> wrote:
>
> I have tried it please see the output attached. This is endlessly
> scrolling after drives are detected.
>
>
> https://drive.google.com/open?id=0B2zW1ur6Z_WeY2tOSXpNT2g3NUJWMWx6bFZlSFBjamE3VEFr
>
> Unfortunately, that isn’t very helpful.
>
> When you boot the floppy, can you press F8 to walk through the
> startup?  What item in the configuration
> causes it to crash?
>
> Jerome
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and
> 

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,

fdisk /mbr:80 did not change anything. Here some BIOS screens:

https://drive.google.com/open?id=0B2zW1ur6Z_Wed09TVi1YY3VNR2s
https://drive.google.com/open?id=0B2zW1ur6Z_WeWDdxWXRrY2NpWEU
https://drive.google.com/open?id=0B2zW1ur6Z_WeQ3ctSS14Z1RINlk

Here is a video of the system booting from FreeDOS 1.2 floppy:

https://drive.google.com/open?id=0B2zW1ur6Z_WeTEtKU1kyNGp3SWc

Cheers,

Dimitris




On Mon, Jul 18, 2016 at 9:53 PM, Louis Santillan  wrote:

> Dimitris,
>
> For giggles, could you do two things?  First, capture the BIOS screens
> for booting and IDE/HD parameters.  Second, after installing FreeDOS
> to C: drive, run the command `fdisk /MBR:80`.
>
> On Mon, Jul 18, 2016 at 12:46 PM, Dimitris Zilaskos 
> wrote:
> > Thank you all for your suggestions. What I have tried so far:
> >
> >* Getting rid of himemx: this works - the boot process continues and
> the
> > installer tries to start. However the floppy drive works continuously
> like
> > mad, screen updates are slow, and I the installation appears to be stuck
> in
> > the 'Gathering information..' stage forever
> >* Replacing himemx with XMGR.SYS /T0 (kudos to Jack): Boot process
> > continues, everything is light speed fast compared to just getting rid of
> > himemx.
> >* Although installation of 1.2 finishes successfully, system fails to
> > boot, hangs right after BIOS system summary is displayed.
> >* sys c: does not help
> >* UDVD2 is able to detect the CDROM connected to the SB16 IDE
> interface.
> > Unfortunately only the CDROM drive that was supplied with sound card
> appears
> > to work there (MATSHITA CR-581-M), connecting other CDROMs that can
> actually
> > read modern CD-R causes the system to get stuck after memory test. So I
> have
> > to use a 1998 HITACHI CDR-8435 attached to the secondary VESA Local Bus
> IDE
> > for the installation. UDVD2 reports the SB16 CDROM drive in IDE1 - I
> would
> > expect that to be IDE2 for tertiary IDE so I may need to play with
> jumpers.
> >
> > I will try to sort out why the boot loader fails.
> >
> > Thanks!
> >
> > Dimitris
> >
> >
> > On Mon, Jul 18, 2016 at 5:04 PM, Don Flowers  wrote:
> >>
> >> Your driver is the problem this might be a case for the XCDROM.SYS
> driver
> >> combined with SHCDX86.COM - A quick way to find out download this file
> >>
> >>
> https://sourceforge.net/projects/xosl-ow/files/xosl-ow116/BootMedia/BootFloppy/
> >> and see if you have clean drive access.
> >>
> >>
> >> On Mon, Jul 18, 2016 at 9:02 AM, Dimitris Zilaskos  >
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> Thanks for the followup. Hitting F8 reveals HIMEMX triggering this
> >>> problem: https://drive.google.com/open?id=0B2zW1ur6Z_WeSWtGNXN0NmxxaU0
> >>>
> >>> I have observed that the gibberish stops given sufficient time:
> >>> https://drive.google.com/open?id=0B2zW1ur6Z_WeVjVMalF6M2YtMTA
> >>>
> >>> Let me know what else I can try - I will recheck the floppies for
> >>> starters in case they went bad and check the rest of your suggestions.
> >>>
> >>> Best regards,
> >>>
> >>> Dimitris
> >>>
> >>>
> >>> On Mon, Jul 18, 2016 at 1:02 PM, Jerome E. Shidel Jr. <
> jer...@shidel.net>
> >>> wrote:
> 
> 
>  On Jul 18, 2016, at 7:51 AM, Dimitris Zilaskos 
>  wrote:
> 
>  I have tried it please see the output attached. This is endlessly
>  scrolling after drives are detected.
> 
> 
> 
> https://drive.google.com/open?id=0B2zW1ur6Z_WeY2tOSXpNT2g3NUJWMWx6bFZlSFBjamE3VEFr
> 
>  Unfortunately, that isn’t very helpful.
> 
>  When you boot the floppy, can you press F8 to walk through the
> startup?
>  What item in the configuration
>  causes it to crash?
> 
>  Jerome
> 
> 
> 
> --
>  What NetFlow Analyzer can do for you? Monitors network bandwidth and
>  traffic
>  patterns at an interface-level. Reveals which users, apps, and
> protocols
>  are
>  consuming the most bandwidth. Provides multi-vendor support for
> NetFlow,
>  J-Flow, sFlow and other flows. Make informed decisions using capacity
>  planning
>  reports.http://sdm.link/zohodev2dev
>  ___
>  Freedos-user mailing list
>  Freedos-user@lists.sourceforge.net
>  https://lists.sourceforge.net/lists/listinfo/freedos-user
> 
> >>>
> >>>
> >>>
> >>>
> --
> >>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> >>> traffic
> >>> patterns at an interface-level. Reveals which users, apps, and
> protocols
> >>> are
> >>> consuming the most bandwidth. Provides multi-vendor support for
> NetFlow,
> >>> J-Flow, sFlow and other flows. Make informed decisions using capacity
> >>> planning
> >>> 

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,

On Mon, Jul 18, 2016 at 10:48 PM, Eric Auer  wrote:

>
> Hi Dimitris,
>
> > * Getting rid of himemx: this works ...
>
> But very slow and lots of floppy access: I assume you booted from
> floppy because the BIOS does not support CD boot and the CD also
> needs to be some ancient model connected to the sound card? Then
> I wonder if a newer model would work if connected to the normal
> IDE controller which your 486 must already have. Because then it
> may be possible to boot with a Smart Boot Manager floppy to CD...
> If you have questions about SBM, Rugxulo could probably help ;-)
>

Indeed! Your assumptions are correct. Getting SBM installed to a floppy was
tricky but I got it. However it does not detect any CDROM drives, no matter
if they are connected on the SB16 IDE or the VL Bus Secondary IDE. I
tried 1E0-1EFh I/O port range per
http://support.creative.com/kb/ShowArticle.aspx?sid=3039 and looking at the
SB16 jumpers but no luck.

>
> > * Replacing himemx with XMGR.SYS /T0 (kudos to Jack)
>
> Cool to know that XMGR works, but what does /T0 mean? Maybe there
> is some option for HIMEMX which makes a similar selection, which
> could make HIMEMX work as well? :-)
>

Jack told me /T0 helps with systems with less than 64MB RAM such as mine,

>
> > * Although installation of 1.2 finishes successfully, system fails
> > to boot, hangs right after BIOS system summary is displayed.
>
> I agree that FDISK /MBR may help. It would replace existing boot
> code in the MBR with a "normal" version. Note that if you have to
> use something like OnTrack "drivers" hidden in the MBR to use the
> full capacity of the harddisk (due to too old BIOS), then this can
> overwrite the driver: You might have to install DOS and/or driver
> again.
>

I tried it but nothing changed. I am not using any drives with OnTrack
connected atm - I do have some that I may use later.


>
> > * UDVD2 is able to detect the CDROM connected to the SB16 IDE interface.
>
> > Unfortunately only the CDROM drive that was supplied with sound
> > card appears to work there (MATSHITA CR-581-M)...
>
> See above :-)
>
> Cheers, Eric
>

This turned out to be a red herring, I was able to get all the CDROMS
detected by UDVD2 while both of them sitting on the SB16 IDE in
master/slave configuration. I suspect I did a mistake during my previous
test.

>
> PS: You may also have a way to change A20 style in BIOS setup,
> which can help HIMEMX and XMGR to work without magic options.
>

BIOS has a Fast and Normal setting for A20, it is currently set to Fast.
Will try Normal later.


Cheers,

Dimitris
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Dear Jerome,

>From what I can tell I never get past the boot loader to be struck by
himemx.

Cheers,

Dimitris

On Mon, Jul 18, 2016 at 10:49 PM, Jerome Shidel  wrote:

> Did you change the installed config?
>
> It uses himemx as well.
>
> Sent from my iPhone, ignore bad sentence structures, grammatical errors
> and incorrect spell-corrected words.
>
> On Jul 18, 2016, at 3:46 PM, Dimitris Zilaskos 
> wrote:
>
> Thank you all for your suggestions. What I have tried so far:
>
>* Getting rid of himemx: this works - the boot process continues and
> the installer tries to start. However the floppy drive works continuously
> like mad, screen updates are slow, and I the installation appears to be
> stuck in the 'Gathering information..' stage forever
>* Replacing himemx with XMGR.SYS /T0 (kudos to Jack): Boot process
> continues, everything is light speed fast compared to just getting rid of
> himemx.
>* Although installation of 1.2 finishes successfully, system fails to
> boot, hangs right after BIOS system summary is displayed.
>* sys c: does not help
>* UDVD2 is able to detect the CDROM connected to the SB16 IDE
> interface. Unfortunately only the CDROM drive that was supplied with sound
> card appears to work there (MATSHITA CR-581-M), connecting other CDROMs
> that can actually read modern CD-R causes the system to get stuck after
> memory test. So I have to use a 1998 HITACHI CDR-8435 attached to the
> secondary VESA Local Bus IDE for the installation. UDVD2 reports the SB16
> CDROM drive in IDE1 - I would expect that to be IDE2 for tertiary IDE so I
> may need to play with jumpers.
>
> I will try to sort out why the boot loader fails.
>
> Thanks!
>
> Dimitris
>
>
> On Mon, Jul 18, 2016 at 5:04 PM, Don Flowers  wrote:
>
>> Your driver is the problem this might be a case for the XCDROM.SYS driver
>> combined with SHCDX86.COM - A quick way to find out download this file
>>
>> https://sourceforge.net/projects/xosl-ow/files/xosl-ow116/BootMedia/BootFloppy/
>> and see if you have clean drive access.
>>
>>
>> On Mon, Jul 18, 2016 at 9:02 AM, Dimitris Zilaskos 
>> wrote:
>>
>>> Hi,
>>>
>>> Thanks for the followup. Hitting F8 reveals HIMEMX triggering this
>>> problem: https://drive.google.com/open?id=0B2zW1ur6Z_WeSWtGNXN0NmxxaU0
>>>
>>> ​​I have observed that the gibberish stops given sufficient time:
>>> https://drive.google.com/open?id=0B2zW1ur6Z_WeVjVMalF6M2YtMTA
>>>
>>> Let me know what else I can try - I will recheck the floppies for
>>> starters in case they went bad and check the rest of your suggestions.
>>>
>>> Best regards,
>>>
>>> Dimitris
>>>
>>>
>>> On Mon, Jul 18, 2016 at 1:02 PM, Jerome E. Shidel Jr. >> > wrote:
>>>

 On Jul 18, 2016, at 7:51 AM, Dimitris Zilaskos 
 wrote:

 I have tried it please see the output attached. This is endlessly
 scrolling after drives are detected.


 https://drive.google.com/open?id=0B2zW1ur6Z_WeY2tOSXpNT2g3NUJWMWx6bFZlSFBjamE3VEFr

 Unfortunately, that isn’t very helpful.

 When you boot the floppy, can you press F8 to walk through the
 startup?  What item in the configuration
 causes it to crash?

 Jerome


 --
 What NetFlow Analyzer can do for you? Monitors network bandwidth and
 traffic
 patterns at an interface-level. Reveals which users, apps, and
 protocols are
 consuming the most bandwidth. Provides multi-vendor support for NetFlow,
 J-Flow, sFlow and other flows. Make informed decisions using capacity
 planning
 reports.http://sdm.link/zohodev2dev
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


>>>
>>>
>>> --
>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>>> traffic
>>> patterns at an interface-level. Reveals which users, apps, and protocols
>>> are
>>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>>> planning
>>> reports.http://sdm.link/zohodev2dev
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>>>
>>
>>
>> --
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>> traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols
>> are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other 

Re: [Freedos-user] Which freedos on 486

[Jerome Shidel]

Did you change the installed config?

It uses himemx as well.

Sent from my iPhone, ignore bad sentence structures, grammatical errors and 
incorrect spell-corrected words. 

> On Jul 18, 2016, at 3:46 PM, Dimitris Zilaskos  wrote:
> 
> Thank you all for your suggestions. What I have tried so far:
> 
>* Getting rid of himemx: this works - the boot process continues and the 
> installer tries to start. However the floppy drive works continuously like 
> mad, screen updates are slow, and I the installation appears to be stuck in 
> the 'Gathering information..' stage forever
>* Replacing himemx with XMGR.SYS /T0 (kudos to Jack): Boot process 
> continues, everything is light speed fast compared to just getting rid of 
> himemx.
>* Although installation of 1.2 finishes successfully, system fails to 
> boot, hangs right after BIOS system summary is displayed.
>* sys c: does not help
>* UDVD2 is able to detect the CDROM connected to the SB16 IDE interface. 
> Unfortunately only the CDROM drive that was supplied with sound card appears 
> to work there (MATSHITA CR-581-M), connecting other CDROMs that can actually 
> read modern CD-R causes the system to get stuck after memory test. So I have 
> to use a 1998 HITACHI CDR-8435 attached to the secondary VESA Local Bus IDE 
> for the installation. UDVD2 reports the SB16 CDROM drive in IDE1 - I would 
> expect that to be IDE2 for tertiary IDE so I may need to play with jumpers.
> 
> I will try to sort out why the boot loader fails.
> 
> Thanks!
> 
> Dimitris
> 
> 
>> On Mon, Jul 18, 2016 at 5:04 PM, Don Flowers  wrote:
>> Your driver is the problem this might be a case for the XCDROM.SYS driver 
>> combined with SHCDX86.COM - A quick way to find out download this file 
>> https://sourceforge.net/projects/xosl-ow/files/xosl-ow116/BootMedia/BootFloppy/
>> and see if you have clean drive access.
>> 
>> 
>>> On Mon, Jul 18, 2016 at 9:02 AM, Dimitris Zilaskos  
>>> wrote:
>>> Hi,
>>> 
>>> Thanks for the followup. Hitting F8 reveals HIMEMX triggering this problem: 
>>> https://drive.google.com/open?id=0B2zW1ur6Z_WeSWtGNXN0NmxxaU0
>>> 
>>> ​​I have observed that the gibberish stops given sufficient time: 
>>> https://drive.google.com/open?id=0B2zW1ur6Z_WeVjVMalF6M2YtMTA
>>> 
>>> Let me know what else I can try - I will recheck the floppies for starters 
>>> in case they went bad and check the rest of your suggestions.
>>> 
>>> Best regards,
>>> 
>>> Dimitris
>>> 
>>> 
 On Mon, Jul 18, 2016 at 1:02 PM, Jerome E. Shidel Jr.  
 wrote:
 
> On Jul 18, 2016, at 7:51 AM, Dimitris Zilaskos  
> wrote:
> I have tried it please see the output attached. This is endlessly 
> scrolling after drives are detected. 
> 
> https://drive.google.com/open?id=0B2zW1ur6Z_WeY2tOSXpNT2g3NUJWMWx6bFZlSFBjamE3VEFr
 Unfortunately, that isn’t very helpful.
 
 When you boot the floppy, can you press F8 to walk through the startup?  
 What item in the configuration
 causes it to crash?
 
 Jerome
 
 --
 What NetFlow Analyzer can do for you? Monitors network bandwidth and 
 traffic
 patterns at an interface-level. Reveals which users, apps, and protocols 
 are
 consuming the most bandwidth. Provides multi-vendor support for NetFlow,
 J-Flow, sFlow and other flows. Make informed decisions using capacity 
 planning
 reports.http://sdm.link/zohodev2dev
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user
>>> 
>>> 
>>> --
>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
>>> patterns at an interface-level. Reveals which users, apps, and protocols are
>>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>>> J-Flow, sFlow and other flows. Make informed decisions using capacity 
>>> planning
>>> reports.http://sdm.link/zohodev2dev
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>> 
>> 
>> --
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity 
>> planning
>> reports.http://sdm.link/zohodev2dev
>> ___
>> Freedos-user mailing list
>> 

Re: [Freedos-user] Which freedos on 486

[Eric Auer]

Hi Dimitris,

> * Getting rid of himemx: this works ...

But very slow and lots of floppy access: I assume you booted from
floppy because the BIOS does not support CD boot and the CD also
needs to be some ancient model connected to the sound card? Then
I wonder if a newer model would work if connected to the normal
IDE controller which your 486 must already have. Because then it
may be possible to boot with a Smart Boot Manager floppy to CD...
If you have questions about SBM, Rugxulo could probably help ;-)

> * Replacing himemx with XMGR.SYS /T0 (kudos to Jack)

Cool to know that XMGR works, but what does /T0 mean? Maybe there
is some option for HIMEMX which makes a similar selection, which
could make HIMEMX work as well? :-)

> * Although installation of 1.2 finishes successfully, system fails
> to boot, hangs right after BIOS system summary is displayed.

I agree that FDISK /MBR may help. It would replace existing boot
code in the MBR with a "normal" version. Note that if you have to
use something like OnTrack "drivers" hidden in the MBR to use the
full capacity of the harddisk (due to too old BIOS), then this can
overwrite the driver: You might have to install DOS and/or driver
again.

> * UDVD2 is able to detect the CDROM connected to the SB16 IDE interface.

> Unfortunately only the CDROM drive that was supplied with sound
> card appears to work there (MATSHITA CR-581-M)...

See above :-)

Cheers, Eric

PS: You may also have a way to change A20 style in BIOS setup,
which can help HIMEMX and XMGR to work without magic options.



--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Louis Santillan]

Dimitris,

For giggles, could you do two things?  First, capture the BIOS screens
for booting and IDE/HD parameters.  Second, after installing FreeDOS
to C: drive, run the command `fdisk /MBR:80`.

On Mon, Jul 18, 2016 at 12:46 PM, Dimitris Zilaskos  wrote:
> Thank you all for your suggestions. What I have tried so far:
>
>* Getting rid of himemx: this works - the boot process continues and the
> installer tries to start. However the floppy drive works continuously like
> mad, screen updates are slow, and I the installation appears to be stuck in
> the 'Gathering information..' stage forever
>* Replacing himemx with XMGR.SYS /T0 (kudos to Jack): Boot process
> continues, everything is light speed fast compared to just getting rid of
> himemx.
>* Although installation of 1.2 finishes successfully, system fails to
> boot, hangs right after BIOS system summary is displayed.
>* sys c: does not help
>* UDVD2 is able to detect the CDROM connected to the SB16 IDE interface.
> Unfortunately only the CDROM drive that was supplied with sound card appears
> to work there (MATSHITA CR-581-M), connecting other CDROMs that can actually
> read modern CD-R causes the system to get stuck after memory test. So I have
> to use a 1998 HITACHI CDR-8435 attached to the secondary VESA Local Bus IDE
> for the installation. UDVD2 reports the SB16 CDROM drive in IDE1 - I would
> expect that to be IDE2 for tertiary IDE so I may need to play with jumpers.
>
> I will try to sort out why the boot loader fails.
>
> Thanks!
>
> Dimitris
>
>
> On Mon, Jul 18, 2016 at 5:04 PM, Don Flowers  wrote:
>>
>> Your driver is the problem this might be a case for the XCDROM.SYS driver
>> combined with SHCDX86.COM - A quick way to find out download this file
>>
>> https://sourceforge.net/projects/xosl-ow/files/xosl-ow116/BootMedia/BootFloppy/
>> and see if you have clean drive access.
>>
>>
>> On Mon, Jul 18, 2016 at 9:02 AM, Dimitris Zilaskos 
>> wrote:
>>>
>>> Hi,
>>>
>>> Thanks for the followup. Hitting F8 reveals HIMEMX triggering this
>>> problem: https://drive.google.com/open?id=0B2zW1ur6Z_WeSWtGNXN0NmxxaU0
>>>
>>> I have observed that the gibberish stops given sufficient time:
>>> https://drive.google.com/open?id=0B2zW1ur6Z_WeVjVMalF6M2YtMTA
>>>
>>> Let me know what else I can try - I will recheck the floppies for
>>> starters in case they went bad and check the rest of your suggestions.
>>>
>>> Best regards,
>>>
>>> Dimitris
>>>
>>>
>>> On Mon, Jul 18, 2016 at 1:02 PM, Jerome E. Shidel Jr. 
>>> wrote:


 On Jul 18, 2016, at 7:51 AM, Dimitris Zilaskos 
 wrote:

 I have tried it please see the output attached. This is endlessly
 scrolling after drives are detected.


 https://drive.google.com/open?id=0B2zW1ur6Z_WeY2tOSXpNT2g3NUJWMWx6bFZlSFBjamE3VEFr

 Unfortunately, that isn’t very helpful.

 When you boot the floppy, can you press F8 to walk through the startup?
 What item in the configuration
 causes it to crash?

 Jerome


 --
 What NetFlow Analyzer can do for you? Monitors network bandwidth and
 traffic
 patterns at an interface-level. Reveals which users, apps, and protocols
 are
 consuming the most bandwidth. Provides multi-vendor support for NetFlow,
 J-Flow, sFlow and other flows. Make informed decisions using capacity
 planning
 reports.http://sdm.link/zohodev2dev
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user

>>>
>>>
>>>
>>> --
>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>>> traffic
>>> patterns at an interface-level. Reveals which users, apps, and protocols
>>> are
>>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>>> planning
>>> reports.http://sdm.link/zohodev2dev
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>>
>>
>>
>> --
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>> traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols
>> are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning
>> reports.http://sdm.link/zohodev2dev
>> ___
>> Freedos-user mailing list
>> 

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Thank you all for your suggestions. What I have tried so far:

   * Getting rid of himemx: this works - the boot process continues and the
installer tries to start. However the floppy drive works continuously like
mad, screen updates are slow, and I the installation appears to be stuck in
the 'Gathering information..' stage forever
   * Replacing himemx with XMGR.SYS /T0 (kudos to Jack): Boot process
continues, everything is light speed fast compared to just getting rid of
himemx.
   * Although installation of 1.2 finishes successfully, system fails to
boot, hangs right after BIOS system summary is displayed.
   * sys c: does not help
   * UDVD2 is able to detect the CDROM connected to the SB16 IDE interface.
Unfortunately only the CDROM drive that was supplied with sound card
appears to work there (MATSHITA CR-581-M), connecting other CDROMs that can
actually read modern CD-R causes the system to get stuck after memory test.
So I have to use a 1998 HITACHI CDR-8435 attached to the secondary VESA
Local Bus IDE for the installation. UDVD2 reports the SB16 CDROM drive in
IDE1 - I would expect that to be IDE2 for tertiary IDE so I may need to
play with jumpers.

I will try to sort out why the boot loader fails.

Thanks!

Dimitris


On Mon, Jul 18, 2016 at 5:04 PM, Don Flowers  wrote:

> Your driver is the problem this might be a case for the XCDROM.SYS driver
> combined with SHCDX86.COM - A quick way to find out download this file
>
> https://sourceforge.net/projects/xosl-ow/files/xosl-ow116/BootMedia/BootFloppy/
> and see if you have clean drive access.
>
>
> On Mon, Jul 18, 2016 at 9:02 AM, Dimitris Zilaskos 
> wrote:
>
>> Hi,
>>
>> Thanks for the followup. Hitting F8 reveals HIMEMX triggering this
>> problem: https://drive.google.com/open?id=0B2zW1ur6Z_WeSWtGNXN0NmxxaU0
>>
>> ​​I have observed that the gibberish stops given sufficient time:
>> https://drive.google.com/open?id=0B2zW1ur6Z_WeVjVMalF6M2YtMTA
>>
>> Let me know what else I can try - I will recheck the floppies for
>> starters in case they went bad and check the rest of your suggestions.
>>
>> Best regards,
>>
>> Dimitris
>>
>>
>> On Mon, Jul 18, 2016 at 1:02 PM, Jerome E. Shidel Jr. 
>> wrote:
>>
>>>
>>> On Jul 18, 2016, at 7:51 AM, Dimitris Zilaskos 
>>> wrote:
>>>
>>> I have tried it please see the output attached. This is endlessly
>>> scrolling after drives are detected.
>>>
>>>
>>> https://drive.google.com/open?id=0B2zW1ur6Z_WeY2tOSXpNT2g3NUJWMWx6bFZlSFBjamE3VEFr
>>>
>>> Unfortunately, that isn’t very helpful.
>>>
>>> When you boot the floppy, can you press F8 to walk through the startup?
>>> What item in the configuration
>>> causes it to crash?
>>>
>>> Jerome
>>>
>>>
>>> --
>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>>> traffic
>>> patterns at an interface-level. Reveals which users, apps, and protocols
>>> are
>>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>>> planning
>>> reports.http://sdm.link/zohodev2dev
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>>>
>>
>>
>> --
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>> traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols
>> are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning
>> reports.http://sdm.link/zohodev2dev
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>>
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and 

Re: [Freedos-user] Which freedos on 486

[Don Flowers]

Your driver is the problem this might be a case for the XCDROM.SYS driver
combined with SHCDX86.COM - A quick way to find out download this file
https://sourceforge.net/projects/xosl-ow/files/xosl-ow116/BootMedia/BootFloppy/
and see if you have clean drive access.


On Mon, Jul 18, 2016 at 9:02 AM, Dimitris Zilaskos 
wrote:

> Hi,
>
> Thanks for the followup. Hitting F8 reveals HIMEMX triggering this
> problem: https://drive.google.com/open?id=0B2zW1ur6Z_WeSWtGNXN0NmxxaU0
>
> ​​I have observed that the gibberish stops given sufficient time:
> https://drive.google.com/open?id=0B2zW1ur6Z_WeVjVMalF6M2YtMTA
>
> Let me know what else I can try - I will recheck the floppies for starters
> in case they went bad and check the rest of your suggestions.
>
> Best regards,
>
> Dimitris
>
>
> On Mon, Jul 18, 2016 at 1:02 PM, Jerome E. Shidel Jr. 
> wrote:
>
>>
>> On Jul 18, 2016, at 7:51 AM, Dimitris Zilaskos 
>> wrote:
>>
>> I have tried it please see the output attached. This is endlessly
>> scrolling after drives are detected.
>>
>>
>> https://drive.google.com/open?id=0B2zW1ur6Z_WeY2tOSXpNT2g3NUJWMWx6bFZlSFBjamE3VEFr
>>
>> Unfortunately, that isn’t very helpful.
>>
>> When you boot the floppy, can you press F8 to walk through the startup?
>> What item in the configuration
>> causes it to crash?
>>
>> Jerome
>>
>>
>> --
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>> traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols
>> are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning
>> reports.http://sdm.link/zohodev2dev
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>>
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Jerome E. Shidel Jr.]

> On Jul 18, 2016, at 9:02 AM, Dimitris Zilaskos  > wrote:
> 
> Hi,
> 
> Thanks for the followup. Hitting F8 reveals HIMEMX triggering this problem: 
> https://drive.google.com/open?id=0B2zW1ur6Z_WeSWtGNXN0NmxxaU0 
> 
> 
> ​​I have observed that the gibberish stops given sufficient time: 
> https://drive.google.com/open?id=0B2zW1ur6Z_WeVjVMalF6M2YtMTA 
> 
> 
> Let me know what else I can try - I will recheck the floppies for starters in 
> case they went bad and check the rest of your suggestions.
> 
> Best regards,
> 
> Dimitris
> 

You could just try removing HIMEMX.SYS from the FDCONFIG.SYS file.

Also, remove the DOS=HIGH, DOS=UMB, DOSDATA=UMB.

Change SHELLHIGH to SHELL.

After doing all of that, see what happens. 

FDI needs very little memory to run. It only loads stuff HIGH so the boot media
could be used to run other (not included) diagnostic programs and recovery 
tools.

Jerome--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Rugxulo]

Hi again,

On Sun, Jul 17, 2016 at 7:21 PM, Dimitris Zilaskos  wrote:
>
> I am trying to install FreeDOS on my old 486.
>
> Versions 1.1 and 1.2 floppy bootdisks either hang on boot printing odd
> characters or will not detect the CDROM.

As mentioned, CD-ROM may not be well-supported by default. You may
have to find your own (legacy, proprietary, hardware-specific) DOS
driver elsewhere (on random third-party site). Unavoidable.

> System is a 486DX4-100, 32 MB RAM. VESA Local Bus controller with primary IDE
> loaded with 2 HDD - 6 GB and 4 GB, secondary IDE the CDROM. BIOS supports
> boot only from floppy and hdd.

Have you not tried Smart Boot Manager? It may let you boot from CD:

http://btmgr.sourceforge.net/about.html

> Is there a recommended strategy to get FreeDOS installed on such an ancient
> system? Did some research and tried several bootdisks that float around,
> nothing worked quite like FreeDOS 1.0.

Just FYI, there's nothing hugely special about FD 1.0, it's roughly
the same. If you want to swap out shell (FreeCOM 0.84-pre2 XMS_Swap)
or kernel (2036) for different versions, it might help (but might
not).

https://sourceforge.net/projects/freedos/files/

http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/kernel/
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/command/

Not sure why HIMEMX would be failing. Also not sure how to isolate
what is going on there. Well, I'm not maintainer anyways (not sure
there is one, actively anyways).

So here's an old floppy of mine, for comparison, yet another to try,
if you really want a different alternative:

https://sites.google.com/site/rugxulo/BARE_DOS.ZIP?attredirects=0
https://sites.google.com/site/rugxulo/bare_dos.txt?attredirects=0

To be honest, floppy doesn't get a lot of attention anymore, even from
me. I would also (maybe?) point you to others of mine, but they use
HIMEMX, and you'd have to manually modify it to avoid that, so that's
probably not a good suggestion right now.

BTW, do you know exactly which version of HimemX you're using here?
3.32, perhaps??? Latest is probably here, so it might be worth trying
instead (rare chance, but anyways):

https://sourceforge.net/projects/himemx/files/v3.34/himemx.zip/download

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Rugxulo]

Hi,

On Mon, Jul 18, 2016 at 8:02 AM, Dimitris Zilaskos  wrote:
>
> Thanks for the followup. Hitting F8 reveals HIMEMX triggering this problem:
>
> Let me know what else I can try - I will recheck the floppies for starters
> in case they went bad and check the rest of your suggestions.

Unless I'm reading it incorrectly, your picture indicates that your
machine has 32 MB of RAM. Is that correct?

In that case, since (strangely) HIMEMX doesn't appear to work on your
machine, you could use a different alternative (e.g. FDXMS or even
probably FDXMS286).

1). https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/xms/fdxms/
2). https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/xms/fdxms286/

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Dimitris Zilaskos]

Hi,

Thanks for the followup. Hitting F8 reveals HIMEMX triggering this problem:
https://drive.google.com/open?id=0B2zW1ur6Z_WeSWtGNXN0NmxxaU0

​​I have observed that the gibberish stops given sufficient time:
https://drive.google.com/open?id=0B2zW1ur6Z_WeVjVMalF6M2YtMTA

Let me know what else I can try - I will recheck the floppies for starters
in case they went bad and check the rest of your suggestions.

Best regards,

Dimitris


On Mon, Jul 18, 2016 at 1:02 PM, Jerome E. Shidel Jr. 
wrote:

>
> On Jul 18, 2016, at 7:51 AM, Dimitris Zilaskos 
> wrote:
>
> I have tried it please see the output attached. This is endlessly
> scrolling after drives are detected.
>
>
> https://drive.google.com/open?id=0B2zW1ur6Z_WeY2tOSXpNT2g3NUJWMWx6bFZlSFBjamE3VEFr
>
> Unfortunately, that isn’t very helpful.
>
> When you boot the floppy, can you press F8 to walk through the startup?
> What item in the configuration
> causes it to crash?
>
> Jerome
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Jerome E. Shidel Jr.]

> On Jul 18, 2016, at 7:51 AM, Dimitris Zilaskos  > wrote:
> I have tried it please see the output attached. This is endlessly scrolling 
> after drives are detected. 
> 
> https://drive.google.com/open?id=0B2zW1ur6Z_WeY2tOSXpNT2g3NUJWMWx6bFZlSFBjamE3VEFr
>  
> 
Unfortunately, that isn’t very helpful.

When you boot the floppy, can you press F8 to walk through the startup?  What 
item in the configuration
causes it to crash?

Jerome--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Jerome E. Shidel Jr.]

One more thing,

> On Jul 18, 2016, at 2:34 AM, Louis Santillan  wrote:
> [...]
> Install FD 1.2 beta.  `sys c:` at the end of your install.

I don’t think you need to do the ‘sys c:’ at the end of the install anymore.
It shouldn’t hurt anything if you do run it.

Now, on the other hand. If the installed system does not boot after 
installation, there is simple batch file included that will run FDI with
a special option. This will tell FDI that you have already installed
FreeDOS and it wouldn’t boot. FDI will then offer some advanced
mode options to FORCE new boot sector code. This will wipe out
any multi-boot boot loader (like GRUB) and install the FreeDOS
boot sector.

You can try this utility by booting one of the FDI install media images.
Then run MBRZAP.BAT from the command line.

Jerome
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Jerome E. Shidel Jr.]

> On Jul 18, 2016, at 2:34 AM, Louis Santillan  wrote:
> 
> On Sun, Jul 17, 2016 at 5:21 PM, Dimitris Zilaskos  
> wrote:
> 
> […]
> 
>> Is there a recommended strategy to get FreeDOS installed on such an ancient
>> system? Did some research and tried several bootdisks that float around,
>> nothing worked quite like FreeDOS 1.0.
> 
> If you're willing to test FDI 1.2, download the beta boot floppy [0],
> and the cdrom iso [1].  Make sure the boot floppy can recognize your
> two hard drives and your CD-ROM.  Add drivers and edit
> autoexec.bat/fdconfig.sys as necessary (especially wrt to ensuring
> CD-ROM access).  Install FD 1.2 beta.  `sys c:` at the end of your
> install.
> 
> [0] http://dnld.lod.bz/FDI-2016-07-17-0.pre.zip 
> [1] 
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/cdrom.iso
>  
> 

Louis is correct. Once you get the FDI 1.2 Preview floppy to boot and access 
your CD-ROM,
you should be able to run the installer. If the included driver (UDVD2) does 
not work with your
drive, you to hunt down an alternate driver or even vendor specific driver for 
your hardware.
There are a couple of other drivers in the old FreeDOS 1.1 Repository. These 
have been
removed from version 1.2 for various reasons. But, you could try UIDE [2], 
XCDROM [3] or
GCDROM [4]. 

If you have a functioning non-FreeDOS boot disk (like MS-DOS 5) that can access 
your
CD-ROM, you could try booting it and then sticking in the FDI floppy and CD. 
Then manually
run the SETUP.BAT. Assuming that works, you would have problems when you reboot 
the
installed system. 

If everything else fails, you could try the the spare disk install method. It 
is mentioned in the
FDI Readme [5]. More or less, you copy everything from one of the USB images to 
a spare
hard drive root directory using another computer. The put that drive in the 
computer where you
want to install FreeDOS and run the SETUP.BAT. The spare drive should NOT be 
the drive
where you want to install FreeDOS. Normally, FDI will not permit you to install 
from and to 
the same drive. Trying to override this behavior using FDI in advanced mode is 
NOT 
recommended and can cause very unpredictable results.

Just a note on the 1.2 Repository CD-ROM [1]. Building the CD can place a heavy 
load on 
the server for several minutes. So, when packages in the 1.2 repo are updated, 
building
of this image is postponed until the end of the day. This process is completely 
automated
and is self maintaining. When packages have changed, a new repo CD will be 
automatically
created and be posted at approximately 0300-0315 EST the next morning. 
Generally, this
image is not updated at release time. But, it takes care of itself within 24 
hours.

There are static CD [6], SLIM [7], USB [8]  and Latest Floppy [9] that are 
created at release time.
these are also available on ibiblio [10]. The packages on these images are not 
updated
once a Preview or Release is issued. 

All released versions use the same version of FDI. However, the booted system 
configuration 
can vary slightly. The biggest difference is the Floppy image. Unlike the 
others, it loads
disk caching software at startup to increase the performance when running FDI 
from a 
real floppy drive. FDI itself is unchanged from one format to another. 

So, for instance, you could pull the BOOT.IMG from RepoCD [1]. Write it to a 
real floppy disk.
Grab the SLIM USB [7] image and write it to a USB stick. Then boot the floppy 
and either
just let FDI run. Or, exit FDI. Switch to the USB stick. Remove the Floppy, 
Then run 
SETUP.BAT. The result should be the same. (Although, FDI does a couple things 
differently when you run it manually.)

[2] 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/util/uide.zip
 

[3] 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/util/xcdrom.zip
 

[4] 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/util/gcdrom.zip
 

[5] https://github.com/shidel/FDI/blob/master/README.md 
 or 
http://dnld.lod.bz/FDI-README.md 
[6] http://dnld.lod.bz/FDI-CD.iso  
[7] http://dnld.lod.bz/FDI-SLIM.zip  
[8] http://dnld.lod.bz/FDI-USB.zip  
[9] http://up.lod.bz/FDI/latest  
[10] 

Re: [Freedos-user] Which freedos on 486

[Louis Santillan]

On Sun, Jul 17, 2016 at 5:21 PM, Dimitris Zilaskos  wrote:
> Hi,
>
> I am trying to install FreeDOS on my old 486. Version 1.0 will boot from
> floppy (only with himem, emm3886 with crash), detect CDROM drive (only if
> connected on Vesa Local bus controller, not on SB16 IDE - tertiary ide IDE

It is likely that you'll require you sound card manufacturer's CDROM
driver to have it recognize the IDE channel there.  The VLB card is
likely recognized natively by the BIOS and/or registering itself in
such a way that its channels are "natively" available to the BIOS.

> channel) , and install happily. However upon reboot it just hangs , without
> printing anything.

Are you sys'ing the C: drive after install?  Run `sys c:` after the
install program.

>
>
> Versions 1.1 and 1.2 floppy bootdisks either hang on boot printing odd
> characters or will not detect the CDROM.

Which specific bootdisks do what?

>
> System is a 486DX4-100, 32 MB RAM.VESA Local Bus controller with primary IDE
> loaded with 2 HDD - 6 GB and 4 GB, secondary IDE the CDROM. BIOS supports
> boot only from floppy and hdd. SB16 CT2290 used to handle the CDROM drive
> via its IDE interface - now I moved the CDROM drive to the VESA card.
> Windows 98SE happily gets installed and works on this system.
>

Win98SE has much more capable HW detection & driver routines.  FreeDOS
(like all DOSes) depends on the BIOS and whatevers you supply it.

> Is there a recommended strategy to get FreeDOS installed on such an ancient
> system? Did some research and tried several bootdisks that float around,
> nothing worked quite like FreeDOS 1.0.

If you're willing to test FDI 1.2, download the beta boot floppy [0],
and the cdrom iso [1].  Make sure the boot floppy can recognize your
two hard drives and your CD-ROM.  Add drivers and edit
autoexec.bat/fdconfig.sys as necessary (especially wrt to ensuring
CD-ROM access).  Install FD 1.2 beta.  `sys c:` at the end of your
install.

[0] http://dnld.lod.bz/FDI-2016-07-17-0.pre.zip
[1] 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/cdrom.iso

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] which open source libraries work?

[dos386]

 Just wondering what Open Source libraries in the graphics/multimedia/audio

GFX: DUGL ( :-) DGJPP), ALLEGRO (buggy, dead, DGJPP), FB-GFX (limited,
some bugs left)

AUDIO: nothing, Allegro (dead, ISA sound cards only), DUGL (sound
support not yet (?) implemented)

MM: APEG (Allegro addon, YES, the player + encoder compiled by Khusraw
do work mostly)

 I read programs with SDL library work in some cases with HX Extender.

YES :-)

 Am assuming SDL doesn't build on its own in djgpp or a similar C/C++ compiler 
 for DOS

Feel free to try.

 about WxUniversal (a port of WxWindows using MGL).

AKA wxwidgets ???

 Any other cross-platform GUI or screen libraries that have a DOS port out 
 there?

cross-platform is equivalent to DOS support dead. Also, DOS
problems to solve:
- No usable mouse driver standard
- Buggy/hacky compiler ports only, no good DOS HLL compiler

 Is there a good C/C++ audio library to use with programs?

There is nothing (feel free to prove me wrong). Also, if you are a C
programmer (I am not), check MPXPLAY - it does have very good
sound code in.





-- 
~~~ wow ~~~

--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] which drive is my usb thumbdrive?

[Florian Xaver]

Hi,

which computer do you have? First you should look at your BIOS if  
USB-support is already present.If it isn't make a update of the BIOS.
Most new BIOSes support it (mostly disabled) and mappe USB-Stick to  
a:\ and handle USB-hard-discs like an ordinary hard disc.

If there isn't an BIOS update, ask again. I used DUSE (google...) and  
where lucky, but there is also another solution.

Bye
  Flo

On Fri, 05 Jan 2007 23:05:23 +0100, [EMAIL PROTECTED] wrote:

 Hi all,

 New to the list and new to freedos.  It's been years since I've used
 DOS, so I was hoping someone could direct me on how to:

 - load the driver for usb-storage devices
 - discover which drive represents the usb device
 - format it to be bootable

 thanks for your help,

 Dan

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



-- 
Florian Xaver

http://www.flox.at.tf oZone GUI, private homepage
Dr-DOS  http://www.drdos.org

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