This is correcting my mistake,
--- On : Tue 2/7/12, Bertho Grandpied wrote :
> In reply to: Mark Brown
> > you *could* try USBASPI.SYS /V /W
> > followed by DI1000DD.SYS
> This is what I tried first thing, and the DI1000DD.SYS
> ["Ninja ASPI DISK DRIVER Ver2.00", 16368 bytes,
> MD5=9C\\\
Mark Brown-27 wrote:
>
> you *could* try USBASPI.SYS /V /W
> followed by DI1000DD.SYS
> ( works for me )
In my opinion, this is applying a band-aid to a problem that actually
requires drastic surgery. USBASPI.SYS + DI1000DD.SYS may in fact work in
certain situations. But, it is not a comp
you *could* try USBASPI.SYS /V /W
followed by DI1000DD.SYS
( works for me )
..
eufdp...@yahoo.com
eufdp...@yahoo.com
eufdp...@yahoo.com
eufdp...@yahoo.com
eufdp...@yahoo.com
On Sun, 5 Feb 2012, Kenneth Davis wrote :
> test kernel supporting 4KB sectors, note it limits
> buffers to 2 to avoid memory corruption on boot.
> Thanks for testing,
Eager to try your kernel mods with real HW, but, there is a but! in order for
my Iomega device to be recognised & proc
On Sun, 5 Feb 2012 22:56-0500 Kenneth Davis wrote :
> For testing only - warning may corrupt data!!!
> https://www.fdos.org/kernel/testing/4K/
Got'm alright! For information, had to downgrade URL protocol to HTTP:// (from
http per provided link). Not sure if it's a temporary problem at the se
On Sat, Feb 4, 2012 at 3:13 PM, Bertho Grandpied wrote:
>
> Hi, Guys! Replying to self, sort of, and Jeremy at the same time.
> I've been glancing thru the ram disk, TDSK, source. Internal buffer (used for
> init only) was provisionned for one 4K sector, but for some reason author(s)
> limited s
Hi, Guys! Replying to self, sort of, and Jeremy at the same time.
I've been glancing thru the ram disk, TDSK, source. Internal buffer (used for
init only) was provisionned for one 4K sector, but for some reason author(s)
limited sector size to 2K, as specified on the driver's command line.
I
