|
JPP_ZOSO i beg to differ. i had planned to keep my mouth shut, but i just got notice the beta-testing perod is closed. as one of the beta-testers, v2.01b11 still produced nothing but kernel panics, just logging off the client. manually unmounting netware drives before logging off helped for a day, but then restart and shutdowns would hang, forcing a hard shutdown. manually unmounting netware drives and quitting the client also worked for a day. last kernel panic i got, the same day the final v2.01 was released, was from manually unmounting a netware drive. so now even the work-arounds and troubleshooting methods produce kernel panics. and this is "final" and "leopard compatible". eeesshhhhh. the beta testing period was 2 weeks. for the entire two weeks, each and every day i used the client i got kernel panics from something. the only days that were trouble free was when i used the windoze netware client through boot camp and/or a vm. why our organization clings to novell netware is beyond me. v1.3x of this client worked flawlessly. lacking some features of the windoze and linux clients, but i/we had hopes. v2.00 worked ok under tiger, but it was unreliable, and produced consistent kernel panics just browsing netware drives. v2.00 and v2.01bx under leopard has been horrid. kernel panics left and right. it's understood this is a small niche market, and it's understood not a whole lot of resources are prolly dedicated to this dying platform or client, but if you're gonna release something as "leopard compatible"...and at least one of the beta testers gets nothing but kernel panics even whe following workarounds and troubleshooting methods...i expect either a notification our netware service is setup incorrectly (highly doubtful), or is incompatible w/ this client (maybe), or i expect the beta-testing period to last as long as it needs to to get it right. maybe my case is some weird isolated instance, but i've seen similar reports since v2.00 was released, so i doubt it. (Version 2.0.1) | 
