On Sun, 18 May 2008 11:34:52 -0400 (EDT), Carl Gehr wrote:
>Because of potential confusion with various test drivers, I'm going to
>use actual driver date/times to identify what I have been using prior
>to Paul's latest update. I believe these to be from the distributions
>shown:
>> uniaud16.sys 72912 4-18-08 10:20p
> uniaud16test20080419-2.zip
>> uniaud32.sys 574658 4-01-08 6:56a
> uniaud32-1.9.2.zip
>
Here are the file dates I am working with:
11-26-06 11:46a 61,198 0 a--- uniaud16.sys
5-17-08 12:48a 4,189,118 54 a--- uniaud32.sys (DEBUG VER)
>A standard question for T6x issues:
>* Do you have:
> RUN=O:\GENMAC\DRIVER\HELPERW.EXE
>as the first executable in the Config.Sys?
No, it's quite far down on the list of run= statements. epw.exe is first.
<SNIP>
>I have:
> IFS=o:\OS2\BOOT\FAT32.IFS /CACHE:2048 /H /Q
> CALL=o:\OS2\CACHEF32.EXE /F /L:OFF
>using the FAT32 0.9.11 version. I have not tried the 0.9.12, nor the
>0.9.12 with the fix to a problem that was reported.
My cachef32 is /F /S
> What ACPI are you using and what are your switch settings?
>
>I am using:
> PSD=ACPI.PSD /SMP /EIS /ALS
> RUN=O:\OS2\ACPIDAEMON.EXE
> BASEDEV=APM.ADD
> [Note: APM.SYS is not compatible with ACPI]
I'm nearly the same, I use:
PSD=ACPI.PSD /SMP /APIC /SAP:0x20
>Don't know that this will be much help since our environments are
>somewhat different. But, the solutions these days seem to be more art
>than science.
Anyway, thanks for the feedback. I've rem'd out fat32.ifs & cachef32 and off to try it again.
Not expecting any miracles.
back to list