Re: [Freedos-user] Which freedos on 486

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 B

Re: [Freedos-user] Which freedos on 486

Somebody correct me if I'm wrong, but I think FreeDOS (all DOSes?) depends on an LBA/EDD capable BIOS when using FAT32 [0][1]. It could be you have a drive and/or BIOS with buggy/incomplete/incompatible/non-existent LBA/EDD implementations. Being your computer is 486-based, that is very much a pos

Re: [Freedos-user] Which freedos on 486

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:

Re: [Freedos-user] Which freedos on 486

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,

Re: [Freedos-user] Which freedos on 486

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

Re: [Freedos-user] Hello again (just introducing)

Hi, On Sun, Jul 17, 2016 at 3:40 PM, Marti van Lin wrote: > > Just re-introducing my self. > > I have been part of this mailing list before, using FreeDOS on bare metal. > > Now I'm testing 1.2 Pre-something on VirtualBox. > > 1.2 looks pretty promising so far, yet I have a lot of questions. > >

Re: [Freedos-user] Which freedos on 486

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 u

Re: [Freedos-user] Which freedos on 486

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

Re: [Freedos-user] Which freedos on 486

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

Re: [Freedos-user] Which freedos on 486

> 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

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 ancient model connecte

Re: [Freedos-user] Which freedos on 486

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

Re: [Freedos-user] Which freedos on 486

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:

Re: [Freedos-user] Which freedos on 486

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 conne

Re: [Freedos-user] Which freedos on 486

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

Re: [Freedos-user] Which freedos on 486

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

Re: [Freedos-user] Which freedos on 486

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,

Re: [Freedos-user] Which freedos on 486

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

Re: [Freedos-user] Which freedos on 486

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

Re: [Freedos-user] Which freedos on 486

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

Re: [Freedos-user] Which freedos on 486

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 ca

Re: [Freedos-user] Which freedos on 486

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

Re: [Freedos-user] Which freedos on 486

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 ins

[Freedos-user] Fwd: Which freedos on 486

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

Re: [Freedos-user] Which freedos on 486

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