> After enjoying these new features for half an hour it found another WiFi > Router. > The "Notification Balloon" poped up the info and crashed my system - hung. > All is not perfect but it is "working" now.
It _seems_ that I can use WiFi Networking if I do not "use" SXCE. If I let SXCE boot, let WiFi Networking connect, and do nothing else - then all is well. If I try to open Firefox 3.0.3 (with 30 tabs saved to re-open) then SXCE crashes. I am guessing that there exists some type of memory conflict. I have 3GB of memory and do not have crashes if I use "Wired" Networking. Initially, my vote is to blame the Driver. It is difficult to say if there is a "bug" in the Driver _or_ if my "illegal" use of an OpenSolaris / Solaris Driver in SXCE is to blame. I have used Solaris 10 Drivers in SXCE and OpenSolaris before with great results. The Driver's Installer _ought_ to refuse to install into the "wrong" Operating System if it is "not possible" to do so. A review of the Logs has not disclosed what went wrong, my guess is that "it crashes so badly" that it "can not write a goodbye message". I like that way Slackware Linux holds it's "Panic Message" on the screen and if you hit the Power Button (for less than 2 seconds) then Slackware shuts down in an orderly manner (writing Logs as it goes). This is a "really bad crash", if you are using SXCE and blink (or turn your head) for a moment then the next thing you see is the BIOS boot message - there is no "proper shutdown" with this type of crash. I will Google to see if there is a way to catch this type of termination. With the exception of this one fatal flaw the Driver seems to work correctly and I would have a great report if it were not for the "instant reboot crash issue" (when you try to use some memory). Rob -- This message posted from opensolaris.org
