Hallo Herr Davi Ramos via Freedos-user,
am Sonntag, 28. April 2024 um 05:28 schrieben Sie:
> So, as I said in another message, I have a computer where I wish to install
> FreeDOS. It is a *Compaq Presario 427, Intel Pentium N3700, 4GB RAM, SSD
> 240GB, and a 14" screen.*
> Unfortunately, I canno
On Sun, 28 Apr 2024 at 16:58, Frantisek Rysanek via Freedos-user
wrote:
>
> Dear Mr. Ramos,
>
> > - Balena Etcher
> > - Rufus
> > - Untebootin
> > - Win32DiskImager.
>
> interestingly to me, you don't mention the trusty old `dd` ... :-)
Or Ventoy, which is quicker and easier than any of them.
>
Dear Mr. Ramos,
> - Balena Etcher
> - Rufus
> - Untebootin
> - Win32DiskImager.
interestingly to me, you don't mention the trusty old `dd` ... :-)
Have you tried looking for a BIOS update?
I have, but the HP support website does not respond to the "Presario
427" search query. Maybe it would res
I realized after post that the link to TinyCore I had given is mark as not
secure under Firefox. (not distributed over https)
(I don't believe it to be much dangerous) but wanted to give an alternative.
So I tested (on Ventoy USB key):
https://psychz.dl.sourceforge.net/project/bodhilinux/5.1.0/bo
I suggest:
https://ventoy.net/en/index.html
(one of the advantage of Ventoy, is that in lower left, it shows if it booted
in Clasic mode, or in UEFI mode)
Use it to make your USB key "Ventoy"
Try it by copying
http://www.tinycorelinux.net/15.x/x86/release/TinyCore-current.iso (only 23 Mb)
on
Plop (www.plop.at) helps to boot legacy usb, it works in laptops with ancient
usb ports, maybe works with your setup. The only problem that I found is that
freedos starts in read only mode.
Yahoo Mail: busca, organiza, toma el control de tu buzón
El dom., 28 de abr. de 2024 a la(s) 8:07 a.
So, that computer came with Linux, and it has a GPT partition scheme. Do
you think it would help to convert it to a msdos partition scheme? I mean
in theory it should boot regardless?
On Sun, Apr 28, 2024 at 7:28 AM Eric Auer via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:
>
> Hi! N
The bios in my machine has a section called "boot override" which works in
the same however, I also used the boot menu outside of the bios setup and
result was the same.
Em dom, 28 de abr de 2024 08:33, tom ehlert via Freedos-user <
freedos-user@lists.sourceforge.net> escreveu:
>
> > Eh... I trie
> Eh... I tried every single BIOS setting
at least on my Dell notebook there is no such *setting*.
instead I have to hit F12 while booting, this then sends me to a "select boot
device",
where I can tell it to boot from USB
Tom
___
Freedos-user m
I found Rufus to be the best option for creating a bootable usb drive for
freeDOS in all my trials.
Booting to usb on any system can be a challenge.
I know on one laptop we have it is a Windows 10 (originally Windows 8) it
absolutely refuses to boot into ANY usb unless we remove the hard drive.
J
Eh... I tried every single BIOS setting that might be even slightly
relevant. I created the USB sticks with the programs which are recommended
for me to use. I ordered 3 USB sticks of different brands. I devoted 24
hours to make this work already. If the new sticks don't work, I think
I'll, unfortu
Hi! Not all USB sticks are enabled for booting. And maybe it is disabled
in your BIOS setup. The MBR of the stick may matter as well, and whether
you boot UEFI style (not possible with FreeDOS) or classic style ;-)
___
Freedos-user mailing list
Thank you Bob and @Norby Droid .
I am aware of that, I didn't just copy the files to the USB stick. As I was
trying multiple methods, I used a variety of programs to generate the
half-a-dozen bootable drives that I tried. I used:
- Balena Etcher
- Rufus
- Untebootin
- Win32DiskImager.
I'm starti
Post ls -l of your usb drive.
As Jim mentioned, you can not just copy the .img file to a formatted usb.
You have to burn the image to the drive to make it bootable.
JP
On Sat, Apr 27, 2024 at 11:27 PM Jim Hall via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:
> To confirm, you're try
On the download page, try gettin the floppy version. On real hardware ya
may need to use an external drive, or built-in cdrom/drdrom drive if one is
available. Also ya need to go in your bios and make sure that the usb is
setup as your first boot item. Find the key for your bot options, i
believ
Thanks!
Yes, that is the image I downloaded. I did extract the image from the zip
file (FD13FULL.img). It is plugged in before boot.
On Sun, Apr 28, 2024 at 1:29 AM Jim Hall via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:
> To confirm, you're trying to boot the USB installer:
>
>
>
To confirm, you're trying to boot the USB installer:
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.3/official/FD13-FullUSB.zip
I assume you unzipped this and wrote the image to the USB flash drive
using the right tool, and didn't just use Copy to get the file to the
d
From: Simon Atkinson
--===1263012890708526426==
Content-Type: multipart/alternative; boundary=94eb2c123f12dac48f05432642a8
--94eb2c123f12dac48f05432642a8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Thanks Louis Santillan, userbeitrag, Andy Sta
From: "Jerome E. Shidel Jr."
> On Oct 28, 2016, at 1:04 PM, Simon Atkinson
wrote:
>
> Hi there
>
> I presume that FreeDOS, like other versions of DOS, will run on an
8086-based system or have I missed something?
>
> I have tried to boot FreeDOS on a IBM PS/2 Model 30 (8086 CPU and standard
From: Andy Stamp
--===2978333473432860302==
Content-Type: multipart/alternative; boundary=94eb2c18a3de3f81f5053ff09cfa
--94eb2c18a3de3f81f5053ff09cfa
Content-Type: text/plain; charset=UTF-8
Hello Simon
You could try Mateusz' Svarog86 distribution (
http://svarog86.sourceforge.net/)
From: Louis Santillan
You need to make sure you're using the 8086 compiled kernel [0][1].
Pretty sure the freedos site defaults to 8086 kernels (should say in
the kernel boot up) but you may need to overwrite the kernel to get
the correct one installed.
[0] http://www.fdos.org/kernel/
[1] http:
From: Mateusz Viste
As other said, you need to be sure to use a 8086 compilation of the
FreeDOS kernel. As an easy test you might want to try out Svarog86,
which is a FreeDOS distribution built specifically for 8086 compatibility:
http://svarog86.sourceforge.net/
Mateusz
On 28/10/2016 19:04,
From: userbeit...@abwesend.de
Hi!
Isnt't FreeDOS dependant on 80286+? Not sure, but pure 8086 isn't very
easy to handle these days. Did you try to boot without any device
drivers at all?
On original 8086 hardware you should try an old version of MS-DOS or DR
DOS. That's what I would do.
Good lu
Thanks Louis Santillan, userbeitrag, Andy Stamp, Mateusz Viste and Jerome
E. Shidel Jr. for your comments and help will investigate further and
post results shortly
Simon
>
On 28 October 2016 at 18:04, Simon Atkinson
wrote:
> Hi there
>
> I presume that FreeDOS, like other versions
> On Oct 28, 2016, at 1:04 PM, Simon Atkinson
> wrote:
>
> Hi there
>
> I presume that FreeDOS, like other versions of DOS, will run on an 8086-based
> system or have I missed something?
>
> I have tried to boot FreeDOS on a IBM PS/2 Model 30 (8086 CPU and standard
> 8-bit ISA and vers
As other said, you need to be sure to use a 8086 compilation of the
FreeDOS kernel. As an easy test you might want to try out Svarog86,
which is a FreeDOS distribution built specifically for 8086 compatibility:
http://svarog86.sourceforge.net/
Mateusz
On 28/10/2016 19:04, Simon Atkinson wrot
Hello Simon
You could try Mateusz' Svarog86 distribution (
http://svarog86.sourceforge.net/).
I am working on an 8088 emulator and I am able to boot his 360k diskette
image with no issues.
Cheers,
--Andy
On Fri, Oct 28, 2016 at 1:22 PM, wrote:
> Hi!
>
> Isnt't FreeDOS dependant on 80286+? No
Hi!
Isnt't FreeDOS dependant on 80286+? Not sure, but pure 8086 isn't very
easy to handle these days. Did you try to boot without any device
drivers at all?
On original 8086 hardware you should try an old version of MS-DOS or DR
DOS. That's what I would do.
Good luck!
userbeitrag
---
You need to make sure you're using the 8086 compiled kernel [0][1].
Pretty sure the freedos site defaults to 8086 kernels (should say in
the kernel boot up) but you may need to overwrite the kernel to get
the correct one installed.
[0] http://www.fdos.org/kernel/
[1] http://www.fdos.org/bootdisks/
Marco Antonio Achury Palma wrote:
> I remember old DOSEMU had a "exitemu" command
>
>
> 2
> Thank you. It worked perfectly! - Bob T.
--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only deve
.
--- On Sun, 9/6/09, Robert J. Thompson wrote:
> From: Robert J. Thompson
> Subject: Re: [Freedos-user] Cannot exit Dosemu/Freedos in a Console
> To: freedos-user@lists.sourceforge.net
> Date: Sunday, September 6, 2009, 8:16 PM
>
>
>
>
>
>
>
> Marco
Marco Antonio Achury Palma wrote:
I remember old DOSEMU had a "exitemu" command
2009/9/3 Robert J. Thompson :
I entered a console, say Ctrl-Alt-F4, and entered dosemu/freedos. All
appeared OK. Then, I immediately tried to exit with"ctrl-alt-page_down".
Nothing happened.
What am I doing wron
I remember old DOSEMU had a "exitemu" command
2009/9/3 Robert J. Thompson :
> I entered a console, say Ctrl-Alt-F4, and entered dosemu/freedos. All
> appeared OK. Then, I immediately tried to exit with"ctrl-alt-page_down".
> Nothing happened.
> What am I doing wrong? Bob T
>
> ---
Hi Blair,
>> PS: Another possibility is that the old MEMDISK used for our
>> 1.0 CD/DVD fails to boot on BIOSes without int 15.87 memcopy?
>
> I don't think so, because the kernel does display its init message
> before invalid opcode.
Maybe it is that "BSS_INIT macro" problem? In theory,
our ke
Eric Auer schrieb:
> Hi Blair,
>
>> I think using aspi.sys you can use cdrecord with it. Maybe I will
>> test it if I can get FreeDOS to boot on my laptop (1.0 CD kernel fails
>> to boot).
>
> Does the Rugxulo.googlepages.com kernel work? You can
> use the floppy images there to make boot CD / D
> PS: Another possibility is that the old MEMDISK used for our
> 1.0 CD/DVD fails to boot on BIOSes without int 15.87 memcopy?
I don't think so, because the kernel does display its init message
before invalid opcode.
>
> I wonder if this is what makes FDAPM ACPIDUMP fail on EEE PC
> and whether lo
Hi Blair,
> I think using aspi.sys you can use cdrecord with it. Maybe I will
> test it if I can get FreeDOS to boot on my laptop (1.0 CD kernel fails
> to boot).
Does the Rugxulo.googlepages.com kernel work? You can
use the floppy images there to make boot CD / DVD...
Eric
PS: Another possib
>> Google says rugxulo.googlepages.com and there a link
>> points to the 7zip: http://rugxulo.googlepages.com/xgcdrm24.7z
>
> Would this driver work for recording? on any drive?
I think using aspi.sys you can use cdrecord with it. Maybe I will
test it if I can get FreeDOS to boot on my laptop (1.
Eric Auer escreveu:
>
> Google says rugxulo.googlepages.com and there a link
> points to the 7zip: http://rugxulo.googlepages.com/xgcdrm24.7z
Would this driver work for recording? on any drive?
Maybe I am just daydreaming :)
Alain
>
> Eric
>
>
>
>
Hi!
Drivers like gcdrom alone only give low-level CD/DVD, no ISO9660.
>
> So apparently the ISO9660 file system is becoming common and older
> drivers won't work, true?
No. SHSUCDX is what does ISO9660 for you. Actually it would
be nice to have a version which also does UDF as well :-).
I
Ray Davison wrote:
> So apparently the ISO9660 file system is becoming common and older
> drivers won't work, true?
No. Olders drivers don't work, because native S-ATA is accessed differently.
>> Xgcdrom is xcdrom (ATAPI) and gcdrom (S-ATA) combined into
>> one driver, so you can use both types
Eric Auer wrote:
> Hi!
>
>>> Drivers like gcdrom alone only give low-level CD/DVD, no ISO9660.
So apparently the ISO9660 file system is becoming common and older
drivers won't work, true?
>
> Xgcdrom is xcdrom (ATAPI) and gcdrom (S-ATA) combined into
> one driver, so you can use both types of C
Hi!
>> Drivers like gcdrom alone only give low-level CD/DVD, no ISO9660.
>
> The CD/DVD is SATA. Since I didn't find xgcdrom I tried gcdrom. Seems
> to work. What benefit would I see with xgcdrom?
Xgcdrom is xcdrom (ATAPI) and gcdrom (S-ATA) combined into
one driver, so you can use both typ
Eric Auer wrote:
> Drivers like gcdrom alone only give low-level CD/DVD, no ISO9660.
The CD/DVD is SATA. Since I didn't find xgcdrom I tried gcdrom. Seems
to work. What benefit would I see with xgcdrom?
Ray
--
Open
Eric Auer wrote:
> Suitable drivers: xcdrom for ATAPI, gcdrom or uide
> or xgcdrom for S-ATA.
>
> Check http://rugxulo.googlepages.com/ for a mirror of XGCDROM
> and other useful updated free DOS software :-).
The CD/DVD drive is SATA.
I do not find any reference to xqcdrom on that page or in
Hi,
> I have a 1.0 CD and a 1G, USB, thumb drive that brings up what looks
> like the same menu as the CD. Both try to load XCDROM and report "No
> CD-ROM to use". Of course the CD had to use the CD drive to get to that
> point. Any idea what is going on?
The CD boots a diskette image with
> I have a 1.0 CD and a 1G, USB, thumb drive that brings up what looks
> like the same menu as the CD. Both try to load XCDROM and report "No
> CD-ROM to use". Of course the CD had to use the CD drive to get to that
> point.
>
> Any idea what is going on?
The CD-ROM contains a boot floppy image
Wang Josh schrieb:
Hello
>whenever I tried to login to freedos irc on
>irc.i7c.org
>I just get:
>"Socket Error: 10060 : The attempt to connect timed
>out"
>
>
>
Maybe theres some kind of network problem to europe. irc.i7c.org is a
"round robin" entry in our dns wich would point u always to a di
48 matches
Mail list logo
