DOS ain't dead

I've been testing the HX/HXGUI release candidate 2.17. When i
run TESTASPI.EXE, i get the following:

-----------------------------------------------------------------
CreateFile('\\.\APIX')=23A7B8
DeviceIoControl(23A7B8, 1) failed
APIX device is unknown, testing WNASPI32 ...
LoadLibrary('WNASPI32')=257000
GetProcAddress('SendASPI32Command')=258130
GetProcAddress('GetASPI32SupportInfo')=2580A0
GetASPI32SupportInfo()=EB00 [unknown error]

dkrnl32: exception C0000005, flags=0 occured at BF:22F5E2
ax=FFFFFFFF bx=257000 cx=FFFFFFFF dx=225F10
si=0 di=0 bp=225EE4 sp=225EE4
ip = Module 'kernel32.dll'+95E2
[eip] = 81 38 45 4C 49 46 75 23 F6 40 04 33
[esp] = 00000000 00259567 FFFFFFFF 90902180 00000000 00000000
dkrnl32: fatal exit!
-----------------------------------------------------------------

I copied WNASPI32.DLL into my HX binaries directory. Clay Ruth's
FILEINFO utility reports the version as:

-----------------------------------------------------------------
Date, Time, Size: 07/17/2002 16:03:58 45,056 Win32 EXE
Internal Name: WNASPI32
Original Name: WNASPI32.DLL
File Description: ASPI for Win32 (95/NT) DLL
File Version: 4.71 (0002)
Product Name: Adaptec's ASPI Layer
Product Version: 4.71 (0002)
Company Name: Adaptec
Copyright Info: Copyright © 1989-2002 Adaptec, Inc.
-----------------------------------------------------------------

I don't know if the error is important, but I thought i'd report
it anyway.

Everything else has been looking ok (except sound of course, as
i do not have a SB installed). OS is MS-DOS 7.1.

- Doug B.

Just curious about this. How serious? Is my setup ok? Is it a bug in TESTASPI.EXE? A bug in HX?

I have my PATH variable set to look in my HX binaries directory first, then in C:\Windows\System\, but i copied the important DLLs (MSVCRTxx, OpenGL32, SDL, WnASPI32, etc) directly into my HX binaries directory for speed.

Any thoughts appreciated.

- Doug

> GetProcAddress('GetASPI32SupportInfo')=2580A0
> GetASPI32SupportInfo()=EB00 [unknown error]

> Any thoughts appreciated.

I found error code EB in WNASPI32.INC:

SS_BAD_INSTALL EQU 0EBH ;The DLL or other components are installed wrong

I will adjust TESTASPI.ASM to make it display this error.

But don't ask me what "installed wrong" does mean - I'm no ASPI expert!

---
MS-DOS forever!

Ok, thanks for the reply.

> But don't ask me what "installed wrong" does mean - I'm no ASPI expert!

Hah! I know what you mean -- neither am i!

- Doug B.