To install Windows 8 Release Candidate on your PC, the processor (CPU) must support the following features:  Physical Address Extension (PAE), NX, and SSE2.  Most CPUs have support for these features, so if you receive this error, it is likely because the NX feature is not enabled on your system.

 To resolve this error, follow manufacturer guidelines to enable NX (“No eXecute bit”), or the equivalent XD (“eXecute Disabled”), feature within the BIOS settings.  This feature is typically found in the Advanced or Security tabs within the BIOS settings, and can be referred to by a variety of names, including but not limited to:

·        No Execute Memory Protect

·        Execute Disabled Memory Protection

·        EDB (Execute Disabled Bit)

·        EVP (Enhanced Virus Protection)

내 똥컴은 WINDOWS 8 설치가 되지 않는다는  ㅠㅠ     

다른 방법을 찾아야 했다..  가벼운 운영체제..  익숙한 UI .

나름 찾은 방법은 Zorin OS에 XBMC를 얹는 것.  자세한 방법은 하기 글 참조하시고..

2012/10/06 - [분류 전체보기] - ZORIN OS에 XBMC 설치하기

2012/10/06 - [분류 전체보기] - NFTS 파티션 자동 마운트

대체로 만족한다.. 그러나..  아직도 느리다는 느낌을 지울 수가 없기에  구글링을 더 해보았다. 

그러다 찾아낸 물건.   geexbox   이거 정말 물건이다. 

3.0버전에서는 XBMC까지 품었다.  100메가 조금 넘는 용량으로 CD/USB 부팅 혹은 Install 후 바로 사용가능하다. 

A shiny new GeeXboX release has arrived! GeeXboX 3.0 is a major upgrade that integrates XBMC 11 “Eden” and adds the long-requested PVR functionality. This means you can finally use GeeXboX to watch and record live TV too! In addition to our usual x86 ISOs, this release is also available for several embedded platforms, with working full HD video and graphics acceleration for most of them.

A year in the making, this new GeeXboX 3.0 release is the accomplishment of hours, days, months of efforts from a lot of people. The ISO image of “GeeXboX for PC” edition grew up to 140 MB, mostly due to additional firmware and drivers to improve hardware support. We still think of GeeXboX as a lightweight distro, aiming at targeting the most PCs and devices as possible. The whole base system has been overhauled as usual, with countless package upgrades for improved stability and functionality, also benefitting from several improvements to the underlying OpenBricks build system.

GeeXboX also support many embedded devices running ARM SoCs (such as TI OMAP4 Pandaboard, nVidia Tegra 2, Solid-Run Cubox powered by Marvell Armada, ST-Ericsson Snowball), and more will be coming soon. Preliminary support for Toshiba AC100 (Tegra2-based netbook) and Raspberry Pi is already integrated in the development tree.

Here’s a roundup of the new release:

New features:

• XBMC Media Center 11 “Eden” frontend.
• PVR support for DVB Digital TV, to watch and record live TV
• Improved remote control support
• Support for Full HD videos on PandaBoard
• Support for Full HD videos on Cubox
• Improved HDD installation
• Installation support for (U)EFI systems
• Installation support for SSD’s

Supported Architectures:

• x86 32 and 64 bits PCs
• ARM TI OMAP4 Pandaboard
• ARM nVidia Tegra2 Harmony
• ARM Cubox (armada5xx)
• ARM Snowball ux500

System:

• Linux Kernel v3.4.4.
• Systemd v188.
• BusyBox v1.21
• Connman Network Manager v1.6.
• Xorg Server v1.11.4.
• Mesa v8.0.3
• OPKG Package Manager v0.18
• USB persistent user data storage.

Audio Drivers:

• ALSA v1.0.24.1.
• Support for Analog, SPDIF and HDMI output devices.

Video Drivers:

• Support for Intel, nVidia, ATI, Matrox and VIA GPUs.
• Support for CRT, LCD and HDMI output devices.
• OpenGL and OpenGL|ES hardware assisted graphics acceleration.
• VDPAU, VA-API and Crystal HD hardware assisted video decoding for nVidia, Intel and Broadcom GPUs.

Input:

• Mouse and Synaptics touch pads.
• HID Keyboards.
• Remote Controls.
• PluseEight CEC devices.

Networking Features:

• NFS shares.
• Samba auto-discovery.
• UPnP / DLNA media discovery.
• ZeroConf services announcements.
• HTTP server.
• FTP server
• SSH server

MediaCenter:

• XBMC Media Center 11 “Eden” frontend.
• Movies and TV Shows, with subtitles support.
• Music Collection
• Pictures and Slideshows
• CDDA, DVD and (non encrypted) Bluray support.
• Media Database Support.
• Internet MovieDB / TVDB metadata and covers grabbers.
• Skins
• Vu+ addon
• Xvdr addon
• Vdr server
• Tvheadend server

우선 터미널에서 다음 명령을 실행하여 각 ntfs 파티션의 'UUID' 넘버를 알아둡니다.

(UUID란? --> 범용 고유 식별자 Universally Unique Identifier)

 $ ls -l /dev/disk/by-uuid/

위 명령어를 실행하면 다음과 같은 형식으로 출력이 됩니다.

          합계 0

          lrwxrwxrwx 1 root root 10 2008-04-25 23:10 3C986B2F986AE6BC -> ../../sdb1

          lrwxrwxrwx 1 root root 10 2008-04-25 23:10 4E8C66928C66747D -> ../../sdb2

          lrwxrwxrwx 1 root root 10 2008-04-25 23:10 6A3CFD903CFD5791 -> ../../sdc1

          lrwxrwxrwx 1 root root 10 2008-04-25 23:10 7730c540-4605-4d87-88dc-760bb9a37ef5 -> ../../sda3

          lrwxrwxrwx 1 root root 10 2008-04-25 23:10 CC24EA6124EA4E50 -> ../../sda1

          lrwxrwxrwx 1 root root 10 2008-04-25 23:10 E8F85FF8F85FC38A -> ../../sdc2

          lrwxrwxrwx 1 root root 10 2008-04-25 23:10 dc464f65-6885-46e8-a7a0-91960d71ab8c -> ../../sda4

여기서 날짜와 시간 뒤에있는 복잡해보이는 일련번호가 바로 'UUID'입니다.

'sda1' 'sdb2' 등등은 각 파티션의 위치를 가리키는 것이라 보면 되겠습니다.

'sda1' 을 예로 들어 설명하자면, 첫번째 하드디스크의 1번 파티션이라는 의미입니다. 'sdb3'은 두번째 하드디스크의 셋째 파티션을 가리키는 것이겠고요. 즉 뒤에서 두번째에 위치한 알파벳은 하드디스크의 순서이고, 맨 뒤에 붙은 숫자는 파티션의 순서인 것이지요.

이 제 UUID 를 알아냈으므로, 부팅시에 자동으로 마운트를 시켜주는 설정 파일을 편집할 차례입니다.

터미널에서 다음 명령어를 입력하여 실행합니다.

$ sudo gedit /etc/fstab

텍 스트 에디터가 열리면서 'fstab'라는 설정 파일을 불러오게 되겠죠.

저의 경우처럼 ntfs 파티션이 자동으로 마운트되지 않은 상태라면 다음과 같이 리눅스 파티션의 마운트 명령어만이 들어있을 것입니다.

          # /etc/fstab: static file system information.

          #

          # <file system> <mount point>   <type>  <options>       <dump>  <pass>

          proc            /proc           proc    defaults        0       0

          # /dev/sda4

          UUID=dc464f65-6885-46e8-a7a0-91960d71ab8c / ext3  relatime,errors=remount-ro 0  1

          # /dev/sda3

          UUID=7730c540-4605-4d87-88dc-760bb9a37ef5 none      swap  sw      0     0

          /dev/scd0       /media/cdrom0   udf,iso9660 user,noauto,exec,utf8 0     0

여기에 다음과 같은 형식으로 자동 마운트할 파티션의 정보를 추가해서 입력해줍니다.

          UUID=CC24EA6124EA4E50  /media/sda1     ntfs    defaults,umask=007,gid=46 0    1

          UUID=0CF64C51F64C3CE8  /media/sda2     ntfs    defaults,umask=007,gid=46 0   1

주의할 점이라면 각 파티션의 이름(sda1등)과 UUID를 정확하게 일치시켜 주어야 한다는 정도겠네요.

정확하게 입력을 마쳤으면 파일을 저장하고 나옵니다.

그리고 마운트될 디렉토리를 미리 만들어줍니다.

이 작업을 빼먹으면 절대 안됩니다.

$ cd /media /media$ sudo mkdir sda1 sda2 ..........

이 제 리부팅하면 ntfs 파티션들이 만들어준 디렉토리( /media/sda1 등)에 마운트되어 있을 것입니다.

끝으로 한가지 응용을 해볼까요.

파티션을 마운트하는 디렉토리가 꼭 /media/sda1 등의 형식일 필요는 없겠죠.

자신의 편의에 맞춰서 임의의 디렉토리에 마운트한다면 더 편할 것입니다.

저는 저의 홈디렉토리에 마운트시키고, 디렉토리의 이름도 직관적으로 알 수 있도록 만들었더니 아주 편하더군요.

예를 들자면 이런 식입니다.

          UUID=CC24EA6124EA4E50  /home/mojo/xp   ntfs  defaults,umask=007,gid=46 0       1

          UUID=0CF64C51F64C3CE8  /home/mojo/text  ntfs  defaults,umask=007,gid=46 0       1

          UUID=3C986B2F986AE6BC  /home/mojo/backup   ntfs  defaults,umask=007,gid=46 0    1

출 처 : http://mojolog.com/tcb/366

State Variables

I was a bit confusing on state variables. The problem is with my use of them, not with the variables.  The test model only had one integration point.  My code is still not working right, the default USERMAT is overwriting my flag somewhere and I don’t have time to figure it out. It’s killing me but I have to do some real work.    

But anyhow, my assertion that the state variables are per integration point is correct.

Debugging

I am not aware of any way to use a debugger with ANSYS.  There is nothing in the documentation, and to be honest, I’ve not used a real debugger in years.  So there may be a way to do so, and see your routine in the debugger since you have the source code, but I have no idea on how to do that.  Perhaps someone with more debugging experience can comment below.

Other UPF’s

Someone asked about other routines that are available and we ran out of time before I could go over them.  Here is a list.

*DIM,MYCNV,TABLE,3,3,,RPM,X,,1
*taxis,mycnv(1,1),1,0,1000,20.01e6
*taxis,mycnv(1,1),2,0,1,2
mycnv(1,1) = .25,4,10
mycnv(1,2) = .35,7,15
mycnv(1,3) = .45,10,28

*DIM,RPM,TABLE,4,1,1,TIME
RPM(1,0)=0.0,10.0,40.0,60.0
RPM(1,1)=0.0,5.0,20.0,30.0

wrttbl,'mycnv','foo4.txt'
wrttbl, 'rpm','foo5.txt'

SF,ALL,CONV,%mycnv%

This macro is missing stuff, like a model and selecting the nodes to apply the SF command to.

The tables look like this:

Table: mycnv    RPM      vs X       

          | 0.000     1.000     2.000    
          |------------------------------
 0.000    |0.2500    0.3500    0.4500    
 1000.    | 4.000     7.000     10.00    
0.2001E+08| 10.00     15.00     28.00    

and

Table: rpm      TIME     vs         

          |0.7889E-30
          |----------
 0.000    | 0.000    
 10.00    | 5.000    
 40.00    | 20.00    
 60.00    | 30.00  

(We’ll cover the wrttbl macro below.)

So at a given substep, the program will take time and figure out what RPM needs to be.  Then it will use RPM and the radius (X in CSYS 1) to figure out the convection coefficient for each node.

As you can imagine, you can get pretty sophisticated with this. The key is that the name of the table you use for the calculated value is input into the variables to interpolate on for the second table, using the *DIM command.

Another common use is scaling tables based on some value. Let say you have a pressure table and the total pressure is scaled over time, based on time.  You would make a pressure table that is dependent on say X and y. It would have two planes. One with 0 values and one with the max values. Then you would make a scale table that scales from 0 to 1 based on time.  It would look like this:

*DIM,pscl,table,5,,,time    !Row label is CPTAB, the table of Cps
*taxis,pscl(1,1),1,0,1,5,10,30        
pscl(1,1) = .25,.5,1,1,.333

*DIM,ptab,TABLE,4,4,2,X,Y,pscl
*taxis,ptab(1,1),1,0,1.35,2.75
*taxis,ptab(1,1),2,-7.2,-3.2,6.5,10.6
*taxis,ptab(1,1),3,0,1
ptab(1,1,1) = 0,0,0,0
ptab(1,2,1) = 0,0,0,0
ptab(1,3,1) = 0,0,0,0
ptab(1,4,1) = 0,0,0,0
ptab(1,1,2) = 72,48,97,123
ptab(1,2,2) = 53,48,88,98
ptab(1,3,2) = 43,38,77,88
ptab(1,4,2) = 33,28,55,77

SF,ALL,PRESS,%ptab%

As always with tables, double check things and make sure you have your  rows and columns correct.  Start simple, and then add more detail. Testing out on a 2x2 or 3x3 tables is a good way to start.

4 and 5 Dimension Arrays and Tables

Most users will simply use a one, two, or even three dimension array or table (row, column, plane). However, both arrays and tables support two more dimensions: books and shelves. Because this capability is a later addition to the program, it behaves a little differently. You need to add values for the size of the book (KMAX) and the shelf (MMAX) as well as variable names for each: VAR4 and VAR5

The first difference is in the *DIM command. For normal arrays and tables you use:

*DIM, Par, ARRAY, IMAX, JMAX, KMAX, Var1, Var2, Var3, CSYSID 

*DIM, Par, TABLE, IMAX, JMAX, KMAX, Var1, Var2, Var3, CSYSID 

*DIM,Par,ARR4,IMAX,JMAX,KMAX,LMAX,Var1,Var2,Var3,Var4,CSYSID
*DIM,Par,TAB4,IMAX,JMAX,KMAX,LMAX,Var1,Var2,Var3,Var4,CSYSID

For 5 dimension arrays or tables you use: 

*DIM,Par,ARR5,IMAX,JMAX,KMAX,LMAX,MMAX,Var1,Var2,Var3,Var4,Var5,CSYSID
*DIM,Par,TAB5,IMAX,JMAX,KMAX,LMAX,MMAX,Var1,Var2,Var3,Var4,Var5,CSYSID

It is important to be aware of this because if you look at the manual entry for *DIM it only lists the 3 dimension version of the command, and these variations are covered in the notes.

Once the array or table is defined you have to fill it using APDL commands, this size is not supported in the user interface. The same commands are used, but instead of supplying one, two or three indices values, you supply four or five.

The following is an example of defining a table in terms of location (X,Y,Z), Time, and Temperature. This is the most common usage of a five dimension table: 

*dim,ldval,tab5,3,3,3,3,3,X,Y,Z,TIME,TEMP    ! table
*taxis,ldval(1,1,1,1,1),1,-2.3,0,3.4      ! X Range
*taxis,ldval(1,1,1,1,1),2,-1.2,0,1.8      ! Y Range
*taxis,ldval(1,1,1,1,1),3,-3.6,0,4.5      ! Z Range
*taxis,ldval(1,1,1,1,1),4,0,5,10          ! Time Range
*taxis,ldval(1,1,1,1,1),5,32,320,500      ! Temp Range

*do,ii,1,3
  *do,jj,1,3
    *do,kk,1,3
      *do,ll,1,3
        *do,mm,1,3
          !silly made up equation to fill the table with
          ldval(ii,jj,kk,ll,mm) = ii*.123+jj/.2+ll*kk+mm*JJ*JJ
        *enddo
      *enddo
    *enddo
  *enddo
*enddo

Writing a Table to a File

For simple 2D tables with up to 10 columns, I use a cheesy macro I wrote called wrttbl.mac. It was used above.  It is a bit of a brute force method, because it has code blocks for from 0 to 10 columns.  A more general approach would build the actual *VWRITE commands with *VWRITES… It should also be expanded to do Planes.  Maybe for a future article.

Anyhow, here it is, maybe you will find it useful.

ttbl = arg1
fname = arg2     
*get,nrw,parm,%ttbl%,dim,X
*get,ncl,parm,%ttbl%,dim,Y
*get,xax,parm,%ttbl%,var,1
*get,yax,parm,%ttbl%,var,2

nmcl = nint((ncl*10)/2)
nmrw = nint(nrw/2)

*cfopen,%fname%

*vwrite,ttbl,xax,yax
('Table: ',A,' ',A,' vs ',A) 
*vwrite,
(x)
*if,ncl,eq,1,then
    *vlen,1
    *vwrite,%ttbl%(0,1)
    (10x,'|',10g10.4)
    *vwrite
    (10x,'|',10('-'))          |
    *do,ii,1,nrw
        *vlen,1
        *vwrite,%ttbl%(ii,0),%ttbl%(ii  ,1)
        (g10.4,'|',10g10.4) 
    *enddo
*endif
*if,ncl,eq,2,then
    *vlen,1
    *vwrite,%ttbl%(0,1),%ttbl%(0,2)
    (10x,'|',10g10.4)
    *vwrite
    (10x,'|',20('-'))          |
    *do,ii,1,nrw
        *vlen,1
        *vwrite,%ttbl%(ii,0),%ttbl%(ii,1),%ttbl%(ii,2)
        (g10.4,'|',10g10.4) 
    *enddo
*endif
*if,ncl,eq,3,then
    *vlen,1
    *vwrite,%ttbl%(0,1),%ttbl%(0,2),%ttbl%(0,3)
    (10x,'|',10g10.4)
    *vwrite
    (10x,'|',30('-'))          |
    *do,ii,1,nrw
        *vlen,1
        *vwrite,%ttbl%(ii,0),%ttbl%(ii,1),%ttbl%(ii,2),%ttbl%(ii,3)
        (g10.4,'|',10g10.4) 
    *enddo
*endif
*if,ncl,eq,4,then
    /gopr
    *vlen,1
    *vwrite,%ttbl%(0,1),%ttbl%(0,2),%ttbl%(0,3),%ttbl%(0,4)
    (10x,'|',10g10.4)
    *vwrite
    (10x,'|',40('-'))          |
    *do,ii,1,nrw
        *vlen,1
        *vwrite,%ttbl%(ii,0),%ttbl%(ii,1),%ttbl%(ii,2),%ttbl%(ii,3),%ttbl%(ii,4)
        (g10.4,'|',10g10.4) 
    *enddo
*endif
*if,ncl,eq,5,then
    *vlen,1
    *vwrite,%ttbl%(0,1),%ttbl%(0,2),%ttbl%(0,3),%ttbl%(0,4),%ttbl%(0,5)
    (10x,'|',10g10.4)
    *vwrite
    (10x,'|',50('-'))          |
    *do,ii,1,nrw
        *vlen,1
        *vwrite,%ttbl%(ii,0),%ttbl%(ii,1),%ttbl%(ii,2),%ttbl%(ii,3),%ttbl%(ii,4),%ttbl%(ii,5)
        (g10.4,'|',10g10.4) 
    *enddo
*endif
*if,ncl,eq,6,then
    *vlen,1
    *vwrite,%ttbl%(0,1),%ttbl%(0,2),%ttbl%(0,3),%ttbl%(0,4),%ttbl%(0,5),%ttbl%(0,6)
    (10x,'|',10g10.4)
    *vwrite
    (10x,'|',60('-'))          |
    *do,ii,1,nrw
        *vlen,1
        *vwrite,%ttbl%(ii,0),%ttbl%(ii,1),%ttbl%(ii,2),%ttbl%(ii,3),%ttbl%(ii,4),%ttbl%(ii,5),%ttbl%(ii,6)
        (g10.4,'|',10g10.4) 
    *enddo
*endif
*if,ncl,eq,7,then
    *vlen,1
    *vwrite,%ttbl%(0,1),%ttbl%(0,2),%ttbl%(0,3),%ttbl%(0,4),%ttbl%(0,5),%ttbl%(0,6),%ttbl%(0,7)
    (10x,'|',10g10.4)
    *vwrite
    (10x,'|',70('-'))          |
    *do,ii,1,nrw
        *vlen,1
        *vwrite,%ttbl%(ii,0),%ttbl%(ii,1),%ttbl%(ii,2),%ttbl%(ii,3),%ttbl%(ii,4),%ttbl%(ii,5),%ttbl%(ii,6),%ttbl%(ii,7)
        (g10.4,'|',10g10.4) 
    *enddo
*endif
*if,ncl,eq,8,then
    *vlen,1
    *vwrite,%ttbl%(0,1),%ttbl%(0,2),%ttbl%(0,3),%ttbl%(0,4),%ttbl%(0,5),%ttbl%(0,6),%ttbl%(0,7),%ttbl%(0,8)
    (10x,'|',10g10.4)
    *vwrite
    (10x,'|',80('-'))          |
    *do,ii,1,nrw
        *vlen,1
        *vwrite,%ttbl%(ii,0),%ttbl%(ii,1),%ttbl%(ii,2),%ttbl%(ii,3),%ttbl%(ii,4),%ttbl%(ii,5),%ttbl%(ii,6),%ttbl%(ii,7),%ttbl%(ii,8)
        (g10.4,'|',10g10.4) 
    *enddo
*endif
*if,ncl,eq,9,then
    *vlen,1
    *vwrite,%ttbl%(0,1),%ttbl%(0,2),%ttbl%(0,3),%ttbl%(0,4),%ttbl%(0,5),%ttbl%(0,6),%ttbl%(0,7),%ttbl%(0,8),%ttbl%(0,9)
    (10x,'|',10g10.4)
    *vwrite
    (10x,'|',90('-'))          |
    *do,ii,1,nrw
        *vlen,1
        *vwrite,%ttbl%(ii,0),%ttbl%(ii,1),%ttbl%(ii,2),%ttbl%(ii,3),%ttbl%(ii,4),%ttbl%(ii,5),%ttbl%(ii,6),%ttbl%(ii,7),%ttbl%(ii,8),%ttbl%(ii,9)
        (g10.4,'|',10g10.4) 
    *enddo
*endif
*if,ncl,eq,10,then
    *vlen,1
    *vwrite,%ttbl%(0,1),%ttbl%(0,2),%ttbl%(0,3),%ttbl%(0,4),%ttbl%(0,5),%ttbl%(0,6),%ttbl%(0,7),%ttbl%(0,8),%ttbl%(0,9),%ttbl%(0,10)
    (10x,'|',10g10.4)
    *vwrite
    (10x,'|',100('-'))          |
    *do,ii,1,nrw
        *vlen,1
        *vwrite,%ttbl%(ii,0),%ttbl%(ii,1),%ttbl%(ii,2),%ttbl%(ii,3),%ttbl%(ii,4),%ttbl%(ii,5),%ttbl%(ii,6),%ttbl%(ii,7),%ttbl%(ii,8),%ttbl%(ii,9),%ttbl%(ii,10)
        (g10.4,'|',10g10.4) 
    *enddo
*endif

*cfclose