On 20-04-23 08 h 03, Ludovico Giorio wrote:
I checked, and the installer can only see my usb, not the hdd inside
the laptop.
Message is:
"SETUP wasn't able to locate any disks to install FreeDOS 1.1 from."
What am I doing wrong?
I enabled legacy support in Bios.
I formatted my hdd in Fat.
Hi! There is no need to use Linux to replace the MBR boot code,
you can easily do that with DOS tools. Of course if you prefer
Linux tools, they can be used for the same purpose :-)
I assume you want to get rid of Windows, so you do not need to
convert from GPT to MBR. Deleting the partitions an
If GPT is the issue, should a Linux based tool be used to get around
that? I'm thinking something like boot nuke or something similar.
April 23, 2020 8:16 AM, "Eric Auer" wrote:
> Hi! Which tools in which versions did you use?
>
> For example which FORMAT, FDISK...? Let me start by
> saying th
Hi! Which tools in which versions did you use?
For example which FORMAT, FDISK...? Let me start by
saying the choice for MBR was good: GPT partitions
are not visible for DOS. Not sure what the purpose
of that EFI partition is, but it is easily possible
that Windows had a boot loader on the first
What kind of hard drive did you take out? Was it a serial ATA hard drive or an
IDE hard drive?
Have you considered trying Freedos 1.3 RC2?
Make sure you aren't in AHCI mode?
April 23, 2020 7:03 AM, "Ludovico Giorio" mailto:ludovico8...@hotmail.it?to=%22Ludovico%20Giorio%22%20)>
wrote:
Hello e
Hi Arkady,
Sorry, she downloaded the SR9 beta2 ISO and got MCB Chain corrupt, I
told her to try Odin 0.6, well it solve the problem.
The Kernel should be 2035a-unstable.
Rgds,
Johnson.
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
On Thu, 15 Jun 2006 05:48:54 +0400, you wrote:
Hi,
> Not enough information: which config.sys and autoexec.bat content on
>those disk? After which statement in config.sys you get this message (what
>you see on screen before this message)? Which kernel and FreeCOM version you
>use (do you get
Candidate for kernel bug of the month perhaps? some underlying malloc()
call that way prog handles memory block integrity of the structures and
become damaged. Step through config.sys/autoexec.bat to see the bad wolf
and remove it..
--chris
Arkady V.Belousov wrote:
>Hi!
>
>5-Июн-2006 11:48 [E
Hi!
5-Июн-2006 11:48 [EMAIL PROTECTED] (cherry chien) wrote to
:
cc> After reboot from 2G-harddisk
cc> Invalid Opcode at 2A18 0EB4 0613 03F2 .
cc> dos mem corrupt, first_mcb=
cc> prev :|1C 12 CF 00 DF 11 CF 00 C3 E2 00 F0 DF 11 Cf 00
cc> notMZ:|1C 12 CF 00 DF 11 CF 00 C3 E
At 02:07 PM 3/25/2006 -0600, I wrote:
As an alternate choice, you might try locating the actual problem, which
likely is not within EMM386 itself, rather than telling people to use
obsolete versions of software which won't fix the underlying problem and
which fail to provide a full range of mac
At 10:55 PM 3/21/2006 +, FreeDOS Ankreuzen wrote:
Yes on some mainbords PC s with PENTIUM II, there is a problem
to install FDOS BETA 9SR2 from CD.
If it s possibel use a Bootdisk with old FreeDOS Version
and pre-install FreeDOS manually.
Please tell me if you are using a Pentium II or whic
I am not using a PII. I am using an Abit KD7E with an AMD Athlon xp
1800 and sr2 won't install. sr1 and several previous releases work.
Jeff
On Tuesday 21 March 2006 22:55, FreeDOS Ankreuzen wrote:
> Yes on some mainbords PC s with PENTIUM II, there is a problem
> to install FDOS BETA 9SR2 from C
Yes on some mainbords PC s with PENTIUM II, there is a problem
to install FDOS BETA 9SR2 from CD.
If it s possibel use a Bootdisk with old FreeDOS Version
and pre-install FreeDOS manually.
Please tell me if you are using a Pentium II or which Mainboard
it is. I ve this problem with a pentium II
[EMAIL PROTECTED] wrote:
I finally figured out what you mean by sr#1
I looked all over the Free DOS website for a download of Service
Release # 1
Can't find a download for this Release
Do you see a download posted anywhere for Service Release # 1 ???
Thank you in advance for looking
h
ftp://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/old/beta9sr1/
On Thursday 23 March 2006 05:03, [EMAIL PROTECTED] wrote:
> I finally figured out what you mean by sr#1
>
> I looked all over the Free DOS website for a download of Service
> Release # 1
>
> Can't find a download
I finally figured out what you mean by sr#1
I looked all over the Free DOS website for a download of Service Release #
1
Can't find a download for this Release
Do you see a download posted anywhere for Service Release #
1 ???
Thank you in advance for looking
I saw your suggestion posted before and I have already tried doing
that
No luck
What is sr#1 ??
Same thing exactly going on here. Many others experiencing
the same results. Something is wrong with sr #2. Try this, I haven't
yet:
Hi, it could be the case that the nlsfunc interaction is what
crashes for you (nlsfunc/display/mode/devel-kernel). Try if it
helps to skip loading nlsfunc (hit f8 a
I ve got the same errors with freedos beta 9SR2
invalid opcodes
messages and the installation stopped
First
I have build a new freedos bootdisk, from my collected files.
I have bought a 400 Mhz PC. Installation of FreeDOS
with Emm386 2.08 , Kernel 2035b-csv works without any
problems. It s
Here is a suggestion that you could try to fix the installation
problem. I haven't had a chance to try it myself:
Hi, it could be the case that the nlsfunc interaction is what
crashes for you (nlsfunc/display/mode/devel-kernel). Try if it
helps to skip loading nlsfunc (hit f8 at boot, then you are
This may be true on your pc, however, I have successfully
installed the last several versions on my pc (since pre release 4
I think) and not a single thing has gone wrong until this one.
I haven't changed a thing so something definitely went wrong with
sr2. I can still put in the previous release
- Original Message -
From: "JeffM." <[EMAIL PROTECTED]>
To:
Sent: Thursday, March 16, 2006 10:44 AM
Subject: Re: [Freedos-user] Installation problem...
I had the same exact problem. There is clearly something wrong
with service release 2. I had to go back and install sr1. I ha
I had the same exact problem. There is clearly something wrong
with service release 2. I had to go back and install sr1. I have
installed the last several releases of FD and they all went in
flawlessly on this hardware.
There have been some suggestions made, but I haven't tried
them yet. Look th
Jens Ungerer schreef:
0Stage 3: Create Startup automation file
...
Invalid Opcode at 9D79 F000 0006 0300 0086 4F43 464E 4749
dos mem corrupt, first_mcb=0271
prev 0271:|4D 0800 E7 01 00 00 00 53 44 00 00 00 00 00 00 M...rSD..
notMZ 0459:|06 00 03 86 00 00 00
24 matches
Mail list logo
