Fujitsu S7021 BIOS 비프음 증상

Posted by Programmer™
2014. 1. 27. 05:53 Hardware

 

아래 글은 PhoenixBIOS 에만 해당된다. Award, AMI 등의 바이오스는 별 도움이 되지 않으므로 다른 사이트를 참조하시기 바란다.

노트북 Fujitsu S7021의 경우 출고당시 300 만원에 가까웠던 명품이긴 하지만, 한가지 단점이 시스템 팬쿨러의 소음이 고질적인 문제이다. 6 개월 한번씩 쿨러에 기름을 쳐주지 않으면 굉음이 난다. 거기다가 쿨러가 특수형이래서 고장이라도 난다면 부품 구하기가 쉽지 않다. 한국에서 후지쯔가 철수했기 때문에 부품을 구하려면 이베이나 아마존으로 해외구매를 해야 한다. 필자도 쿨러가 소음이 심해서 분해하다가 한번 고장내 옥션에서 17,000원씩이나 주고 중고로 구매했다.

아래는 필자의 노트북의 바이오스 버전이다. (Phoenix BIOS Date : 2007/07/24  v1.08)

비프음 4번 - 메모리 접촉 불량 (메모리를 뺏다가 지우개로 금박부분 지우고 재장착 후 해결)

간혹 아무런 비프음도 나지 않으면서 화면이 나오지 않는 경우(오른쪽 상단의 어플리케이션 LED 와 전원 LED 는 불 들어옴 )가 있는데 이 경우도 메모리 탈착 후 재장착 하니 해결되었다.

 

1 Beep

A single beep from a Phoenix based BIOS is actually an "all systems clear" notification. Technically, it's an indication that the Power On Self Test is complete. No troubleshooting necessary!

 

1 Continuous Beep

One continuous beep isn't an officially listed Phoenix beep code but I know of several instances of this occurring. In at least one case, the solution was to reseat the CPU.

필자의 경우 노트북 키보드 장착 에러인 경우 이 소리가 났다.

1 Short Beep, 1 Long Beep

One short beep followed by one long beep also isn't an officially listed Phoenix beep code but two readers have let me know about this one. In both cases, the problem was bad RAM which replacing obviously solved.

 

1 Long Beep, 2 Short Beeps

One long beep followed by two short beeps indicates that there has been a checksum error. This means that there is some kind of motherboard issue. Replacing the motherboard should fix this problem.

 

1-1-1-1 Beep Code Pattern

Technically, a 1-1-1-1 beep code pattern doesn't exist but I've seen it and many readers have too. Most often, it's a problem with the system memory. This Phoenix BIOS issue is usually corrected by replacing the RAM.

 

1-2-2-3 Beep Code Pattern

A 1-2-2-3 beep code pattern means that there has been a BIOS ROM checksum error. Literally, this would indicate an issue with the BIOS chip on the motherboard. Since replacing a BIOS chip is often not possible, this Phoenix BIOS issue is usually corrected by replacing the entire motherboard.

 

1-3-1-1 Beep Code Pattern

A 1-3-1-1 beep code pattern on a PhoenixBIOS system means that there has been an issue while testing the DRAM refresh. This could be a problem with the system memory, an expansion card, or the motherboard.

 

1-3-1-3 Beep Code Pattern

A 1-3-1-3 beep code pattern means that the 8742 keyboard controller test has failed. This usually means that there is a problem with the currently connected keyboard but it could also indicate a motherboard issue.

 

1-3-4-1 Beep Code Pattern

A 1-3-1-1 beep code pattern on a PhoenixBIOS system means that there is some kind of issue with the RAM. Replacing the system memory usually fixes this problem.

 

1-3-4-3 Beep Code Pattern

A 1-3-1-1 beep code pattern indicates some kind of issue with the memory. Replacing the RAM is the usual recommendation for solving this problem.

 

1-4-1-1 Beep Code Pattern

A 1-4-1-1 beep code pattern on a PhoenixBIOS system means that there is an issue with the system memory. Replacing the RAM usually fixes this problem.

 

2-1-2-3 Beep Code Pattern

A 2-1-2-3 beep code pattern means that there has been a BIOS ROM error, meaning an issue with the BIOS chip on the motherboard. This Phoenix BIOS issue is usually corrected by replacing the motherboard.

 

2-2-3-1 Beep Code Pattern

A 2-2-3-1 beep code pattern on a PhoenixBIOS system means that there has been an issue while testing hardware related to IRQs. This could be a hardware or misconfiguration problem with an expansion card or some kind of motherboard failure.
 

 

 

IObit 의 LiveUpdateSvc 삭제하는 방법

Posted by Programmer™
2014. 1. 22. 23:06 Utility

 

컴퓨터에서 LiveUpdate.exe 를 삭제하는 방법

I check all running processes regular on the computer systems that I use to make sure that the system is safe and that nothing slipped by the defenses.

While that works well, I usually spot processes started by third party programs after installation. Most of the time, they are not needed at all and waste only system resources.

I noticed the LiveUpdate.exe process recently on a Windows PC and was not really sure what to make of it at first. I immediately thought of Windows Live, but since I never heard of the executable before, it was almost certain that it had nothing to do with Microsoft's service.

It is thankfully relatively easy to find out more about a process running on your system.

LiveUpdate.exe 란 무엇인가?

The first thing that I usually do is open the Windows Task Manager with Ctrl-Shift-Esc, right-click the process in question, and select properties from the context menu.

The location of the service on the system is displayed here, so that I know its folder location and as part of this usually also the program that installed it on my system.

Note: The process LiveUpdate.exe only shows up if you select to "Show processes from all users" in the Task Manager.

task manager live update

If it is a service, you can get similar information by loading services.msc on your system using the run box or command prompt. The process in this case was a service, and the Services Manager revealed additional information about it.

liveupdate.exe

I knew now that it was created by the software company IObit, likely to power the updating of company products on my system similar to how Firefox or Google Chrome are handling the updating.

Now that I knew that, I started to investigate the matter further. I noticed that I did not have any IObit products installed on my system anymore, which led to the conclusion that LiveUpdate.exe was a leftover that -- for whatever reason -- was not removed during the uninstallation of the last IObit product that made use of it.

Disabling  and removing LiveUpdate.exe

Since there was no IObit program left on the system, it did not really make that much sense to have the updater running in the background at all times.

First thing I did was to change its startup type from automatic to disabled in the Services Manager. I also made sure that the service itself was stopped.

Next thing I did was to delete the service. I have explained how this is done on the linked article. Here is a quick rundown of the commands:

  1. 윈도우 키 + R 을 누르고 cmd 를 타이핑합니다.
  2. 표시되는 명령 프롬프트(데스크톱 앱)에서 마우스 오른쪽을 클릭하여 관리자 권한으로 실행을 클릭합니다.
  3. sc delete LiveUpdateSvc 를 입력하고 엔터키를 칩니다.
  4. 이제 Windows 로부터 서비스가 삭제됩니다.
  5. [SC] DeleteService SUCCESS 메시지가 보이면 제대로 삭제된 것입니다.

I checked that the service was indeed deleted, and proceeded to its directory on the system: C:\Program Files (x86)\IObit\LiveUpdate.

I deleted the full directory, and the IObit directory as well, since no products of said company were installed on the system.

It is very likely that you will find orphaned keys in the Registry that point to Live Update. You can run a search for them if you want, but they should not cause any issues on the system. It is alternatively possible to run a program like CCleaner to find orphaned files in the Registry.

 

[Windows 7] ATI Radeon Xpress 200M Driver Update 하기

Posted by Programmer™
2014. 1. 12. 17:00 Windows 7, 8

Windows 7 설치후 ATI Radeon Xpress 200M 을 잡지 못하는 현상 ( 제어판 - 하드웨어 및 소리 -  장치관리자 - 디스플레이 어댑터를 보면 표준 VGA 그래픽 어댑터로 되어 있는 경우 ) 이 일어나는 경우 수작업으로 업데이트를 시켜주어야 한다.

 

 

ATI 사가 AMD 사에 의해 합병되었는데, AMD 사 홈페이지를 가보면 어디에도 Windows 7 드라이버는 보이지 않는다.

이런 경우에는 Microsoft Update Catalog 사이트를 이용하자. http://catalog.update.microsoft.com/v7/site/search.aspx?q=ati+radeon+xpress+200m

 

ATI Technologies Inc. - Display - ATI RADEON XPRESS 200M Series Windows 7 Client,Windows Vista Drivers (Other Hardware) 2007-06-13 8.383.0.0 6.7 MB 7070159

2015년 1월 7일 현재 8.383.0 버전이 가장 최신인 것 같다. 추가를 누른 후 오른쪽 상단의 바스켓 보기(1)를 클릭한다. 그리고 다운로드를 클릭한다.

표준 VGA 그래픽 어댑터의 오른쪽 클릭후 속성 - 드라이버 - 드라이버 업데이트 - 컴퓨터에서 드라이버 소프트웨어 찾아보기 를 해주면 된다.

 

재부팅 후 제어판 - 디스플레이 - 화면해상도 - 고급설정을 보면 사용 가능한 총 그래픽 메모리가 895 MB 이다. 

 

 

 화면 해상도는 ①  1280 x 800  ②  1280 x768  ③  1024 x 768  ④  800 x 600 를 선택할 수 있다.

 

 

CPU-Z 로 확인해보면 비디오 메모리가 이제 제대로 잡힌 것을 확인할 수 있다.

 

 

필요하신 분들을 위해 Windows7 32비트(64비트는 설치 안 해봐서 될지 안될지 모름)용 ATI Radeon Xpress 200M Driver 를 첨부한다.

 ATI RADEON XPRESS 200M_X86_Win7_en-20085193_8.383.0.0.cab

 

 

기타 장치 - 기본 시스템 장치:

Ricoh RL5C843 SD/MMC Host Controller --  PCI Bus 2, Device 9, Function 2 Ricoh RL5C592 Memory Stick Bus Host Adapter -- PCI Bus 2, Device 9, Function 3

Ricoh CardReader R5U230, v.2.07.01.02, A00   (Windows 7 32 bit & 64 bit)                 

  • Release Date : 2010.03.16
  • Version: 2.07.01.02 
  • File Size: 5,443,320 byte

Windows 7 Driver :  http://ftp.us.dell.com/chipset/R253443.exe 

 

R253443.exe

 

모든 드라이버 파일을 설치한 후 화면이다.

위의 라데온 그래픽 드라이버 설치 시 가끔 문제를 일으킵니다.

그래픽 드라이버 설치는 삼성 NT-R40 윈도우7 그래픽 드라이버 설치하기 (1),(2)

http://cprogramming.tistory.com/entry/NTR40-그래픽-드라이버-설치하기

를 참고해 주세요.

 

스타크래프트 업데이트 패치하기

Posted by Programmer™
2013. 12. 27. 15:09 Game

스타크래프트 최신 업데이트 패치를 설치시, 게임을 다시 인스톨 해달라는 메시지와 함께 패치가 안되는 경우가 있다. 이런 경우 아래 레지스트리 키값만 등록해주면 된다.

enablepatch.reg

위의 파일을 다운로드 받던지 아니면 아래 처럼 설치된 경로 내용을 편집해주면 된다.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Blizzard Entertainment\Starcraft]
"InstallPath"="C:\\Game\\Starcraft"

 

2013 년 12 월 27 일 현재 최신 패치는 1.16.1 버전이다. 패치를 적용시키면

1. patch.txt  2. bnupdate.log  3. Patch_rt.mpq  4. bnupdate.exe

의 파일 4개가 업데이트된다.

 

Starcraft and Brood War Patch Information

--------------------------------------------------------------------------------
- patch 1.16.1
--------------------------------------------------------------------------------

Feature Changes

- In-game Speed Options menu now has a "Enable CPU Throttling" checkbox.
  Enabling this option will allow StarCraft to consume fewer CPU cycles. By
  default this option is off.

Bug Fixes

- Fixed an issue with the reply feature where any character followed by a "r "
  was being treated as a reply.
- Removed an unnecessary delay when processing palette cycling updates.
- Lessened the imposed delay in the CPU Throttling feature.