Carga de juegos en Advmenu

DEVICEHIGH=C:\DOSDRV\XDMA.SYS = XDMA -- DOS UltraDMA Disk Driver

Digamos que lord usa discos Serial Ata????? eso va a ser que zumba muuuucho mas que el ide....

Para mas info pinchar aqui.

¿Y eso en qué afecta? ¿Se aceleran las lecturas al disco, o simplemente que con ese tipode disco si no se usa el driver XDMA no carbura?

digamos que si le pones eso al disco... es como si le pones queroseno a tu coche... a que zumbaria mas???

Carburar carbura... ya que el controlador lo carga en el config.sys por lo que ya ha empezado a leer el disco... eso si... le pone el turbo

Pero si pongo queroseno al coche, corre la hueva pero me lo cargo. ¿Pasaría lo mismo con el HD? No creo, ¿no?

pues no... pero ese controlador no creo que sirva para tu disco duro...

Esto es lo que he encontrado al respecto, yo creo que sirve para discos P-ATA normales de toda la vida pero no para los S-ATA.

Bubu esto tienes que probarlo porque si va bien debería estar en el Arcados.

XDMA is a DOS driver for UltraDMA hard-disks. It supports normal "end
user" PC mainboards having an Intel, VIA, SiS, ALi, or similar UltraDMA
controller set by the BIOS in "Legacy IDE mode". XDMA does NOT handle
Serial-ATA, "Native PCI mode" servers or "add-on" adapter cards made by
Promise, SiiG, etc. XDMA runs normal mainboard IDE chips and AVOIDS a
need for an "add-on" card!

XDMA handles up to 4 UltraDMA disks of any size, including newer models
over 128 gigabytes of storage. It "intercepts" DOS disk I-O requests
issued as "Int 13h" calls for the BIOS; read/write requests are handled
using UltraDMA. All other "Int 13h" calls (seeks, requests for other
device types, etc.) are "passed" back to the BIOS or to another driver.
XDMA accepts 48-bit LBA mode I-O requests used by MS-DOS V7.xx, FreeDOS
or other newer DOS systems that use LBA mode I-O. 24-bit CHS requests
used by MS-DOS V6.xx or other "old" DOS systems are also accepted. As
CHS I-O has only 24-bit addressing, data accessed using CHS I-O must be
in the first 8 gigabytes of a disk. Other partitions may contain more
data and may be accessed by operating systems that permit LBA mode I-O.

XDMA offers output overlap, which buffers all output and does NOT await
output end, so user work may overlap the DMA! Depending on the user's
system and software, overlap can increase speed significantly! For an
output error or 400-msec output timeout, an error message will display,
and a warning "beep" will sound. Overlap must be enabled with a /O in
the CONFIG.SYS command which loads XDMA (see section 3 below for switch
options). Output overlap requires that each IDE channel CANNOT run an
UltraDMA disk and an ATAPI drive (CD-ROM, etc.) or a non-UltraDMA unit!
Other drivers are unaware XDMA leaves output "running" and such drivers
may post controller-busy ERRORS if using the same channel as XDMA. If
either IDE channel runs an UltraDMA disk and an ATAPI or a non-UltraDMA
drive, output overlap must NOT be enabled! XDMA is intended for most
"home user" systems, which normally place their UltraDMA disk(s) on the
primary IDE channel, with ATAPI and other units placed on the secondary
IDE channel. These systems can achieve better speed IMMEDIATELY using
XDMA with output overlap! NOTE that the XCDROM driver DOES permit an
UltraDMA disk and a CD/DVD drive to "share" an IDE channel and use XDMA
output overlap!

XDMA requires 1344 bytes of memory with output overlap enabled and 1056
bytes without overlap. An XMS manager, HIMEM.SYS or similar, and 128K
of XMS memory are also required, so XDMA can allocate a "local buffer".
For overlap or for any user I-O buffers not meeting UltraDMA alignment/
boundary rules, UltraDMA I-O goes through the "local buffer" which acts
as a "middleman" between the user buffer and the disk. Almost all DOS
systems do load HIMEM.SYS, since it lets the DOS "kernel" reside in the
high-memory area (HMA) and saves MUCH space below 640K!

Pues sí, hay que catarlo. Por lo que leo ahí parece que es un driver que intercepta las llamadas del S.O. a la BIOS mediante la interrupción INT 13h, y puede mejorar significativamente los tiempos de acceso, jiji. A ver qué tal. ¡ Gracias !

Ya lo he catado, y no supone ninguna mejora en el rendimiento. Los tiempos de carga del menú de juegos, y de la ejecución de éstos son idénticos a como si no estuviera cargado el XDMA. Bueno, ya saldrá otra cosa, jiji.