Enlight Cases/BE6ll

----snip----

Umm, I didn't have a problem, I was just posting that I didn't have any
problems with a BE6-II and an Enlight 7237 because the original poster asked
if any one had that combination working ok. I don't think the original
poster's problem had anything to do with VXDs because by the sound of it his
machine wasn't even getting through the POST until he reset it.

Matt.

No problem with my enlight 7237 w/300W

My System
Enlight 7237 Case with 2 extra fans 300W Power supply
Abit BE6-II Q J BIOS 1/17/2000
PIII 500@620(5X124)(2.1vdc)
256 MB PC-100 SDRAM 128 X 2 Micron
 IBM Deskstar 34GXP 20.5G 7200RPM (IDE 3/M)
 Iomega Zip drive (IDE 1/S)
Sony 40X CDU-4011 (IDE 2/M)
Acer 4432A CDRW (IDE 2/S)
3dfx Voodoo3 3500 16MB AGP video card
SB Live Value (Liveware3.0)(PCI 4)
Cambridge FPS2000 Digital 4 Point speaker system
USR Sportster 56K V.90 V/F/D internal(ISA 1)
Standard Floppy
Standard windows keyboard
Logitech Mouseman wheel USB
Saitek X36 USB Flight control system
Compaq V70 Monitor (16bpp 1024x768)
HP DeskJet 932C USB printer
Plustek Opticpro 9636T Scanner LPT1
SIIG 4000P USB port
Creative Labs WebCam Go USB
Cyberpower 500VA UPS (Com 1)

--
Regards
Renegade
reneg @interacs.com

thanks for the responses....i will try another BE6ll motherboard this week....

  I have had several issues with this combination relating to
grounding probs.  I have only had these problems however with the
newer revision of the 7237 (one with removable sides).  In both cases
I was able to fix the probs without replacing the case.  Here is some
of a previous post dealing with this issue.
  Scott

I do not have the case, but have the same problem with two identical systems of
BE6-II and Cel2 566@850.  I  99.9% doubt it's my midtower antec cases.  I have
tried 3 different power supplies (two 250watt and one 300watt) with same problem.
They especially hang at startup when they have been on for fifteen or more minutes
and I shutdown and restart within five minutes.  I have "QJ" bios.  It does this
with the bare essentials of PC133ram, and Video installed as well.   I have not
played with it much, but I think I'll first update win98 (since they are fresh
installs) and if it persist, I may put ACPI to "disabled" in the bios.  I've been
following this NG lately for any other suggestions.  I just wanted to relate that I
am experiencing similiar problems.  I've heard from the tech support where I bought
this MOBO that Win98 SE has been giving the BE6-II problems.  I suspect the BIOS
and ACPI conflicts with Win98 SE base on his info at this point

thanks for responding...i have another BE6ll motherboard coming.....im gonna
try it and see what happens......

I have an Enlight 7237 case with 250W power supply and a BE6-II and have no
problems with it.

Matt.

Your setup looks good on the PCI and AGP usage.  You might have to do a process of
elmination to see which component is causing the hang.  Start with the basics CPU,
Video, Memory, Keyboard and Floppy and try to boot.  If it still hangs then reseat
everything and try again.  Make sure all the cables and wires are connected good.

 Enlight 7237 with 300 watt PS & BE6 II here with no problems.

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----==  Over 80,000 Newsgroups - 16 Different Servers! =-----

did you try ACPI turned off?

Matt,  Windows98 is designed so that if it runs into trouble booting it trys
to find ways around the trouble if it can. Most likely your problem lies
with a Vxd file.
I am assuming this is not happening during setup because that procedure is
different.  I would try to hit F8 and bring up the boot menu.  Choose Logged
(bootlog.txt) and see if you can read which file is causing the trouble.  It
will log two boots (1st time is bootlog.txt, 2nd time bootlog.txt is renamed
to bootlog.prv and a new bootlog.txt is created.  Use notepad or wordpad to
compare them.  Besides looking for a difference and failure in one and not
the other, take a look at a section named SYSCRITINIT (critical system
drivers).  The initialization (or lack thereof) of each non-SYSCRITINIT
driver is recorded as it occurs.  If Bootlog.txt does not record any
SYSCRITINIT entries, then at least one VxD has failed.  If you want to
determine which failed, you must add LogSysCritInit=1 to the [386enh]
section of System.Ini. This forces the VxDs to display individually at the
top of the screen.  You can hit the ESC key to bypass the logo so you can
see this.  Typically you will see SYSCRITINITSUCCESS=SHELL since Shell is
the last VxD.  If a VxD is causing the problem, the culprit will show
instead.

Once you deterimine which one it is, you will have to search for the true
cause and cure.  It could be duplicate files, missing files, corrupted
files, or configuaration errors from prior devices or setup issues.

sk