Jim Lawrence
accessd at shaw.ca
Tue Jun 26 23:11:56 CDT 2012
Hilarious, in a sort of twisted way. We knew authentication was coming and now its here. I have some concerns with later versions of windows as they may not accept third-party software unless it is appropriately vetted through the correct channels (translation; higher costs). These issues will rarely affect a good hundred percent Windows shop but for those of us who mix various applications depending on our requirements, we may be in for a rough ride. Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Tuesday, June 26, 2012 8:53 PM To: Access Developers discussion and problem solving Subject: [AccessD] OT: The things we have to do / know / figure out I installed a driver for my Areca RAID controller on my Windows 2008R2 server. It seems that the driver was unsigned. The next time I booted it refused to boot saying that the driver is unsigned. I have never run into this before. It cannot be worked around. There is a selection in the boot menu to disable driver signing but that only works for that boot cycle. Thus in order to boot one has to hit F8 and select that menu item whereupon the system boots (that cycle). The "accepted practice" is to use this to uninstall the unsigned driver. PERIOD! Uhhh excuse me but I need my RAID system. Anyway after some googling, it appears that there is a "test mode" and a third party app that will "sign" the driver with an unauthenticated signature file which only works in "test mode". So an hour later I am booting again but in "test mode" whatever that may be. -- John W. Colby Colby Consulting Reality is what refuses to go away when you do not believe in it -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com