Hi,
> On Jul 14, 2022, at 12:28 AM, Rugxulo wrote:
>
> Hi,
>
> On Wed, Jul 13, 2022 at 10:20 PM Jerome Shidel wrote:
>>
>>> On Jul 13, 2022, at 2:29 PM, Rugxulo wrote:
>>>
FDAUTO.BAT
——
set DOSDRV=C:
>>>
>>> If you're using FreeCOM and already in the root directory from
Hi,
On Wed, Jul 13, 2022 at 10:20 PM Jerome Shidel wrote:
>
> > On Jul 13, 2022, at 2:29 PM, Rugxulo wrote:
> >
> >> FDAUTO.BAT
> >> ——
> >> set DOSDRV=C:
> >
> > If you're using FreeCOM and already in the root directory from bootup, try
> > this:
> >
> > REM ... should be "C:\" ...
> > set
Hi,
> On Jul 13, 2022, at 2:29 PM, Rugxulo wrote:
>
> Hi,
>
>> On Mon, Jul 11, 2022 at 6:09 AM Jerome Shidel wrote:
>>
>> FDCONFIG.SYS
>>
>> !LASTDRIVE=Z
>
> You probably don't actually need that many drives, I'd suggest "G" or
> "P" instead (to save RAM).
>
>> FDAUTO.BAT
>> —
Hi,
On Mon, Jul 11, 2022 at 6:09 AM Jerome Shidel wrote:
>
> FDCONFIG.SYS
>
> !LASTDRIVE=Z
You probably don't actually need that many drives, I'd suggest "G" or
"P" instead (to save RAM).
> FDAUTO.BAT
> ——
> set DOSDRV=C:
If you're using FreeCOM and already in the root directory f
On Tue, Jul 12, 2022 at 2:05 PM Jose Senna wrote:
>
>
> Jim Hall said:
> > The /P switch in FreeCOM says that
> > COMMAND.COM is a permanent shell,
> > so it never exits (the EXIT command
> > does nothing). That /P ("permanent")
> > feature probably doesn't exist on
> > other applications,
Jim Hall said:
> The /P switch in FreeCOM says that
> COMMAND.COM is a permanent shell,
> so it never exits (the EXIT command
> does nothing). That /P ("permanent")
> feature probably doesn't exist on
> other applications, because they
> don't need it.
Then you mean the /P switch is
Hi Nico,
> I'm only interested in the files on the USB drive. Also, I'm not sure if
> this will have to run on EFI machines, my main target is like the
> 2000s-early 2010s laptops that some people seem to have lying around. My
> main main target is specifically my laptop from that time period,
On Mon, Jul 11, 2022 at 3:11 AM Nico via Freedos-user
wrote:
> I'm only interested in the files on the USB drive. Also, I'm not sure if
> this will have to run on EFI machines, my main target is like the
> 2000s-early 2010s laptops that some people seem to have lying around. My
> main main target
> Jim Hall said:
>
> | Let's say you wanted to run FreeDOS EDIT every time FreeDOS boots up.
> | The full path to EDIT is C:\FREEDOS\BIN\EDIT.EXE, so you would create
> | a custom FDCONFIG.SYS that probably looked like this:
> |
> | FILES=20
> | BUFFERS=20
> | SHELL=C:\FREEDOS\BIN\EDIT.EXE
Hi,
My 2 cents worth…
Like Mateusz mentioned… There is no guarantee that the BIOS will permit disk
writes to a booted USB stick. However since you intend on supporting only your
personal machines, you can just do a quick test and not worry about that. A
quick and dirty test would be to burn t
On 11/07/2022 03:56, Bob Pryor wrote:
Hi Nico,
Are you interested in access to system hardware and files?
Or simply your editor and the files you are using on the usb drive?
And UEFI could be a problem if you are thinking of hardware not in your
control.
FreeDOS _might_ boot anywhere with a keyb
On 7/10/2022 2:46 PM, Nico via Freedos-user wrote:
hi,
I would like to create a minimal bootable image for a USB drive (or
other formats, maybe even floppies, but USB is the focus) that boots
into a single application (in my case, a custom minimal word
processor, although freeDOS EDIT is a dec
On 10/07/2022 23:46, Nico via Freedos-user wrote:
I would like to create a minimal bootable image for a USB drive (or
other formats, maybe even floppies, but USB is the focus) that boots
into a single application (in my case, a custom minimal word processor,
although freeDOS EDIT is a decent st
Jim Hall said:
| Let's say you wanted to run FreeDOS EDIT every time FreeDOS boots up.
| The full path to EDIT is C:\FREEDOS\BIN\EDIT.EXE, so you would create
| a custom FDCONFIG.SYS that probably looked like this:
|
| FILES=20
| BUFFERS=20
| SHELL=C:\FREEDOS\BIN\EDIT.EXE
|
| For #2,
Hi Nico,
Are you interested in access to system hardware and files?
Or simply your editor and the files you are using on the usb drive?
And UEFI could be a problem if you are thinking of hardware not in your
control.
FreeDOS _might_ boot anywhere with a keyboard and compatible video, with
your usb
Regarding exiting the program. What about wrapping it in endless cycle?
Only hard reset or shutdown would break it. Something like while (true) {}
? Or just put it in bat multiple times, so if you exit, it start again and
user will ignore it few times :-D
On Mon 11. 7. 2022 at 1:23, Jim Hall wrot
On Sun, Jul 10, 2022 at 5:03 PM Nico via Freedos-user
wrote:
>
> hi,
> I would like to create a minimal bootable image for a USB drive (or
> other formats, maybe even floppies, but USB is the focus) that boots
> into a single application (in my case, a custom minimal word processor,
> although fre
17 matches
Mail list logo
