Opened 11 years ago

Closed 10 years ago

#59 closed defect (fixed)

VDMs don't start with ACPI 3.02

Reported by: Mike Forester <forester@…> Owned by: anonymous
Priority: major Milestone:
Component: ACPI PSD Version: 3.03
Keywords: Cc:

Description

WinOS2 sessions don't appear to launch. DOS sessions launch but immediately hang -- AUTOEXEC.BAT is never processed. This is true whether I have any REMAPs or not. DOS/WinOS2 works normally with ACPI 2.22.

ACPI 3.02, APM 1.17, Tyan S2865, nForce 4, Athlon64 X2 in SMP APIC mode SNAP 3.18

Attachments (3)

ACPI_PIC_Trap-0e.jpg (61.1 KB) - added by guest 11 years ago.
acpi.log (15.4 KB) - added by guest 11 years ago.
acpi_SMP_APIC_no_remaps.log (14.9 KB) - added by guest 11 years ago.

Download all attachments as: .zip

Change History (31)

comment:1 follow-up: Changed 11 years ago by pasha

  • Owner changed from pasha to anonymous
  • Status changed from new to assigned

Do you try use EARLYMEMINIT=TRUE in config.sys ? (if absent hpfs386.ifs)

comment:2 in reply to: ↑ 1 Changed 11 years ago by Mike Forester <forester@…>

Replying to pasha:

Do you try use EARLYMEMINIT=TRUE in config.sys ? (if absent hpfs386.ifs)

Yes, I've had that for a long time. I used to need it for FAT32, now I need it to enable a large JFS cache. (I need the large JFS cache to make the SBlive driver work with 3GB RAM.)

Should I try turning EARLYMEMINIT off?

comment:3 follow-up: Changed 11 years ago by pasha

No, try remming FAT32.IFS

comment:4 in reply to: ↑ 3 ; follow-up: Changed 11 years ago by Mike Forester <forester@…>

Replying to pasha:

No, try remming FAT32.IFS

No change.

However, I have an old problem with VDMs that may be pertinent. I can open them from a desktop object, but if I type "start /win/dos" at a CMD prompt, I always get a SYS0005. That's been true for a couple of years now.

Let me try on a clean install and see if there's any difference.

comment:5 in reply to: ↑ 4 Changed 11 years ago by Mike Forester <forester@…>

Replying to Mike Forester <forester@panix.com>:

Let me try on a clean install and see if there's any difference.

Okay, I did a clean install of eCS 1.2R and added kernel 14.104a_SMP, Snap 3.18 and Amouse. EARLYMEMINIT=TRUE. Same result.

I did notice that both processors went up to ~50% while the DOS session was trying to start.

This doesn't affect anybody else? :(

comment:6 Changed 11 years ago by pasha

  • Resolution set to fixed
  • Status changed from assigned to closed

Ok. Wait acpipsd version 3.3 , then try acpi.psd /SMP /PIC. If problem was here - reopen ticket

Changed 11 years ago by guest

comment:7 Changed 11 years ago by guest

  • Resolution fixed deleted
  • Status changed from closed to reopened
  • Version changed from 3.02 to 3.03

Okay, VDMs still don't work in 3.03. Also, I can't boot with /SMP /PIC -- I get a Trap 0E. (See attached jpg.)

/SMP /APIC works fine (except for VDMs).

Would acpi.log help? Should I use the debug version?

comment:8 Changed 11 years ago by pasha

acpi.log yes, debug version - as you want

Changed 11 years ago by guest

comment:9 Changed 11 years ago by guest

Sorry, I forgot to mention, the /PIC mode trap occurs when PMSHELL starts.

comment:10 follow-up: Changed 11 years ago by pasha

Can you remove all LINK from acpi.cfg and try boot with psd=acpi.psd /SMP, if fail - boot with /APIC and give me log

comment:11 in reply to: ↑ 10 ; follow-up: Changed 11 years ago by guest

Replying to pasha:

Can you remove all LINK from acpi.cfg and try boot with psd=acpi.psd /SMP, if fail - boot with /APIC and give me log

Okay...

psd=acpi.psd /SMP = trap E at PMSHELL startup

almost identical to the trap screen I attached

psd=acpi.psd /ACPI = hang in config.sys

leaves all USB ports disabled (!) -- I had to turn main power off to reenable them

ACPI.LOG attached with psd=acpi.psd /SMP /ACPI and all REMAPS removed from acpi.cfg.

Changed 11 years ago by guest

comment:12 in reply to: ↑ 11 Changed 11 years ago by guest

Replying to guest:

psd=acpi.psd /ACPI = hang in config.sys

Gaah. I meant

psd=acpi.psd /APIC

comment:13 follow-up: Changed 11 years ago by pasha

Do you use in VDM session SoundBlaster?, Network or any device, except mouse and keyboard?

Problem with /PIC at nvidia I see and work for resolving.

comment:14 in reply to: ↑ 13 Changed 11 years ago by guest

Replying to pasha:

Do you use in VDM session SoundBlaster?, Network or any device, except mouse and keyboard?

By default my DOS sessions load ANSI.SYS and VDOSTCP.SYS. Removing them from specific DOS sessions doesn't help.

I have an old version of DTA loaded for Windows audio, but no audio in plain DOS.

Problem with /PIC at nvidia I see and work for resolving.

Cool. :)

comment:15 Changed 11 years ago by guest

Here's the complete list:

DEVICE=C:\OS2\MDOS\VASPI.SYS DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\MDOS\VCDROM.SYS DEVICE=C:\OS2\MDOS\VCOM.SYS DEVICE=C:\MMOS2\VCSHDD.SYS DEVICE=C:\MMOS2\VGENAUD.SYS DEVICE=C:\OS2\MDOS\VSVGA.SYS DEVICE=C:\OS2\MDOS\VMANWIN.SYS DEVICE=C:\OS2\MDOS\VDPMI.SYS DEVICE=C:\OS2\MDOS\VDPX.SYS DEVICE=C:\OS2\MDOS\VEMM.SYS DEVICE=C:\OS2\MDOS\VW32S.SYS DEVICE=C:\OS2\MDOS\VWIN.SYS DEVICE=C:\OS2\MDOS\VXMS.SYS /UMB DEVICEHIGH=E:\TCPIP\bin\vdostcp.sys

comment:16 follow-up: Changed 11 years ago by pasha

I mean, what you load for each VDM session. Properties -> session -> DOS properties

comment:17 in reply to: ↑ 16 ; follow-up: Changed 11 years ago by guest

Replying to pasha:

I mean, what you load for each VDM session. Properties -> session -> DOS properties

Right, just ANSI.SYS and VDOSTCP.SYS show in DOS settings. However, VASPI.SYS, VCOM.SYS and VGENAUD.SYS are loaded by the system. Ima REM them out and see what happens.

comment:18 in reply to: ↑ 17 ; follow-up: Changed 11 years ago by pasha

Replying to guest:

Replying to pasha:

I mean, what you load for each VDM session. Properties -> session -> DOS properties

Right, just ANSI.SYS and VDOSTCP.SYS show in DOS settings. However, VASPI.SYS, VCOM.SYS and VGENAUD.SYS are loaded by the system. Ima REM them out and see what happens.

I understand right? If you remming this drivers - VDM work.

comment:19 in reply to: ↑ 18 Changed 11 years ago by guest

Replying to pasha:

Right, just ANSI.SYS and VDOSTCP.SYS show in DOS settings. However, VASPI.SYS, VCOM.SYS and VGENAUD.SYS are loaded by the system. Ima REM them out and see what happens.

I understand right? If you remming this drivers - VDM work.

That's what I hoped. It does not help. :(

comment:20 follow-up: Changed 11 years ago by pasha

Diff from acpi 2.22 and 3.xx for you only in IRQ number. Now you have high IRQ number. Problem is here. So one of your VDM driver or VDM options can't work with high IRQ number.

comment:21 in reply to: ↑ 20 ; follow-up: Changed 11 years ago by guest

Replying to pasha:

Diff from acpi 2.22 and 3.xx for you only in IRQ number. Now you have high IRQ number. Problem is here. So one of your VDM driver or VDM options can't work with high IRQ number.

Okay, I understand that. I've tried removing all the VDDs, though, and that doesn't solve it. I'll post on the forum and see if anyone else has this problem.

Thanks.

comment:22 in reply to: ↑ 21 ; follow-up: Changed 11 years ago by guest

Replying to guest:

Replying to pasha:

Diff from acpi 2.22 and 3.xx for you only in IRQ number. Now you have high IRQ number. Problem is here. So one of your VDM driver or VDM options can't work with high IRQ number.

Okay, I understand that. I've tried removing all the VDDs, though, and that doesn't solve it. I'll post on the forum and see if anyone else has this problem.

From: Bill Silverstein: Adding in my two cents worth. I have had On two fresh installs of RC3 on dual core systems with /SMP and /APIC, I had two different results.

On the laptop (Lifebook e8210, core 2 duo), all works fine, but when when using windowed VDMs, dos does not work (but does in full screen) and Windowed Windows vdm gives an error message, but works fine. This uses irqs 0,1,2,4,8,9,12,14,16,and 19.

On the desktop (K4N9 utra, using a separate realtek 8139 card), the sessions think that they are completed. This uses irqs 0,1,2,4,6, 8,9,12,14,16,21, 22, and 23.

comment:23 in reply to: ↑ 22 Changed 11 years ago by pasha

Replying to guest:

Replying to guest:

Replying to pasha:

Diff from acpi 2.22 and 3.xx for you only in IRQ number. Now you have high IRQ number. Problem is here. So one of your VDM driver or VDM options can't work with high IRQ number.

Okay, I understand that. I've tried removing all the VDDs, though, and that doesn't solve it. I'll post on the forum and see if anyone else has this problem.

From: Bill Silverstein: Adding in my two cents worth. I have had On two fresh installs of RC3 on dual core systems with /SMP and /APIC, I had two different results.

On the laptop (Lifebook e8210, core 2 duo), all works fine, but when when using windowed VDMs, dos does not work (but does in full screen) and Windowed Windows vdm gives an error message, but works fine. This uses irqs 0,1,2,4,8,9,12,14,16,and 19.

On the desktop (K4N9 utra, using a separate realtek 8139 card), the sessions think that they are completed. This uses irqs 0,1,2,4,6, 8,9,12,14,16,21, 22, and 23.

As I see, your laptop use PS/2 like mouse which use IRQ12, what a mouse use K4N9 ?

comment:24 Changed 11 years ago by guest

"As I see, your laptop use PS/2 like mouse which use IRQ12, what a mouse use K4N9 ?"

I'm using a PS2 mouse with the k4n9.

comment:25 follow-up: Changed 10 years ago by pasha

Try acpi 3.5 from betazone with /!NOD options

comment:26 in reply to: ↑ 25 Changed 10 years ago by guest

Replying to pasha:

Try acpi 3.5 from betazone with /!NOD options

Okay, VDMs work with /!NOD. But high IRQs are no longer used. Isn't this the equivalent of /PIC mode?

(Also, shouldn't references to acpica.add be removed from the docs?)

-Mike

comment:27 follow-up: Changed 10 years ago by pasha

It is specific in your MB. Using APIC but in low IRQ number

comment:28 in reply to: ↑ 27 Changed 10 years ago by guest

  • Resolution set to fixed
  • Status changed from reopened to closed

Replying to pasha:

It is specific in your MB. Using APIC but in low IRQ number

Cool. Well, it works! :)

Note: See TracTickets for help on using tickets.