KernelEx? (with full info of what did not work)

The available list for the Anapa is:
VBE miniport ---choose this one

VBE miniport - Standard Graphics Adaptor (VGA) ???
VBE miniport - Standard PCI Graphics Adaptor ??? -- or this?
VBE miniport - Standard PCI Graphics Adaptor (VGA) ???
VBE miniport - Standard PCI Graphics Adaptor (XGA) 1024x768
VBE miniport - SVGA 800x600
VBE miniport - VGA 640x480
It is the SVGA option i use now.
So, what do you recommend?

I haven't used it myself, but what I understand of it
you should use the first one that only say VBE miniport.
I don't understand the other ones, since talking VESA
there should only be one (except for possibly
VGA and SVGA that are there if you temporarly want
to communicate the old standard-ways before vesa)?

On the other hand, he mentioned at the pages something
about if one doesn't work - try the next, so perhaps
they are there for cards that need special treatment.

hmm... if you look in the vbemp.inf file there is these lines:

%AnaPa.DeviceDesc% = Driver.Install, NOPNP
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc1% = Driver.Install, PCI\CC_0300
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc2% = Driver.Install, PCI\CC_0301
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc3% = Driver.Install, PCI\CC_0380
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc4% = Driver.Install, *PNP0900
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc5% = Driver.Install, *PNP0917
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc6% = Driver.Install, NOPNP

so it seems to be if the card is plug-and-play or not?

AnaPa.DeviceDesc = "VBE Miniport" -----not PnP?
AnaPa.DeviceDesc1 = " - Standard PCI Graphics Adapter (VGA)"
AnaPa.DeviceDesc2 = " - Standard PCI Graphics Adapter (XGA)"
AnaPa.DeviceDesc3 = " - Standard PCI Graphics Adapter"
AnaPa.DeviceDesc4 = " - Standard Graphics Adapter (VGA)"
AnaPa.DeviceDesc5 = " - VGA"
AnaPa.DeviceDesc6 = " - SVGA"


Somehow I get a feeling that you should not have got that
list at all during install, windows should have selected
the correct one automaticly (and don't select "show list"
but keep it at "search after")

It is the SVGA option i use now.

hmmm... in the screenshot
http://bearwindows.boot-land.net/w98-1.png
they seems to have selected this:

VBE miniport - Standard PCI Graphics Adaptor (VGA)

and that seems to work fine in 1024x768 truecolor
so hehe... don't ask me, I will probably guess wrong :-)
If neither of them work when you try them and not the
old 'manual' version with nvidia either, then you better
ask the programmer. check the 'Driver troubleshooting'
section at the webpage too then

It is the SVGA option i use now.

hmmm... in the screenshot
http://bearwindows.boot-land.net/w98-1.png
they seems to have selected this:

VBE miniport - Standard PCI Graphics Adaptor (VGA)

and that seems to work fine in 1024x768 truecolor
so hehe... don't ask me, I will probably guess wrong :-)
If neither of them work when you try them and not the
old 'manual' version with nvidia either, then you better
ask the programmer. check the 'Driver troubleshooting'
section at the webpage too then

MEB wrote:
Try using Dependency Walker [2.0 or higher] and use the "profile" option
while attempting the installation from within Dependency Walker. Check the
help supplied with the program for more information..
For profiling to work, the module you open in Dependency Walker has to be an
executable file.
Otherwise, you can click on [open] the various files within the target
[what you want to check] and it will attempt to resolve the dependencies
using the present system files.

*IF* these are drivers related to the motherboard [or other devices] and
designed for 2000/XP/VISTA, you will not get them to work with 9X by using
the mod.
These are designed for HAL and other aspects of the NT environment.

The kernel mods are designed to allow some *applications* to work in the 9X
environment.

Dependency Walker is awesome!
Now all i have to do is find the time to impliment a "special" patch
that i have in mind that should fix a lot of problems.

MEB wrote:
Try using Dependency Walker [2.0 or higher] and use the "profile" option
while attempting the installation from within Dependency Walker. Check the
help supplied with the program for more information..
For profiling to work, the module you open in Dependency Walker has to be an
executable file.
Otherwise, you can click on [open] the various files within the target
[what you want to check] and it will attempt to resolve the dependencies
using the present system files.

*IF* these are drivers related to the motherboard [or other devices] and
designed for 2000/XP/VISTA, you will not get them to work with 9X by using
the mod.
These are designed for HAL and other aspects of the NT environment.

The kernel mods are designed to allow some *applications* to work in the 9X
environment.

Dependency Walker is awesome!
Now all i have to do is find the time to impliment a "special" patch
that i have in mind that should fix a lot of problems.

teebo wrote:
The available list for the Anapa is:
VBE miniport ---choose this one

VBE miniport - Standard Graphics Adaptor (VGA) ???
VBE miniport - Standard PCI Graphics Adaptor ??? -- or this?
VBE miniport - Standard PCI Graphics Adaptor (VGA) ???
VBE miniport - Standard PCI Graphics Adaptor (XGA) 1024x768
VBE miniport - SVGA 800x600
VBE miniport - VGA 640x480
It is the SVGA option i use now.
So, what do you recommend?

I haven't used it myself, but what I understand of it
you should use the first one that only say VBE miniport.
I don't understand the other ones, since talking VESA
there should only be one (except for possibly
VGA and SVGA that are there if you temporarly want
to communicate the old standard-ways before vesa)?

On the other hand, he mentioned at the pages something
about if one doesn't work - try the next, so perhaps
they are there for cards that need special treatment.

hmm... if you look in the vbemp.inf file there is these lines:

%AnaPa.DeviceDesc% = Driver.Install, NOPNP
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc1% = Driver.Install, PCI\CC_0300
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc2% = Driver.Install, PCI\CC_0301
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc3% = Driver.Install, PCI\CC_0380
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc4% = Driver.Install, *PNP0900
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc5% = Driver.Install, *PNP0917
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc6% = Driver.Install, NOPNP

so it seems to be if the card is plug-and-play or not?

AnaPa.DeviceDesc = "VBE Miniport" -----not PnP?
AnaPa.DeviceDesc1 = " - Standard PCI Graphics Adapter (VGA)"
AnaPa.DeviceDesc2 = " - Standard PCI Graphics Adapter (XGA)"
AnaPa.DeviceDesc3 = " - Standard PCI Graphics Adapter"
AnaPa.DeviceDesc4 = " - Standard Graphics Adapter (VGA)"
AnaPa.DeviceDesc5 = " - VGA"
AnaPa.DeviceDesc6 = " - SVGA"


Somehow I get a feeling that you should not have got that
list at all during install, windows should have selected
the correct one automaticly (and don't select "show list"
but keep it at "search after")
1) The BAERstuff was exactly what i had (Anapa).
2) Oh yes, WinDoz did select what it "thought" was the correct one -
the VGA driver with only 16 colors. So i had to go into the list and
select the SVGA driver.
3) Video card is supposedly PnP but since two "motherboard resources"
etc are not satisfied, it is a wonder the card works at all.
Will try the "plain" (not PnP) driver.

teebo wrote:
The available list for the Anapa is:
VBE miniport ---choose this one

VBE miniport - Standard Graphics Adaptor (VGA) ???
VBE miniport - Standard PCI Graphics Adaptor ??? -- or this?
VBE miniport - Standard PCI Graphics Adaptor (VGA) ???
VBE miniport - Standard PCI Graphics Adaptor (XGA) 1024x768
VBE miniport - SVGA 800x600
VBE miniport - VGA 640x480
It is the SVGA option i use now.
So, what do you recommend?

I haven't used it myself, but what I understand of it
you should use the first one that only say VBE miniport.
I don't understand the other ones, since talking VESA
there should only be one (except for possibly
VGA and SVGA that are there if you temporarly want
to communicate the old standard-ways before vesa)?

On the other hand, he mentioned at the pages something
about if one doesn't work - try the next, so perhaps
they are there for cards that need special treatment.

hmm... if you look in the vbemp.inf file there is these lines:

%AnaPa.DeviceDesc% = Driver.Install, NOPNP
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc1% = Driver.Install, PCI\CC_0300
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc2% = Driver.Install, PCI\CC_0301
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc3% = Driver.Install, PCI\CC_0380
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc4% = Driver.Install, *PNP0900
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc5% = Driver.Install, *PNP0917
%AnaPa.DeviceDesc%%AnaPa.DeviceDesc6% = Driver.Install, NOPNP

so it seems to be if the card is plug-and-play or not?

AnaPa.DeviceDesc = "VBE Miniport" -----not PnP?
AnaPa.DeviceDesc1 = " - Standard PCI Graphics Adapter (VGA)"
AnaPa.DeviceDesc2 = " - Standard PCI Graphics Adapter (XGA)"
AnaPa.DeviceDesc3 = " - Standard PCI Graphics Adapter"
AnaPa.DeviceDesc4 = " - Standard Graphics Adapter (VGA)"
AnaPa.DeviceDesc5 = " - VGA"
AnaPa.DeviceDesc6 = " - SVGA"


Somehow I get a feeling that you should not have got that
list at all during install, windows should have selected
the correct one automaticly (and don't select "show list"
but keep it at "search after")
1) The BAERstuff was exactly what i had (Anapa).
2) Oh yes, WinDoz did select what it "thought" was the correct one -
the VGA driver with only 16 colors. So i had to go into the list and
select the SVGA driver.
3) Video card is supposedly PnP but since two "motherboard resources"
etc are not satisfied, it is a wonder the card works at all.
Will try the "plain" (not PnP) driver.

teebo wrote:
It is the SVGA option i use now.

hmmm... in the screenshot
http://bearwindows.boot-land.net/w98-1.png
they seems to have selected this:

VBE miniport - Standard PCI Graphics Adaptor (VGA)

and that seems to work fine in 1024x768 truecolor
so hehe... don't ask me, I will probably guess wrong :-)
If neither of them work when you try them and not the
old 'manual' version with nvidia either, then you better
ask the programmer. check the 'Driver troubleshooting'
section at the webpage too then
I tried the "plain" (no PnP) driver and picked hires 16 bit (did not
have guts for hivid 24 bit) and.... it works!
Thanks!

teebo wrote:
It is the SVGA option i use now.

hmmm... in the screenshot
http://bearwindows.boot-land.net/w98-1.png
they seems to have selected this:

VBE miniport - Standard PCI Graphics Adaptor (VGA)

and that seems to work fine in 1024x768 truecolor
so hehe... don't ask me, I will probably guess wrong :-)
If neither of them work when you try them and not the
old 'manual' version with nvidia either, then you better
ask the programmer. check the 'Driver troubleshooting'
section at the webpage too then
I tried the "plain" (no PnP) driver and picked hires 16 bit (did not
have guts for hivid 24 bit) and.... it works!
Thanks!

On 06/18/2009 04:51 AM, Robert Baer wrote:
MEB wrote:
Try using Dependency Walker [2.0 or higher] and use the "profile" option
while attempting the installation from within Dependency Walker. Check
the
help supplied with the program for more information..
For profiling to work, the module you open in Dependency Walker has to
be an
executable file.
Otherwise, you can click on [open] the various files within the target
[what you want to check] and it will attempt to resolve the dependencies
using the present system files.

*IF* these are drivers related to the motherboard [or other devices] and
designed for 2000/XP/VISTA, you will not get them to work with 9X by
using
the mod.
These are designed for HAL and other aspects of the NT environment.

The kernel mods are designed to allow some *applications* to work in
the 9X
environment.

Dependency Walker is awesome!
Now all i have to do is find the time to impliment a "special" patch
that i have in mind that should fix a lot of problems.

Good, glad you picked up on it, thought you were going to ignore the
recommendation..

Wonderful graphic debug style program for the 9X [32bit] environment,
I used it during many years of testing and code manipulation... simple
and quick, yet elegant and informative, and requires no real coding
experience so anyone can become a tester, though it is certainly useful
even to coders/programmers... great for bug reports/files and other aspects.

Keep us informed, we are always interested in efforts to support 9X.
I think the prior issues in the group pertaining to 9X modifications
ended, for the most part, with the end of support/end of life and
certainly as its now three years later, so if you know of other reliable
coders/programmers working on keeping it viable or fixing issues or
creating programs/applications, invite them to the forum. You can see
the number of interested parties [e.g., MVPs and long term posters, and
resultant mirrored materials].
Moreover, I seriously doubt there can be much argument to be leveraged
for NOT posting suggestions, modifications [links], and/with testing and
results, within the forum, even by the MVPs; perhaps they might even
help with their cumulative knowledge.

In fact that might spark others to also work on/within the now stable
9X coding environment.

--
~
--
MEB
http://peoplescounsel.org/ref/windows-main.htm
Windows Diagnostics, Security, Networking
http://peoplescounsel.org
The *REAL WORLD* of Law, Justice, and Government
_______