달력

11

« 2024/11 »

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30

싸이월드에서 또 삽질을 하고 있는 것 같습니다.

즉, 그리드 컴퓨팅의 클라이언트 프로그램으로 각 개인의 PC가 싸이월드 사의 서버 역활을 해줌으로써 싸이월드는 시스템 투자 비용을 줄일 수 있지만 대신 일반사용자의 PC는 만성적으로 버벅대는 성능 손실을 초래하게 되는 것이지요.

당근 이건 BGM설치시 경고문구 내지는 약관을 통해서 명시해 두기는 했지만, 보통 지나치는 경우가 많지요.

결과론적으로 다음 프로그램을 다운로드 받아서 실행시켜 주면 자신의 컴퓨터에 몰래 설치되어 있는 프로그램을 삭제할 수 있다.

http://cyimg8.cyworld.nate.com/cymusic/package/cyplayer_uninstall.exe


이제 정상적인 컴퓨터 성능과 인터넷 속도가 나오는지 확인해보자!!


오랜만에 피시 견적 요청을 할려고 윈도우즈로 부팅하여 다나와에 들어갔습니다.

백신 프로그램 설치하여 항상 바이러스 대비를 철저히 하고 있지만, 그래도 가끔은 바이러스에 걸리는 경우가 있어 걍 밀어버리고 윈도우 설치이미지로 다시 설치할 수 있는 비상체제는 항상 준비되어 있습니다.

그래도 평상시에 깔끔하게 유지해 주는게 짜증을 줄일 수 있는 지름길입니다.

된장 그런데,,,,,,,,

윈도우즈 익스플로러 7 탭1개만 열었을 뿐인데 절대 죽지 않습니다.

시스템이 맛탱이 갔나?

바이러스를 체크해봅니다.

알약도 못찾는 바이러스가 있다던데 다른 백신 프로그램을 설치해야 하나?

v3, 노턴, 맥아피 설치해서 검색, 지우고 다른걸로 깔고 검색, 지우기 반복해서 검색하여 보았지만 바이러스 없었습니다.

도대체 백신 몇 종 세트를 준비해야 하는걸까요?

이런 고물스러운 시스템을 그동안 어떻게 사용해 왔었는지 괴기스럽습니다.

몇번이고 어플리케이션을 중단시키려고 시도하였지만, 그럼에도 절대 안죽습니다.

더운데 이것까지 맘대로 되질 않으니 열 받았습니다.


하는 수 없습니다.

업무용이라면 백업데이타나 설치CD를 이용하여 복구하겠지만, 재설치해도 문제없는 시스템이라 간단하게 처리하기로 하였습니다.

TaskInfo라는 툴을 이용해서 강제로 죽였습니다.


덥고 짜증나는데 인터넷 익스플로러까지 말썽입니다.

그래서, 맥이나 리눅스계열 페도라, 우분투를 사용할 수 밖에 없는 것 같습니다,,,,,,,

참고로 실시간으로 시스템에 접속되어 있는 IP주소를 확인하는 방법입니다.


:
Posted by Ritz®™

출처 : http://gold.textcube.com/10

윈도 비스타 부터는 XP와 달리 USB 메모리를 이용한 설치를 지원하고 있어 USB 메모리를 부팅 가능하게 만든 다음 필요한 파일들을 복사만 하면 윈도 설치가 된다. 문제는 USB 메모리를 이용한 XP의 설치다. 그러던 중 한 블로그에서 설치 파일 생성에 관해 내용을 보고 이 글을 작성한다.

○ 준비물 : 윈도 설치 CD, USB 메모리

○ 드라이브 현황 : CD-ROM : E 드라이브, USB 메모리 : F 드라이브

1. USB 메모리를 부팅 가능하게 만들기

가. 아래 링크된 페이지에서 스텝 1에서 4까지 함.

http://www.hiren.info/pages/bootcd-on-usb-disk

나. boot.lst는 아래 첨부파일로 대체

#boot.lst

#윈도 7 설치

title Install Windows 7

find --set-root /bootmgr

chainloader /bootmgr

#윈도 XP 설치

title Install Windows XP

find --set-root /NTLDR

chainloader /NTLDR

2. XP 설치 파일 준비

가. XP 설치할 때 보면 설치 파일들을 하드디스크로 복사하는 과정이 있는데 아마도 이 과정을 통해서 필요한 파일들을 추출하는 것 같음.

나. 한번 만들어진 설치파일은 복사해서 다른 USB 메모리에서 사용 가능함.

다. 이 명령은 XP에서 실행해야 함.

라. 임시 설치파일 생성 명령

1) E:\i386\winnt32 /noreboot /makelocalsource /tempdrive:F /syspart:F

   2) 위 명령을 굳이 풀어보면 F 드라이브에 윈도XP를 설치할 건데 리부팅은 하지 말고 설치파일만 복사하라로 해석됨.

   3) 결과

명칭

비고

$WIN_NT$.~BT

폴더

$WIN_NT$.~LS

폴더

bootfont.bin

ntdetect.com

NTLDR

txtsetup.sif

자동설치용 파일로 안 생길 수 있음.

3. Windows 7 설치 파일 복사

설치 DVD에 있는 boot, source, bootmgr 등을 USB 메모리(F:)로 복사.

4. 설치할 컴퓨터에서 USB 부팅으로 설정하고 설치. 끝.

○ 참고 : http://blogdoc.nate.com/368435

:
Posted by Ritz®™

alc888_dump.txt





Ubuntu나 페도라등 리눅스에서 사운드카드 코덱 덤프 받는 방법입니다.

Linux로 부팅하고 난 후, 다음과 같은 명령어를 입력합니다.

<code>cat /proc/asound/card0/codec#1 > ~/Desktop/codec_dump.txt

</code>

:
Posted by Ritz®™

The Alternatives

Users with ATI cards basically have these options:

  1. Open Source Drivers These are stable and nice, but currently have poor 3D performance, if any. If you have a Radeon X1k product or earlier, this is your only option.
  2. The Ubuntu Way Use the restricted-driver management system that comes with Ubuntu to install the drivers.
  3. Third (Fourth?) Party Installer Use envy/jockey or other installer helper.
  4. Install the drivers manually Using the installer downloaded from AMD's site via either package based install or direct install.

[edit] Open Source Drivers

By default, Ubuntu will already try to use one of the open source drivers for your hardware. If the feature set and stability work for you, then you don't need to change anything.

The drivers that may be used are

  • vesa Lowest common denominator across all graphics vendor, not many features.
  • ati Actually a facade that will invoke the radeon driver.
  • radeon Driver support all radeon classes of hardware - with limited 3D for newer cards.
  • radeonhd An alternate driver support R520 hardware and later.

By default there is no configuration file for X anymore, so X will try to do the right thing.

If you run into stability problems with 3D applications using the radeon/radeonhd drivers, consider trying a more recent kernel. mainline-2.6.29.3 did the trick on a few machines.

There's an ongoing debate about how and if the radeon and radeonhd drivers will be used in the future.

[edit] The Ubuntu way

[edit] Restricted Drivers Manager

  • Ubuntu 9.04 (Jaunty) provides a notification saying that there are restricted drivers available
  • Go to the Restricted Drivers Manager and enable the "ATI accelerated graphics driver"
  • Ubuntu will then install and configure the driver for you

Note that you will be restricted to the drivers for you version of Ubuntu that Canonical deem as stable. This may not give you the latest drivers, but should be safest.

[edit] Installing the drivers manually

  • PLEASE READ FIRST!

This portion of the guide works, since I have used it myself. I guess the rest of the guide is broken or it may be because the new driver doesn't support any of the older ATI cards anymore. Which cards does ATI no longer support? The ATI Radeon 9500-9800,X300-X2100,Xpress. See the complete list [1] here.If your card is on that list, you are restricted to the 9.3 driver - however since 9.3 driver doesn't support xorg-xserver 1.6, it will not work with Jaunty! This guide currently is for installing 9.4. !!!SO BE CAREFUL!!!

_______________________________________________

I recommend using copy and paste. However, you can Ctrl + C in your browser but you cannot Ctrl + V in the terminal. When you have copied something simply use Shift + Insert to paste into the terminal or go to the terminals menu, select edit and click paste. This method will ensure there are no typing mistakes and will greatly speed up the install process.

If you are using the x86_64 architecture (64 bit), be sure to install "ia32-libs" before proceeding!

Make sure universe and multiverse are enabled in your repository sources.

[edit] Before you start

Install the necessary programs

Terminal Command

sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms

[edit] 1. Download the latest Catalyst package.

Download page: Catalyst 9.4. This package contains both the 32-bit and 64-bit driver.

Open a terminal window and switch to the directory you downloaded the installer to. (Example: $ cd Desktop)

Make sure your directory path does not contain spaces

[edit] 2. Create .deb packages.

Terminal Command

sh ati-driver-installer-9-4-x86.x86_64.run --buildpkg Ubuntu/jaunty

[edit] 3. Just in case

Write down or remember this series of Alt+PrntScr key combinations, just in case your screen should go black and Ctrl+Alt+F1 and Ctrl+Alt+Backspace doesn't work.

Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b

These keypresses will reboot the system safely. To remember the keypresses, remember this nonsensical phrase: "Raising Skinny Elephants Is Never Utterly Boring"

[edit] 4. Install .debs.

Install the debs, depending on if you're on a 32-bit or 64-bit system:

  • For 32-bit systems
Terminal Command

sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb

(This may fail due to a missing dpmk. If so install this first. Also check the version numbers (8.561) against the created debs)

  • For 64-bit systems
Terminal Command

sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb

Using tab completion can make this command easier.

[edit] 5. Additional 64-bit instructions

If you have a 64 bit install, the above dpkg command may complain that "Errors were encountered while processing: fglrx-amdcccle". This is because of a dependency of the amdccle package on 32 bit libraries. If you receive this error, issue the following command after the above dpkg command, which will force the installation of all of the 32 bit dependencies, and then the amdcccle package:

Terminal Command

sudo apt-get install -f

Catalyst 9.4 on 64-bit systems requires the --force-overwrite command in the above dpkg command:

Terminal Command

sudo dpkg -i --force-overwrite xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb

Using tab completion can make this command easier.


[edit] 6. Generate a new /etc/Xorg.conf file

Terminal Command

sudo aticonfig --initial -f

in a terminal. If it doesn't give an error you should be good.

[edit] 7. Force use of /etc/Xorg.conf file

Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

Terminal Command

sudo aticonfig --input=/etc/X11/xorg.conf --tls=1

[edit] 8. Test your installation

Finally, reboot the computer and type

Terminal Command

fglrxinfo

into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Release 9.4 looks like:

display: :0.0  screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 4800 Series (This line may be different depending on what graphics card you are using.)
OpenGL version string: 2.1.8591

Please note: Depending on the particular ATI card that you own, you may or may not automatically have all of the relevant driver features enabled. R500 and R600 cards (X1xxx, HD series, and newer) in particular will need TexturedVideo enabled in Xorg.conf (rather than the traditional VideoOverlay) in order to support Xv accelerated video playback.

[edit] HOW TO UPDATE DRIVER

To update your driver to a new version (say 9.3 to 9.4) first disable the current driver through Ubuntu's Hardware Manager or use EnvyNG to remove the driver, then go to synaptic and search for "xorg-driver-fglrx" without the quotes and mark it for "Complete removal" and hit "Apply" then reboot your computer. Now simply repeat steps #1, 2, 4 and finally run these commends in a terminal:

Terminal Command

sudo aticonfig --initial -f

and

Terminal Command

sudo aticonfig --input=/etc/X11/xorg.conf --tls=1

then reboot.

It is very important that you COMPLETELY remove the old driver which includes the config files because when upgrading without uninstalling the old driver I noticed even though the new driver installed and worked there were some annoying problems that I experienced but after I completely uninstalled the driver then reinstalled it, it worked perfectly.

[edit] Tweaks

  1. Add tweaks as needed: http://ubuntuforums.org/showthread.php?t=849422
  2. Restart X, if it doesn't work, you can use the "vesa", "ati", "radeon" or "radeonhd" driver in the mean time, until you make it work.
  3. If you downgraded X to make fglrx work: enter synaptic, make sure all packages with "xorg" and "x11" are locked so that you can update and upgrade without worries.

Done! Now run amdcccle, glxgears, warsow etc :)

[edit] Issues

[edit] Installation

There are some system configurations on which none of the installation alternatives work with the latest 9.4 driver (please add; also please add if you got it to work in one of the listed setups):

  • Ubuntu 9.04 (x64) on x86_64 with Radeon HD4870X2: Framebuffer error, garbled screen.
  • Ubuntu 9.04 (x64) on x86_64 with Radeon HD 3300 (790GX): garbled screen.

[edit] Mesa drivers

If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

  • Remove the package xserver-xgl.
sudo apt-get remove xserver-xgl
Explanation: If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
DISPLAY=:0 glxinfo | grep render
If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [2])
Warning: This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
Section "Extensions"
Option "Composite" "Enable"
EndSection




  • Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
(EE) fglrx(0): cannot init AGP
(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
(WW) fglrx(0): * DRI initialization failed! *
If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others:
rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx
Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
blacklist i82875p_edac
This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).
Explanation: http://openwetware.org/wiki/Computing/Linux/Ubuntu




  • Check you are running the correct kernel.
Explanation: If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
Run in a terminal:
uname -r
If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.

If this doesn't help, try Ubuntu Gutsy Installation Guide#Verifying, or other links: [3], [4], [5].


[edit] Hang at logout

If you experience hangs when logging out (of X) it is probably due to the /etc/ati/authatieventsd.sh script looking for X authorisation files in the wrong place when it starts up. You can kill the hanging authatieventsd.sh processes from a console tty to allow the shutdown of the X server. This can be fixed permanently with:

sudo mkdir -p /var/lib/xdm/authdir
sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles

If that doesn't work then you can disable atieventsd with this command:

sudo /usr/sbin/update-rc.d -f atieventsd remove


Before the above commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do  : (assuming that the installer is in your home directory)

sh ati-driver-installer-8-12-x86.x86_64.run --extract driver
sudo cp ~/driver/packages/Ubuntu/dists/jaunty/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh

(jaunty is to be replaced by the name used at the building stage (intrepid,hardy,8.10,8.04,etc...)

sudo chmod +x /etc/ati/authatieventsd.sh

just reboot login and ctrl+alt+backspace to try

[edit] Suspend/Hibernation

Suspend hibernation works with the latest driver.

For ATI X1400, to get the laptop to wake up from suspend, I had to change the following in /etc/default/acpi-support:

SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
Comment: This is a little surprising, since the comments at the beginning of /etc/default/acpi-support seem to make it quite clear that those settings are ignored unless you add "acpi-support" to SUSPEND_METHODS. --Bewst 23:22, 19 December 2008 (UTC)

For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf: (This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)

Section "Extensions"
Option "Composite" "Disable"
EndSection

Section "ServerFlags"
Option "AIGLX" "off"
EndSection

[edit] Can't remove fglrx with dpkg

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This is a hack and should be avoided.

[edit] This module/version combo is already installed

If you get this error-message, simply uninstall the previous version before installing the new one with:

Terminal Command

sudo dkms remove -m fglrx -v 8.522 --all

[edit] New kernel installed?

I found out that when getting a new kernel the fglrx kernel-module is not installed for your new kernel. You can do that by these simple steps:

Terminal Command

sudo dkms build -m fglrx -v 8.552 -k `uname -r`
sudo dkms install -m fglrx -v 8.552 -k `uname -r`

if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf

:
Posted by Ritz®™

Windows 7 on Mac with VMware Fusion: A Practical Guide

FinderScreenSnapz002.mov

There’s been a lot of buzz flying around about Microsoft’s next big operating system, Windows 7, which just entered public beta.

As our readers know, a great way to start testing out a new operating system is in a virtual machine, where you can see how it works without having to dedicate a whole physical machine. 

Well guess what: this is certainly the case with Windows 7 and VMware Fusion, too.  So we wanted to take the time to share best practices on how to make this happen, with screenshots and video of the process to make it nice and easy for you.

Git yer free trial Windows!  Six months to see what you think of Windows on Mac!

Another cool thing about the Windows 7 Beta, is that it’s free to use for anyone.  That’s right.  Anyone can go and download the Windows 7 bits, and get a beta serial key that’s good through July 1st, 2009.

One of the costs associated with running Windows on the Mac is the cost of Windows.  And unlike VMware Fusion, which has a fully-functional 30-day trial for anyone to play with, Microsoft doesn’t typically provide trial access to operating systems in a way conducive to playing around in a VMware virtual machine—like an OS disk image, for example.

As such, a lot of Mac users who aren’t recent switchers, haven’t taken the opportunity to play around with the idea of Windows on the Mac, and as a result haven’t seen how fast, stable, and easy it can be.  Instead, you get people sitting back and saying “Windows on Mac? Ew!” because they haven’t really had the opportunity to learn any better.  They don’t know what they’re missing.  Well this is the chance to fix that.

It’s All About the Apps, Baby.

This kind of old-school thinking is a bit of a bummer, as there are tens of thousands of great Windows-only applications that Mac users can’t access without virtualized Windows apps, like Microsoft’s Photosynth on MacWorldwide Telescope on Mac, or Microsoft’s new Songsmith on the Mac, not to mention things like Google Chrome on Mac.  The list goes on and on, but you get the point.  It’s nice to have a balanced Dock!

Dock


Not just that, but Windows on the Mac nowadays isn’t your father’s Windows on Mac.  This isn’t Virtual PC for Mac, which emulated the Intel chip in software.  This isvirtualization, with direct CPU access, and all the speed that entails.  Also, this isn’t Mac virtualization of the sort you may have seen in early 2007.  The Macs are twice as fast, and the software’s much more mature.

So, we wanted to take the opportunity to show you that Windows 7, like Windows XP, Windows Vista, Windows 98, and pretty much any other Intel-based OS (Linux too!) will run in a VM with VMware Fusion, and give some guidance on how to set things up for best success.

First, The Caveats

Windows 7 beta, both 32-bit and 64-bit, is not supported with VMware Fusion, but many VMware product features appear to work well today including Drag and Drop, Unity, and more.  Based on commentary in our VMware Fusion forums, the best experience with Windows 7 beta with Fusion results from the following VMware settings:

- Use the Windows Server 2008 option to create your VM 
- Disable 3D Acceleration 
- Disabled Shared Folders

We plan to support Windows 7 after it is released.

Next, What You Care About

Because VMware Fusion does not yet support Windows 7, there are some tweaks you’ll have to do.

First, go ahead and download the Windows 7 ISO from Microsoft’s Windows 7 Beta siteand get yourself a beta product key. You can use 32-bit or 64-bit, but we’ve heard that lots of folks are getting better performance out of 64-bit, so this example will assume that.  Just download the ISO to your desktop.

Then, you’ll go to create a new virtual machine, the same as you’ve done before via “File>New”:

Picture 1

Next, we’re going to point the New Virtual Machine Assistant at the Windows 7 ISO you just downloaded.  Typically, if you just insert a Windows install disk, VMware Fusion automagically recognizes what OS is in it, but in this case, we have to point it at the ISO.

Click “Continue without disk.”

Picture 2

Then, click “Use operating system installation disk image file”:

Picture 4

Just select the ISO in the dialog that pops up:

Picture 3

Next, based on what we’ve seen in our VMware Fusion forums, you have to do a little bit of tweaking. 

First, Windows Easy Install will parse the disk image as Windows Vista (either 32 or 64 bit, depending on which ISO you downloaded).  Go ahead and change that to Windows Server 2008 (again 32 or 64-bit, depending on which one you downloaded).  We’ve heard that it works fine defined as “Vista” too, but this appears to be the best way. 

Picture 5

Next, go ahead and take that serial key that was provided to you by Microsoft, and paste it into the Windows Product Key form in Windows Easy Install.

Also, untick “Make your home folder accessible to the virtual machine", as based on reports in our VMware Fusion forums, shared folders aren’t working in Windows 7. 

Picture 6

 

At this point, you should see your final configuration setup, with 1 GB of RAM assigned, and a virtual hard disk that will expand up to 40GB (but will start much smaller).  Click “Finish.” 

Picture 7

Once you hit “Finish,” Windows Easy Install will be off and running, installing Windows 7.  You’ll see some reboots, and VMware Tools will install automatically.

After that’s all finished, you should be able to play around with Windows 7 as you would expect, with the noted exceptions up top.  Again, this is not a supported configuration, and there will likely be bugs, as we repeat above from reports in our VMware Fusion forums.

Running Windowed - 13

And for those who like movies more, we threw together the one below to help you through the process.

Enjoy, and remember, for those of you who haven’t played around with Windows on your Mac yet because you didn’t quite see the light, this is your opportunity to join the ranks of the truly enlightened who realize that one OS per machine is so 20th century…

Download the free trial of VMware Fusion 2 or buy yourself a copy, and then get yourself the Windows 7 Beta.

:
Posted by Ritz®™

8.10 will be run natively from the portable device utilizing a persistent casper-rw loop file for saving and restoring changes.Ubuntu is a product of Canonical Ltd.

Ubuntu 8.10 Intrepid Ibex Screenshot

Ubuntu 8.10 USB Flash Drive 설치하기 위한 준비사항

  • Windows PC to perform conversion
  • Ubuntu 8.10 ISO
  • 2GB or larger USB flash drive (fat32 formatted)
  • U810p.exe (contains the files to do the conversion)

Ubuntu 8.10 USB Flash Drive 설치과정

  1. Download 한 후 U810p.exe를 실행시키면, PC에 자동으로 풀린다. AU810p 폴더가 자동생성된다.
  2. Download Ubuntu 8.10 ISO 를 다운로드 하고 U810p 폴더에 복사하여 준다.
  3. U810p 폴더에서 U810.bat 화일을 클릭하여 설치과정에 따라 설치하여 준다.
  4. 스크립터 실행이 끝나면 PC를 재시작하고 BIOS 나 혹은 Boot Menu 에서 USB device로 세팅하여 저장하고 재부팅한다.

진행과정에 따라 제대로 설치되었다면 Live Ubuntu 8.10 USB 로 부팅될 것이다.

Persistence size: 기본적인 casper-rw loop file 크기는 변경된 것이 1GB로 설정되어 있다. 만약 좀더 많은 공간을 원한다면 자기 usb크기에 맞는 다음 파일을 다운로드하여 기존 파일을 변경하여 준다.


DSDT 덤프 받는 커맨드

#sudo cat /proc/acpi/dsdt > dsdt.aml

:
Posted by Ritz®™
2009. 4. 29. 19:29

Vmware Unity 기능 Other OS/Windows2009. 4. 29. 19:29

Update : Unity 기능을 사용하기 위해서는 상단메뉴의 Virtual Machine에서 Vmware Tools을 다음과 같이 설치해야 한다.




Unity 기능을 사용하면 윈도우즈와 MAC 이 혼용되어버려 맥인지 윈도우즈인지 분간이 안되게 만들어 버리는 군요.

1. Unity 적용전


2. Unity 적용후



:
Posted by Ritz®™

ASUS 노트북 공장초기화 하는 방법입니다.

방법 1

복원 파티션(Recovery Partition)을 이용하는 방법
1. 전원을 켠 다음 < F9 > 를 누른다.
2. Windows Setup [EMS Enabled]를 선택하고[Enter]를 누른다 .

3. 언어(language)를 선택하고 다음(Next)을 누른다. 

4. ASUS Preload Wizard messages 를 읽고 다음(Next)을 누른다.

5. 파티션 선택사항(partition option)을 선택하고 다음(Next)을 누른다.:

Recover Windows to first partition only. 
이 옵션은 첫번째 파티션을 제거하고 다른 파티션은 유지하며 새로운 시스템 파티션 "C"드라이버를 생성한다.
Recover Windows to entire HD. 
이 옵션은 하드디스크의 모든 파티션을 제거하고 새로운 파티션 "C"를 생성한다.
Recover Windows to entire HD with two partitions. 
이 옵션은 하드디스크의 모든 파티션을 제거하고 새로운 두개의 파티션 "C" (25%) 와 "D" (75%)를 생성한다.

6. 다음 지침에 따르고 복원이 끝날때까지 수행한다.

 

 

방법 2

복원용DVD(Recovery DVD)를 이용하는 방법
복원용 DVD(Recovery DVD)를 생성한다.: 
1. 윈도우즈 데스크탑에서 AI Recovery Burner 아이콘을 클릭한다.
2. 쓰기가능한 공 DVD 를 넣고 Start 를 클릭하여 복원용 DVD(Recovery DVD)를 생성한다.

aicovery.jpg

 
3. 다음 지침에 따르고 복원이 끝날때까지 수행한다.

提醒.jpg


여유공간이 충분한 쓰기가능한 공DVD를 이용하여 복원용 DVD(Recovery DVD)를 생성한다.

手.jpg

주의사항!

복원과정을 진행하기 전에 외장형 하드디스크를 제거한다. 마이크로소프트에 따르면 드라이버 파티션을 포맷하기 때문에 모든 중요한 데이타를 잃게 될 것이다.


복원용 DVD(Recovery DVD) 이용방법:
1. 복원용 DVD(Recovery DVD)를 넣는다.  전원을 켠다.
2. 노트북을 재시작한다. ASUS 로고가 보이면 ESC 키를 누르고 광학드라이버 ("CD/DVD") 를 선택한다. [Enter] 를 입력하여 복원과정에 들어간다.

3. OK 를 누르고 이미지 복원에 들어간다.
4. OK 를 선택하여 시스템 복원 확인을 한다.

手.jpg


복원과정은 하드드라이버에 덮어쒸우기를 하게 된다. 모든 중요한 데이타를 백업하였는지 확인한다.


5. Follow the onscreen instructions to complete the recovery process.

 

주의사항: 복원과정 동안 복원 DVD(Recovery disc)를 제거하지 않는다. 그렇지 않으면 파티션은 사용불가능하게 된다.노트북에 전원 어댑터가 제대로 연결되었는지 확인한다. 그렇지 않으면 복원이 실패로 돌아갈 것이다..

차라리 윈도우즈 설치용 USB를 만들어서 설치하는 방법이 더 빠를 수도 있다.
https://cafe.naver.com/uefi/19295

 

Rufus

준비물 - 16G USB, https://search.shopping.naver.com/search/all?where=all&frm=NVSCTAB&query=sandisk+...

cafe.naver.com

 

:
Posted by Ritz®™