中国DOS联盟

I used loadsys, addev and other methods but couldn't load in batch processing and command prompt.

Is it because I wrote the command incorrectly, or is it that DI1000DD.SYS just can't be loaded in batch processing and command prompt?

Asking all friends.

Last edited by lsj1112 on 2006-9-7 at 07:24 ]

Can be loaded in the command line or batch processing, and the format is
device drive letter:\path\file name

I want to be able to uninstall it at any time after loading, so using device, deload, etc., can't achieve my function.

Is it that if there is no USB device connected, you can't load di1000dd.sys at the prompt?

I didn't connect a USB flash drive. When I used devload to load di1000.sys at the prompt, the result was:

DI1000 ASPI DISK Driver Ver 2.00
Copyright(C)2001 NOVAC Co.,Ltd.

Available ID = 01234567 Not found installable device.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Loading with loadsys:

Loadsys v1.4i: Copyright (C) G W Robinson/DRAL 1990-95. All Rights Reserved.
Loading Device Driver in upper memory
!!!Warning: Insufficient space in upper memory to supply
053D paragraph block. Largest available block is 045C paragraphs.
Attempting to obtain block from lower memory
?Program Run
DI1000 ASPI DISK Driver Ver 2.00
Copyright(C)2001 NOVAC Co.,Ltd.

Available ID = 01234567 Not found installable device.

?Program End

!!!Error: Driver failed to Initialise with error: 810C
!!!Error: Device Driver I:\DI1000DD.SYS failed to load


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Please ask the experts for an answer, thank you!

Load in config, use mem to check, can't see di1000dd.sys. Can see it with ram.

Attachment:
mem/c/p:

Modules using memory below 1 MB:

Name Total Conventional Upper Memory
-------- ---------------- ---------------- ----------------
SYSTEM 32,768 (32K) 9,888 (10K) 22,880 (22K)
HIMEM 3,840 (4K) 3,840 (4K) 0 (0K)
UMBPCI 176 (0K) 176 (0K) 0 (0K)
EMM386 3,200 (3K) 3,200 (3K) 0 (0K)
LOWDMA 688 (1K) 688 (1K) 0 (0K)
COMMAND 4,864 (5K) 4,864 (5K) 0 (0K)
SHSUCDX 5,808 (6K) 5,808 (6K) 0 (0K)
TW 35,232 (34K) 12,352 (12K) 22,880 (22K)
GH95 2,816 (3K) 0 (0K) 2,816 (3K)
ZENO 1,376 (1K) 0 (0K) 1,376 (1K)
XMSDSK 688 (1K) 0 (0K) 688 (1K)
VIDE-CDD 5,024 (5K) 0 (0K) 5,024 (5K)
USBASPI 14,816 (14K) 0 (0K) 14,816 (14K)
KILLER 400 (0K) 0 (0K) 400 (0K)
DOSKEY 3,968 (4K) 0 (0K) 3,968 (4K)
DOSLFN 28,144 (27K) 0 (0K) 28,144 (27K)
Free 631,696 (617K) 610,288 (596K) 21,408 (21K)



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

ram :

Memory status of this computer
Address. Low memory Upper memory Resident programs or device drivers
----- -------- -------- --------------------------
021Eh 3,824 .. Device name=HIMEM Address=8000h Name=XMSXXXX0
030Eh 160 .. Device name=UMBPCI Address=E000h Name=UMBPCIXX
0319h 3,184 .. Device name=EMM386 Address=C000h Name=EMMXXXX0
03E1h 672 .. Device name=LOWDMA Address=E000h Name=LOWDMA$$
040Ch 544 .. IFS=
045Bh 4,816 .. COMMAND /E:640 /P /D /K AUTOEXEC
05D9h 5,792 .. SHSUCDX
07A5h 12,336 22,864 TW
0AA9h 607,584 .. <Maximum free memory space>
----- Start of upper memory status ------
B1ADh .. 1,360 ZENO /q
B203h .. 2,784 GH95
B2A9h .. 672 XMSDSK
D802h .. 5,008 Device name=VIDE-CDD Address=C800h Name=IDE-CD
D93Ch .. 14,800 Device name=USBASPI Address=C000h Name=SCSIMGR$
DCDAh .. 1,200 IFS=DI1000DD
E26Dh .. 384 KILLER
E286h .. 3,952 DOSKEY
E37Eh .. 28,128 DOSLFN

651,264 bits total (636k) is the total conventional memory managed by DOS 7.10.
607,584 bits (593k) is the maximum free space available for programs. There is 21,168 bits of upper memory free.

EMM386 is already running. Upper memory is now managed by DOS.

0 bits of Ext(extended) (AT/286/386) memory, as reported by BIOS.
65,408k bits of XMS 2.0 (4.00) memory: 12,178k in use + 53,230k free. DOS resides in HMA.

33,152k bits of XMS 4.0 memory: 384k in use + 32,768k free. Page frame C800h.

Last edited by lsj1112 on 2006-9-7 at 07:22 ]

Originally posted by lsj1112 at 2006-9-7 07:17 AM:
Is it that without a connected USB device, you can't load di1000dd.sys at the prompt?

Yes.

Thanks to the reply from the upstairs!

Why can't mem see di1000dd.sys in memory but ram can see di1000dd.sys?

Also:
To use USB devices, before loading di1000dd.sys, do you have to load usbaspi.sys first? That is to say, to load di1000dd and usbaspi at the same time, usbaspi must be loaded first?

Last edited by lsj1112 on 2006-9-7 at 09:20 ]

Originally posted by lsj1112 at 2006-9-7 08:03 AM:
To use USB devices, before loading di1000dd.sys, do you have to load usbaspi.sys first? That is, to load di1000dd and usbaspi at the same time, must usbaspi be loaded first?

Right.

Are the ASPIOHCI.SYS, ASPIUHCI.SYS, and ASPIEHCI.SYS necessary USB drivers?

What are the requirements for their loading order?

I found that loading DI1000DD.SYS under DOS7.1 went very smoothly, but in DOS6.22, there was a prompt message at the end, and I had to press "R" to use the USB flash drive. Whether it's called with DEVLOAD or called with DEVICE in CONFIG.SYS, it's the same. I don't know why. Is it a version issue of USBASPI.SYS or DI1000DD.SYS?

Originally posted by lsj1112 at 2006-9-7 10:35 PM:
Are ASPIOHCI.SYS, ASPIUHCI.SYS, and ASPIEHCI.SYS necessary USB drivers?

What are the requirements for their loading order?

These USB drivers vary depending on the motherboard.
It is best to use USBASPI.SYS (the highest version is 2.2), which is very universal. It seems that the above several drivers are all included, and it is very universal anyway.
Moreover, USBASPI.SYS is a USB flash drive driver, and DI1000DD.SYS is for assigning drive letters. Therefore, you must load USBASPI.SYS first, and then load DI1000DD.SYS.
LOADSYS.EXE can be used to simulate hot plugging.

Insert the USB flash drive first!!!!!!!
Format: LOADSYS USBASPI.SYS
LOADSYS DI1000DD.SYS

At this time, the USB flash drive has been loaded

Uninstall by using LOADSYS /u twice

These files can be found in the forum.

Good person, finally found it

Got it, thanks everyone

Thanks everyone for sharing, finally found it