China DOS Union

http://freespace.virgin.net/alpha.systems/tips.htm


Quote:

NOTE: Logitech’s MouseWare for DOS/Windows 31/95, version 7.1, is a

MUST HAVE FOR ALL DOS/WINDOWS USERS! Download it from:

1. UPDATE: LOGI71.ZIP is not available on AOL anymore!
2. http://www.logitech.com/TechSupp/2122.htm (where you can find ONLY the old version 6.43 of Logitech DOS/Win31 mouse drivers and the NEW version 7.2 of Win95 only Logitech virtual mouse driver).

3. A concerned emailer found LOGI71.ZIP at this FTP site:

ftp://ftp.volftp.vol.it/pub/pc/windows/win95/driver/mouse/logi71.zip

Thanks a lot Guenter for the valuable tip!

UPDATE: LOGI71.ZIP is zipped by Video On Line FTP Site:

http://www.volftp.vol.it ftp://ftp.volftp.vol.it email: ftpsw@vol.it and contains Logitech MouseWare Drivers version 7.1 for DOS/Windows 3.1x and version 7.2 for Windows 95.

This update appears courtesy of:

jezek@ure.cas.cz


4. Another FTP server that has LOGI71.ZIP posted: ftp://ftp.cyberbox.north.de/pub/misc/drivers/misc/logi71.zip

I tried it, but couldn't download. Anyone else try it............................

Here is also:

http://www.kisser.net.au/tontodan/Dos95mem.html

It's too long. I took a general look.

I can make the free conventional memory reach 632K by using QEMM386 with 4DOS. If I reduce the environment variable space of 4DOS a bit (since I really need that much), I can even reach 634K.

Modules using memory below 1 MB:

Name Total = Conventional + Upper Memory
-------- ---------------- ---------------- ----------------
SYSTEM 4,189 (4K) 725,149 (708K) 4,294,24 (4,193,
QEMM386 912 (1K) 912 (1K) 0 (0K)
4DOS 6,544 (6K) 336 (0K) 6,208 (6K)
DOS-UP 224 (0K) 0 (0K) 224 (0K)
DOSDATA 6,496 (6K) 0 (0K) 6,496 (6K)
QDPMI 2,912 (3K) 0 (0K) 2,912 (3K)
DISPLAY 8,304 (8K) 0 (0K) 8,304 (8K)
ANSI 4,208 (4K) 0 (0K) 4,208 (4K)
RAMDRIVE 1,328 (1K) 0 (0K) 1,328 (1K)
FILES 2,096 (2K) 0 (0K) 2,096 (2K)
FCBS 96 (0K) 0 (0K) 96 (0K)
WKBUFFER 528 (1K) 0 (0K) 528 (1K)
LASTDRIV 2,304 (2K) 0 (0K) 2,304 (2K)
INSTALL 160 (0K) 0 (0K) 160 (0K)
UDMA 656 (1K) 0 (0K) 656 (1K)
TRICDVD 7,536 (7K) 0 (0K) 7,536 (7K)
POWER 4,704 (5K) 0 (0K) 4,704 (5K)
MSCDEX 34,000 (33K) 0 (0K) 34,000 (33K)
DIET 1,760 (2K) 0 (0K) 1,760 (2K)
QDICT 2,352 (2K) 0 (0K) 2,352 (2K)
DISKMON 9,616 (9K) 0 (0K) 9,616 (9K)
SMARTFLP 14,560 (14K) 0 (0K) 14,560 (14K)
kstack 1,600 (2K) 0 (0K) 1,600 (2K)
NCACHE2 16,400 (16K) 0 (0K) 16,400 (16K)
NCACHE23 14,048 (14K) 0 (0K) 14,048 (14K)
Free 673,536 (658K) 647,552 (632K) 25,984 (25K)

Memory Summary:

Type of Memory Total = Used + Free
---------------- ---------- ---------- ----------
Conventional 655,360 7,808 647,552
Upper 4,294,414, 4,294,388, 25,984
Reserved 0 0 0
Extended (XMS) 67,596,208 488,368 67,107,840
---------------- ---------- ---------- ----------
Total memory 67,698,688 4,294,884, 67,781,376

Total under 1 MB 102,480 4,294,396, 673,536

Total Expanded (EMS) 267,501,56 (261,232
Free Expanded (EMS) 220,102,65 (214,944
Largest executable program size 647,536 (632K)
Largest free upper memory block 25,856 (25K)
Available space in High Memory Area 1,184 (1K)
MS-DOS is resident in the high memory area.

If I use the new mouse and CD - ROM drives now, I can save more upper memory.

Your SYSTEM is a bit smaller than mine. What exactly is your upper?

Your basic memory is at most 640K, but mine is only 637K. This is probably related to the motherboard.

Conventional memory should theoretically be 640K. In some cases, 639K is also normal. But your 637K, according to the past DOS situation, must have a virus, but according to the current machine configuration, it's not known if it's the reason mentioned by "Fujian ABC".

Free conventional memory reported by MEM:

Free Conventional Memory:

Segment Total
------- -----------------
00153 2,368 (2K)
001E7 88,992 (87K)
017A1 558,560 (545K)

Total Free: 649,920 (635K)

Free Upper Memory:

Region Largest Free Total Free Total Size
------ -------------- -------------- --------------
1 128 (0K) 128 (0K) 28,784 (28K)
2 25,856 (25K) 25,856 (25K) 139,296 (136K)

Memory status listed by QEMM itself:

Unavailable Converted
Initial to QEMM by QEMM Leaving
Conventional: 640K - 0K - 0K = 640K
Extended: 286M - 0K - 255M =32767K
Expanded: 0K - 0K + 254M = 254M
High RAM: 0K - 0K + 168K = 168K
------ ------ ------ ------
TOTAL: 287M - 0K - 344K = 287M

344K QEMM Overhead
Code & Data: 276K Maps: 0K
Tasks: 20K Mapped ROM: 24K
DMA Buffer: 16K Unassigned: 8K
0.8K Conventional Memory Overhead

Suggest the above friends to post your AUTOEXEC.BAT and COBFIG.SYS for everyone to see.

There are too many posts. My two files are more than ten and twenty-something K respectively, and they are still being modified continuously. Moreover, the basic structures are all the same, and it's just that the content loaded is different. If you have any questions, just feel free to ask.

config.sys

device=c:\qemm\dosdata.sys
SET LOADHIDATA=C:\QEMM\LOADHI.RF
DEVICE=C:\TOOLS\QEMM386.SYS RAM ST:F DMA=64 RF
device=c:\qemm\dos-up.sys @c:\qemm\dos7-up.dat
DOS=HIGH,UMB
FILES=40
LASTDRIVE=K
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\TOOLS\QCDROM.SYS /D:IDE-CD
SHELL=C:\QEMM\LOADHI.COM /RF C:\COMMAND.COM C:\ /P

[ Last edited by 3dfx on 2006-6-14 at 23:37 ]

autoexec.bat

C:\QEMM\LOADHI /RF C:\TOOLS\NWCDEX.EXE /D:IDE-CD /E
C:\QEMM\LOADHI /RF C:\TOOLS\PCCACHE.COM
PATH C:\DOS;C:\TOOLS;C:\QEMM;C:\FPE;C:\GW;C:\TOOLS\SEA13;C:\AV98;C:\UCDOS;C:\CCDOS;C:\ARACHNE;%PATH%
LH C:\DOS\CTMOUSE.EXE
SET TEMP=I:\
XMSDSK 36000 /T /Y

[ Last edited by 3dfx on 2006-6-14 at 23:32 ]

Strong! But after booting from the MSDOS 7.1 boot disk, there are about 610K left in the conventional memory. What advantages will there be after the foreigners optimized it to over 630K? Is it that the disk reading and writing will be faster after optimization? In DOS, I am already satisfied with 600K left in the conventional memory, but my most concerned issue is the hard disk reading and writing speed.

qemm386 is indeed powerful, but the file size is too large to be used for a boot disk.

No, my boot disk uses QEMM386.SYS. Of course, I also use HIMEM.SYS + EMM386.EXE (mainly to prevent compatibility issues). A floppy disk has such a small capacity, you can't include all functions. Everyone can make it according to their own preferences and habits. Therefore, my system starts with a single disk, one or several tool disks, one Chinese system disk, and others are made as needed.

Floppy disks have limited capacity and are easily damaged. Why not use USB drives

Originally posted by DOSforever at 2006-6-16 01:33 AM:
No, the boot disk I use is QEMM386.SYS. Of course, I also use HIMEM.SYS + EMM386.EXE (mainly to prevent compatibility issues). A floppy disk has such a small capacity, you can't have all the functions...

In that case, you might as well use a bootable CD or bootable USB drive.
By the way, does QEMM386 bring DOS into protected mode like EMM386?

[ Last edited by brglng on 2006-6-16 at 10:48 ]

You know, not all machines support USB drive booting. At least my own machine doesn't. As for the CD-ROM, it's fixed and can't be modified. Of course, don't say let me use a RW disc to burn it. Originally, I also had the idea of using a 2.88M floppy disk as a boot disk, and later I also had the idea of using ZIP, LS120, EZ-FLYER and so on. Hey... unfortunately, they haven't become popular.

QEMM386.SYS is the same as EMM386.EXE. As long as EMS is enabled, the CPU's operating mode is in V86 mode. According to my understanding, as long as DOS can use more than 1M of memory, the CPU should be in protected mode. But I'm curious that if only HIMEM.SYS is used to enable XMS, the CPU is still in real mode. I haven't figured out this problem yet. And QEMM386.SYS, whether EMS is enabled or not, even if only XMS is used, the CPU is in V86 mode. I think it may be that the memory management mechanisms of the two are different. I haven't used other memory management programs much. Those who have used them can talk about it.

In fact, it's not necessary for us users to deliberately care about what working mode the CPU is in, and it's not something we can change manually. At that time, the program will switch by itself. Just like some programs that need DOS4GW.EXE to run, you don't need any memory management, and then it will automatically switch to protected mode to run.