 |
 |
 |
Route Map of Continental Micronesia |
||
 |
 |
 |
星期二, 十一月 10, 2009, 22:36 ;) [ 发表评论 ] | [ 0 trackbacks ] | permalink |    ( 2.9 / 21 ) |
||
 |
 |
 |
|
|
|
intel 855GM with windows 7 |
||
|
|
|
星期六, 十月 24, 2009, 01:53 The W7 will automatically assign the standard VGA driver for 855GM and only allows maximum resolution to 1024x768.
Several solutions can be found online. 1.Install 8XXGM Series Video Driver on Windows 7 - Tutorial Tested with 855GM Chipset By Lexxion here 2.specific driver for 855GM under W7, one can be found here 3.(This one is simple and works for me) here As this thread comes up first when you google for this problem I thought I would register and provide the solution to the problem here... edit: The above method only works if the external monitor is attached. Otherwise BSOD occurs. You asked, and I can deliver. The 0x7E STOP blue screen is occuring due to the new boot animation in Windows 7 which runs at 1024x768 and the crash occurs when the resolution changes at the end of that (since the driver was written when no resolution change occurred then). Strangely it only crashes if an external monitor isn't attached. So if you avoid the new boot animation that forces the old boot VGA resolution (640x480) that the driver can handle, and the blue screen doesn't occur. That can be achieved by running msconfig and checking Boot->OS boot information. Instead of the animation you now get text showing driver loads and the 0x7E STOP blue screen is avoided. And now you don't need an external monitor connected each time you reboot. Final solution: A. Turn off Digital Driver Signing Check cmd.exe->Run as administrator-> type bcdedit /set nointegritychecks ON bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS Reboot in safe mode (press F8 repeatedly during the BIOS screen). B.Installing the XDDM Vista Driver C.to disable the start up screen which forces a certain resolution and default graphics drivers ("running msconfig and checking Boot->OS boot information. Instead of the animation you now get text showing driver loads and the 0x7E STOP blue screen") gpedit.msc->navigate to: User Configuration -> Administrative Templates -> System -> Driver Installation and enable the "Code signing for drivers" and then choose "Ignore"." [ 发表评论 ] | [ 0 trackbacks ] | permalink | ( 3.1 / 31 ) |
||
|
|
|
|
|
|
Frequent Flyer |
||
|
|
|
星期三, 十月 21, 2009, 23:30 Frequent Flyer from Gabriel Leigh on Vimeo. [ 发表评论 ] | [ 0 trackbacks ] | permalink | ( 3 / 51 ) |
||
|
|
|
|
|
|
AA gogo inflight wifi |
||
|
|
|
星期五, 十月 16, 2009, 06:42 I am posting from my HTC touch pro2 over the 30k feet sky on AA flight. The gogo inflight wifi is great. With the free promotion is even better. :)[ 发表评论 ] | [ 0 trackbacks ] | permalink | ( 3 / 72 ) |
||
|
|
|
|
|
|
ODBC for 64-bit windows??? |
||
|
|
|
星期一, 七月 13, 2009, 01:28 ODBC, stands for Open Database Connectivity.
If you are switching windows system from 32bit to 64bit, and you are using ODBC, you will get this error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified. There are two ODBC administrators in a 64bit computer: ODBC 32bit is placed in c:windowssyswow64odbcad.exe
and ODBC 64bit version is placed in c:windowssystem32odbcad32.exe
(default for administration tool). In order to use ODBC, you can change the shortcut in administration tool(from control panel) to the 32bit one (in SysWOW64 folder). Note for Matlab: It is not possible to connect to a Microsoft Access database which is a 32-bit application with 64-bit MATLAB. Due to a general limitation of ODBC drivers, 64-bit MATLAB (or any 64-bit application) cannot interact with 32-bit ODBC drivers. The easiest way is to install 32-bit MATLAB on 64-bit machine. Solution from Mathworks [ 发表评论 ] | [ 0 trackbacks ] | permalink | ( 3 / 462 ) |
||
|
|
|
|
|
|
compile fortran openmp code with O3 switch |
||
|
|
|
星期二, 七月 7, 2009, 19:04 Strange stuff happens with the -O3 switch on
e.g. ifort -openmp -O3 -o test test.f90 w/o -O3 or with -O2, the code works, can't figure out yet. Also recommend a parallel code debugger, Totalview (available under Linux). Useful when looking into details of each thread, variable. Can do evaluation (print out variable, if this is what you usually do to debug) at any point during the process, without recompile your code. [ 发表评论 ] | [ 0 trackbacks ] | permalink | ( 3 / 466 ) |
||
|
|
|
|
|
|
new weapon |
||
|
|
|
星期二, 七月 7, 2009, 19:02 build a new system with i7
CPU: i7 920 2.66GHz (not yet OC) Mem: OCZ DDR3 1600MHz 12GB MO : EVGA X58 SLI 758 Installed Win2008 Server HPC edition. Now happy to fight those heavy computation. [ 发表评论 ] | [ 0 trackbacks ] | permalink | ( 3 / 459 ) |
||
|
|
|
|
|
|
Install Windows 7 (ISO) from USB Flash Drive |
||
|
|
|
星期三, 七月 1, 2009, 11:16 Requirement:
USB Pen Drive (Min 4 GB) Windows 7 ISO (32 bit or 64 bit) MBRwiz Download and Extract it on your hard drive (Diskpart utility for Windows XP doesn’t detect USB drive as Disk hence we need to use this free utility to make bootable USB drive). Steps: 1. Format USB Flash Drive 2.Now go to Start Menu->run->cmd (Open Command Prompt) and Type following command convert i: /fs:ntfs (Where “I” is your USB drive latter) 3.(optional, if your usb drive is already active. you can check with MBRwiz /list) In command window, dir to directory where you have extracted MBRWiz and run following commands mbrwiz /list (note down disk number of your USB Pen drive) mbrwiz /disk=X /active=X (X is Disk Number of your USB Drive) 4.Mount Windows 7 iso as drive. In command window, type following command J: (Drive letter of Windows 7 iso mounted with demon tool) CD boot bootsect /nt60 Y: (Y is drive latter of your USB drive ) (if your current OS system is 32bit, you can only try this with 32bit win7, since your system can not run 64bit exe. Then you need a 32bit win7.) 5.Now copy all files from drive where you have mount Windows 7 iso. Done [ 发表评论 ] | [ 0 trackbacks ] | permalink | ( 3 / 510 ) |
||
|
|
|
Next