Hi,
Apparently, choice can accept any printable ASCII character for an
option, with three exceptions.
Those would be <, |, and > of course.
Are there any plans for adding a shell escape character(like \ in UNIX)
in FreeCOM?
If so, what character would be a suitable candidate?
Jeffrey
Op 30-1-2012 0:29, kurt godel schreef:
> Fellas, tnx; I didn't realize dircmd had been set that way; indeed, the
> behaviour occurs in a directory with enough entries to cause paging.
> Also, the space or lack of it in the 'dir' does not affect it
> at all. However there is still a bit of a mystery
Fellas, tnx; I didn't realize dircmd had been set that way; indeed, the
behaviour occurs in a directory with enough entries to cause paging. Also,
the space or lack of it in the 'dir' does not affect it
at all. However there is still a bit of a mystery:
even with the 'P' enabled, booting from optio
In reply to: Eric Auer
>>> ... in vague terms, that most stringent "anti
>>> reverse engineering" laws allow for independent fixes
>>> and enhancements to IP protected code, but IANAL.
> You can manipulate software to fix interoperability bugs afair.
My understanding too.
>> usually the cl
In reply to: Bernd Blaauw
> Op 29-1-2012 12:21, Bertho Grandpied schreef:
>> Hard Disk -- USB (4K sectors) -- DOS with "usbaspi.sys" (ASPI manager) --
>> "didd1000.sys" (ASPI to DOS converter)
(...)
>> The ASPI to DOS converter is the part that has to
> adapted, or else redone from scratch. I
Op 29-1-2012 17:52, Jack schreef:
> What UIDE will NOT permit is handling any BIOS units flagged as being
> "removeable"!! One CANNOT be certain all DOS variants will handle a
> "media change" (new disk) within their Int 13h coding, which was done
> at a time when Int 13h hard-disks really were
> Jack has his own private reasons for not being a fan of ASPI, thus his
> UIDE driver (PCI IDE/SATA storage and optical disk driver) doesn't
> implement nor hook into ASPI. I'm not aware of opensource CD-writing
> software that doesn't require ASPI.
Not entirely true -- UIDE can call "Int 13h"
Hi Bret,
the ASPI thing that we are missing now is, afaik, a driver
which turns partitions on ASPI non-int13 disks into DOS
block devices... Separate from that question, I find it a
very good idea in USB drivers to support the ASPI API so
other drivers and client apps can use that to access the
d
Op 29-1-2012 16:19, Bret Johnson schreef:
> USBDRIVE provides a device driver, but also provides an INT 13h interface.
> There are lots of freely available DOS tools that will work with this type of
> architecture, since the USB disk appears to be a simple removable hard drive.
> DOS should h
As I was designing USBDRIVE, I considered writing it as a straight ASPI driver
(similar to the architecture of DIDD1000 or ASPIDISK), but decided against it
for a multitude of reasons. The most important reason was the lack of freely
available DOS ASPI support programs (e.g., to format or parti
Hi people,
>> Hard Disk -- USB (4K sectors) -- DOS with "usbaspi.sys" (ASPI
>> manager) -- "didd1000.sys" (ASPI to DOS converter)
Adaptec ASPIDISK is less than 8 kB, much smaller than DI1000 the
2001 Novac Ninja ASPI disk driver 2.00 which made some FreeDOS
developers write angry comments about
Op 29-1-2012 12:21, Bertho Grandpied schreef:
> Hard Disk -- USB (4K sectors) -- DOS with "usbaspi.sys" (ASPI manager) --
> "didd1000.sys" (ASPI to DOS converter)
Ah the data flow from a drive behind an USB connector, to operating
system booted from harddisk?
> The ASPI to DOS converter is the
Continuation of previous question, subj changed, was: "Support for 4k byte
sectors"
Leaving aside (Free)DOS kernel support for bigger HD sectors.
Reminder : the following - should fit on one line - is a schematic of what is
expected to work :
Hard Disk -- USB (4K sectors) -- DOS with "usbaspi
13 matches
Mail list logo
