Re: [Freedos-user] Which freedos on 486

:31 PM, Dimitris Zilaskos <dimitr...@gmail.com> 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 <e.a...@jpberlin.de> wrote: > >> >> Hi Dim

Re: [Freedos-user] Which freedos on 486

Hi, On Wed, Jul 20, 2016 at 9:50 PM, Jerome E. Shidel Jr. <jer...@shidel.net> wrote: > On Jul 20, 2016, at 12:56 PM, Dimitris Zilaskos <dimitr...@gmail.com> > wrote: > […] > > Dimitris > > > I have a few silly questions. > > You have verified the dri

Re: [Freedos-user] Which freedos on 486

. Shidel Jr. <jer...@shidel.net> wrote: > > On Jul 20, 2016, at 5:23 PM, Dimitris Zilaskos <dimitr...@gmail.com> > wrote: > > Hi, > > On Wed, Jul 20, 2016 at 9:50 PM, Jerome E. Shidel Jr. <jer...@shidel.net> > wrote: > >> On Jul 20, 2016,

Re: [Freedos-user] Which freedos on 486

Hi, On Wed, Jul 20, 2016 at 7:56 PM, <perditi...@gmail.com> wrote: > On Jul 20, 2016 12:57 PM, "Dimitris Zilaskos" <dimitr...@gmail.com> wrote: > > > > Hi > > > > > > > Since I now have a bootable C: drive, can't we just comp

Re: [Freedos-user] Which freedos on 486

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,

Re: [Freedos-user] Which freedos on 486

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

Re: [Freedos-user] Which freedos on 486

://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 <dimitr...@gmail.com> > wrote: > >> Hi, >> >> Thanks for the followup.

[Freedos-user] Which freedos on 486

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 channel) , and install happily. However upon reboot it just hangs ,

Re: [Freedos-user] Which freedos on 486

, Jul 19, 2016 at 6:03 AM, Dimitris Zilaskos <dimitr...@gmail.com> wrote: > Hi, > > On Tue, Jul 19, 2016 at 1:58 AM, Rugxulo <rugx...@gmail.com> wrote: > >> Hi, >> >> On Mon, Jul 18, 2016 at 7:21 PM, Dimitris Zilaskos <dimitr...@gmail.com> >&

Re: [Freedos-user] Which freedos on 486

wrote: > > > On Jul 18, 2016, at 6:52 PM, Dimitris Zilaskos <dimitr...@gmail.com> > 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. > I

Re: [Freedos-user] Which freedos on 486

Hi, On Tue, Jul 19, 2016 at 1:58 AM, Rugxulo <rugx...@gmail.com> wrote: > Hi, > > On Mon, Jul 18, 2016 at 7:21 PM, Dimitris Zilaskos <dimitr...@gmail.com> > wrote: > > > > Thank you for following up. fdisk reports that C: drive is already > active. I >

Re: [Freedos-user] Which freedos on 486

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 <dimitr...@gmail.com> > wrote: > > Thank you all for your suggestions. What I have tried so far: >

Re: [Freedos-user] Which freedos on 486

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

Re: [Freedos-user] Which freedos on 486

haps 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

Re: [Freedos-user] Which freedos on 486

om my iPhone, ignore bad sentence structures, grammatical errors > and incorrect spell-corrected words. > > On Jul 18, 2016, at 3:46 PM, Dimitris Zilaskos <dimitr...@gmail.com> > wrote: > > Thank you all for your suggestions. What I have tried so far: > >* Getting

Re: [Freedos-user] Which freedos on 486

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

Re: [Freedos-user] Which freedos on 486

Cheers, Dimitris On Wed, Jul 20, 2016 at 12:04 AM, Rugxulo <rugx...@gmail.com> wrote: > Hi, > > On Tue, Jul 19, 2016 at 8:26 AM, Dimitris Zilaskos <dimitr...@gmail.com> > wrote: > > > > I have LBA configured in the BIOS for the hard drives, mostly because i

Re: [Freedos-user] Which freedos on 486

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

Re: [Freedos-user] Which freedos on 486

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

Re: [Freedos-user] Which freedos on 486

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

[Freedos-user] Fwd: Which freedos on 486

Re-sending this as the attachment is caught up in moderation. -- Forwarded message -- From: Dimitris Zilaskos <dimitr...@gmail.com> Date: Mon, Jul 18, 2016 at 11:36 AM Subject: Re: [Freedos-user] Which freedos on 486 To: "Discussion and general questions about FreeDOS.

Re: [Freedos-user] freedos 1.2 archivers

Ok thanks. Would be awesome to have an option to get them installed. Cheers, Dimitris On Tue, Aug 16, 2016 at 5:52 PM, Jerome Shidel <jer...@shidel.net> wrote: > Hello, > > > On Aug 16, 2016, at 11:38 AM, Dimitris Zilaskos <dimitr...@gmail.com> > wrote: > > >

Re: [Freedos-user] freedos 1.2 archivers

with FULL/ALL), you can browse > through and select packages to be installed. Similar to using some Linux > package browsing systems like Yast. FDIMPLES does not do networking at > present. So, you will need to have you CD inserted. > > Jerome > > On Aug 16, 2016, at 7:01 PM,

Re: [Freedos-user] freedos 1.2 archivers

Thank you for your replies. I think I must had the wrong cd inserted, because now I can see all the packages as expected. Sorry for the confusion! Cheers, Dimitris On Fri, Aug 19, 2016 at 1:36 AM, Rugxulo <rugx...@gmail.com> wrote: > Hi, > > On Thu, Aug 18, 2016 at 5:46 PM, Di

[Freedos-user] freedos 1.2 archivers

Hi, I did a full freedos 1.2 installation but not all archivers were installed. While I got them from the CD eventually from the ARCHIVERS directory I was wondering if that is supposed to happen. Best regards, Dimitris

[Freedos-user] dma crosses 64k boundary error

Hi, I keep getting the error dma crosses 64k boundary when using tools like rawrite3 or hard drive manufacturers tools floppy creation software. I need to boot from Windows 98 bootdisk to get rid of it. Please let me know if there is a way to get rid of this problem under FreeDOS. Cheers,

Re: [Freedos-user] dma crosses 64k boundary error

they are executables around 1.44 MB I suspect they are just too big for LH to work with them. Cheers, Dimitris On Tue, Aug 23, 2016 at 10:56 PM, Dimitris Zilaskos <dimitr...@gmail.com> wrote: > Hi, > > rawrite1 also works. Problem is tools from maxtor/western digital/seaga

Re: [Freedos-user] dma crosses 64k boundary error

Hi, Hi, Thank you for your reply. Hardware is a year 1995 486-DX4 100, hardly remarkable at its time. Cheers, Dimitris On Tue, Aug 23, 2016 at 6:28 PM, Tom Ehlert wrote: > > I keep getting the error dma crosses 64k boundary when using tools > > like rawrite3 or hard

Re: [Freedos-user] Which freedos on 486

p! Cheers, Dimitris On Tue, Aug 9, 2016 at 10:51 PM, TJ Edmister <damag...@hyakushiki.net> wrote: > On Tue, 09 Aug 2016 13:57:35 -0400, Dimitris Zilaskos > <dimitr...@gmail.com> wrote: > > > The issue I am facing now is that the mechanical drives I connected to > &g

Re: [Freedos-user] dma cr

From: Dimitris Zilaskos <dimitr...@gmail.com> --===7567637663601894498== Content-Type: multipart/alternative; boundary=001a114013c0cba44c053ac0e9fc --001a114013c0cba44c053ac0e9fc Content-Type: text/plain; charset=UTF-8 Hi, Hi, Thank you for your reply. Hardware is a year 19

Re: [Freedos-user] Which

From: Dimitris Zilaskos <dimitr...@gmail.com> --===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

Re: [Freedos-user] dma cr

From: Dimitris Zilaskos <dimitr...@gmail.com> --===3972634112440227579== Content-Type: multipart/alternative; boundary=001a113f201c552d2b053ac43b1a --001a113f201c552d2b053ac43b1a Content-Type: text/plain; charset=UTF-8 Hi, rawrite1 also works. Problem is tools from maxtor/w

Re: [Freedos-user] Which

From: Dimitris Zilaskos <dimitr...@gmail.com> --===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 to

Re: [Freedos-user] freedo

From: Dimitris Zilaskos <dimitr...@gmail.com> --===6441216991813819129== Content-Type: multipart/alternative; boundary=001a114013c0e837f6053a385540 --001a114013c0e837f6053a385540 Content-Type: text/plain; charset=UTF-8 Ok thanks. Would be awesome to have an option to ge

Re: [Freedos-user] freedo

From: Dimitris Zilaskos <dimitr...@gmail.com> --===4049000903152666126== Content-Type: multipart/alternative; boundary=001a114004b64325ba053a605bd1 --001a114004b64325ba053a605bd1 Content-Type: text/plain; charset=UTF-8 Hi, Thank you for the advice. I tried FDIMPLES, seem t

Re: [Freedos-user] freedo

From: Dimitris Zilaskos <dimitr...@gmail.com> --===2905593142841686751== Content-Type: multipart/alternative; boundary=001a114b0aa08b4740053a6228e0 --001a114b0aa08b4740053a6228e0 Content-Type: text/plain; charset=UTF-8 Thank you for your replies. I think I must had the wr

[Freedos-user] dma crosse

From: Dimitris Zilaskos <dimitr...@gmail.com> --===2004488960791693994== Content-Type: multipart/alternative; boundary=001a11402ebefae056053a86f6a3 --001a11402ebefae056053a86f6a3 Content-Type: text/plain; charset=UTF-8 Hi, I keep getting the error dma crosses 64k boundar

[Freedos-user] freedos 1.

From: Dimitris Zilaskos <dimitr...@gmail.com> --===7160934022374945973== Content-Type: multipart/alternative; boundary=001a113f201cec7e0e053a3222e4 --001a113f201cec7e0e053a3222e4 Content-Type: text/plain; charset=UTF-8 Hi, I did a full freedos 1.2 installation but not all arc

Re: [Freedos-user] Some driver updates

done faster and smoother, allowing for more time to be spend for example looking for parts in friends' basements. Cheers, Dimitris On Sat, Nov 4, 2017 at 11:58 AM, <userbeit...@abwesend.de> wrote: > Hi! > > On 2017-11-04, 11:41, Dimitris Zilaskos wrote: > >> Hi, >>

Re: [Freedos-user] Some driver updates

2017 at 7:17 PM, Dimitris Zilaskos <dimitr...@gmail.com> > wrote: > > > > the wishes of the owners of the respective intellectual property have to > be respected. > > Personal opinion does not invalidate the law, and a so-called license > is only valid if it does

Re: [Freedos-user] Some driver updates

Hi, Jack's drivers are required on a number of dos-era systems else FreeDOS will not even install/boot. Being unable to use FreeDOS is annoying but a working system is needed and the wishes of the owners of the respective intellectual property have to be respected. Cheers, Dimitris On Fri, Nov