Jump to content

tom_tom

Stały użytkownik
  • Posts

    297
  • Joined

  • Last visited

Everything posted by tom_tom

  1. Próbuje zainstalować na laptopie HP 250 windows 7. Wcześnie było tam zainstalowane Ubuntu. Po włożeniu dvd z win7 (obraz ze strony microsoftu) pierwsze kroki przechodzą bezproblemowo. Nowa instalacja, delete partycji, ustawienie nowych, dalej i instalacja rusza. 1. krok, czyli kopiowanie plików przechodzi bezproblemowo 2. krok, czyli rozpakowywanie plików idzie 100%, po czym chyba odznaczane na zielono są następne kroki i pojawia się w tym samym oknie informacja, że wymagane jest ponowne uruchomienie komputera, po którym wszystko zaczyna się od nowa - tj. wybór języka instalacji itd. I tak w kółko. W jaki sposób można to naprawić?
  2. zdebugowany? to tylko odczyt w bluescreenviewer
  3. Witam, Na nowym sprzęcie od 2 tygodni spotykam się z bluescreenami. Pytałem na forum microsoftu. Nakierowano mnie, aby ściągnąć program, który odczyta mini dumpa, i widzę tam, że w sekcji Probably caused by jest przyczyna, tylko ze 99% przypadków ten problem caused by to: ntoskrnl.exe Poniżej 2 ostatnie logi z mini dumpa: Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:WindowsMinidump082413-7593-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: *** Invalid ******************************************************************************** Symbol loading may be unreliable without a symbol search path. ** Use .symfix to have the debugger choose a symbol path. ** After setting your symbol path, use .reload to refresh symbol locations. *****************************************************************************Executable search path is: ********************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Unable to load image SystemRootsystem32ntoskrnl.exe, Win32 error 0n2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeWindows 8 Kernel Version 9200 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 9200.16628.amd64fre.win8_gdr.130531-1504Machine Name:Kernel base = 0xfffff801`9660f000 PsLoadedModuleList = 0xfffff801`968dba20Debug session time: Sat Aug 24 19:12:45.122 2013 (UTC + 2:00)System Uptime: 0 days 0:42:18.812********************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Unable to load image SystemRootsystem32ntoskrnl.exe, Win32 error 0n2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeLoading Kernel Symbols.......................................................................................................................................................................................Loading User SymbolsLoading unloaded module list...........******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 50, {ffffffffffffffe8, 0, fffff960000a9147, 0}***** Kernel symbols are WRONG. Please fix symbols to do analysis.**************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************* WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sys**************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ****************************************************************************Probably caused by : win32k.sys ( win32k+5e147 )Followup: MachineOwner oraz Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:WindowsMinidump082413-6687-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: *** Invalid ******************************************************************************** Symbol loading may be unreliable without a symbol search path. ** Use .symfix to have the debugger choose a symbol path. ** After setting your symbol path, use .reload to refresh symbol locations. *****************************************************************************Executable search path is: ********************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Unable to load image SystemRootsystem32ntoskrnl.exe, Win32 error 0n2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeWindows 8 Kernel Version 9200 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 9200.16628.amd64fre.win8_gdr.130531-1504Machine Name:Kernel base = 0xfffff802`03a0c000 PsLoadedModuleList = 0xfffff802`03cd8a20Debug session time: Sat Aug 24 23:55:32.351 2013 (UTC + 2:00)System Uptime: 0 days 4:42:16.040********************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Unable to load image SystemRootsystem32ntoskrnl.exe, Win32 error 0n2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeLoading Kernel Symbols........................................................................................................................................................................................Loading User SymbolsLoading unloaded module list.............******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 1E, {ffffffffc0000005, fffff80203a8e321, 0, ffffffffffffffff}***** Kernel symbols are WRONG. Please fix symbols to do analysis.**************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ****************************************************************************Probably caused by : ntoskrnl.exe ( nt+82321 )Followup: MachineOwner Wpisałem w google wczoraj ten ntoskrnl.exe + kod błędu i był jeden przypadek, który po zmianie ramu został "wyleczony". Jak sprawdzić co jest przyczyną tego braku stabilności? Co to powoduje?
  4. Czyli jaka ta plyta? Naprawde mowimy tu o budzetowkach :) Jedyna fajna opcja to usb 3.0. Msi-h61 slyszalem ze nie ma domyslnie wsparcia dla ivy, potrzebny jest update. Co polecicie w tym przedziale?
  5. Okej, poszedlem za Wasza rada i przekonalem znajomego do G1610. Szukam teraz taniej plyty do tego. Mam juz 4gb ddr3 i zostaje pytanie, czy zasilacz ktory jest teraz w tym k8nspro + athlon 3200 pociagnie ten zestaw?
  6. hm, a takie g1610 na msi h61m-p31 bedzie wydajniejsze od tego e6300?
  7. tyle ze g1610 + plyta to koszt 300-400zl. to ma byc komputer do ogladania filmow w hd, czy jakies gry, ale wszelkie nowosci i tak leca na ps3, wiec nie ma parcia na wydajnosc, to ma ladnie plynnie dzialac ;) moze jakas plyta z obsluga ddr3 i potem zmiana procesora najwyzej?
  8. Znajomy chce zmienic swojego athlona 3000 na e6300, ktore wyjal z dekstopowego della gx i zanastanawiam sie jaka plyte dobrac (niskim kosztem) do tego oraz jaka karte graficzna i ramy. Zastanawialem sie nad radeonem 4770. Powinien wystarczyc?
  9. Mamy problem z kompem znajomego. Konfiguracja: Athlon 64 3200 s.754 Gigabyte GA-K8NS Pro 1,5GB DDR Radeon 9550 Dysk ata + sata I teraz pytanie, bo ostatnio postawilismy czysty system, i komputer nadal na swiezo nie dziala jak powinien. Po odpaleniu windy pasek najpierw ma czarne obszary w niektorych miejsach a film/muzyka na youtubie potrafi zaciac. Pytanie czy to wina konfiguracji czy np. blednych sterownikow, choc te byly sciagane ze strony gigabyte'a? Znajomy mysli o rozbudowaniu tego kompa i tu pytanie, bo odkad mam maka, przestalem sie w tym orientowac. Z tego co rozejrzalem sie na allegro poza ramem, max 3gb i grafiką(ati 3650?) nie rozbudujemy tu nic. Prockow na allegro nie ma a i skok z 3200 na 3800 bylby chyba nikly. Czy jest sens sie w to bawic czy moze lepiej postawic cos nowego? I tu pytanie, co, na jakiej platformie? Nie ma na to duzego budzetu, bo do gier ma konsole, a pc ma do filmow i czasem do pojedynczych tytulow jak stalker np.
  10. Czesc, Mam problem w kolejnoscia bootowania dyskow na mojej plycie glownej - GIGABYTE GA-K8NS PRO s.939 Przy instalacji xp musialem odlaczyc sata dysk, bo zacinalo instalke. Zainstalowalem w kazdym razie xp na ata, bo tak bylo ostatnio. Wszystko ladnie. Po zakonczonej instalce podlaczylem sata dysk i przy probie uruchomienia dostaje komunikat: BRAK BOOTMGR. Kliknij ctrl alt delete. Podejrzewam w takim razie ze na sata dysku znajdowal sie jakis bootmgr z poprzedniej instalacji, a komputer traktuje sata na pierwszym miejscu i proboje stamtad uruchomic xp. I teraz pytanie co z tym zrobic? W BIOS mam na 1. pozycji cos takiego jak hard drive priority ale mam do wboru tylko sata dysk i "all cards usb, czy jakos tak". Jak ustawic, aby ATA mialo priorytet?
  11. Jak wypadaja te MSI? Od zawsze mialem gigabyte'a az do am3 ostatnio. Potem mak i jakos nie wiem co poza asusem i gigabytem jest warte uwagi? @Alucard69, więcej rdzeni? Moglbys rozwinac? Czy przy renderowaniu mi się to nie zagrzeje? Bo tak naprawde projektowac w 3d moge sobie na swoim mbp 13" ale po [gluteus maximus] dostaje gdy dochodzi do wyplucia renderu gotowego. Czy te boksowe chlodzenia na karcie i procku nie powinny byc zastapione cyzms wydajniejszym?
  12. Witam, Noszę się z zamiarem zakupu sprzętu do zabawy w Cinema 4D. Nic wielkiego, narazie tylko nauka i nieskomplikowane rzeczy, dlatego na początku chciałbym zlożyc dobra baze, ktora potem moge rozbudowac. Tak wiec na chwile obecna wystarczy mi sredniej mocy i5. Myslalem o 3450/3470. Mam problem z plyta glowna, jaki chipset? Zastanawialem sie nad tym: http://www.komputronik.pl/product/131735/Sprzet_komputerowy/Podzespoly/Asus_P8Z68_V_LX.html lub jego odpowiednikiem od Gigabyte'a. Nigdy nie narzekalem na gigabyte'a ;) Pamieci? Tu bolaczka totalna. Nie mam zielonego pojecia jakie, z jakim taktowaniem, CL, jaka marka? Jesli chodzi o pojemnosc to min 8GB w jednej kostce, zeby potem dolozyc druga. Karta grafiki. Z tego co wyczytalem, kazda z obsluga OpenGL, wiec myslalem o GTX 650. Nie chce na chwile obecna wydac na to wiecej niz max 650zl. Chyba ze jakis radeon? I jaka marka? Czy to jest taka zaleznosc, ze przy plycie asusa, karta tez powinna byc od asusa? Jesli chodzi o dyski to myslalem o 60GB samsunga SSD + WD na 1TB dane. I to chyba tyle. Dochodzi kwestia zasilacza, i tu nie mam zielonego pojecia, jaka marka i jaka moc bedzie potrzebna. Z gory dziekuje za pomoc ;)
  13. Witam, Mam taką płytę główną i zastanawiam się jaki procesor tam mogę wsadzić: http://www.gigabyte.pl/products/page/mb/ga-m61p-s3_10/ Czy athlon II będzie obsługiwany czy może szukać cos z tego: http://allegro.pl/athlon-64-x2-am2-48881 ?
  14. Problem w tym skąd wziąć oryginalny nośnik : )
  15. No właśnie problem w tym , że na torrentach nie ma wersji home basic pl visty ...
  16. Mam laptopa Lenovo 3000 n500 z dołączonym systemem Windows Vista Home Basic. Obecnie była tu inny system, teraz chcę powrócić do visty i mam problem, bo poza kluczem do niej nie mam niczego. Skąd mogę otrzymać obraz czystej Visty w tej wersji? Do laptopów krążków nie dołączają, a recovery usunięte..
  17. Witam, Poszukuję jakieś płyty pod socket 754 lub 939 z wyjściem na SATA, żeby osadzić na niej Semprona lub jakiegoś Athlona. Interesuję mnie coś używanego, w cenie ok.150zł za komplet. Myślałem o k8ns, podobno dobre? Cudów nie oczekuję, chce tam tylko postawić gentoo do zabawy, więc fajnie jakby się nie grzała i była dość stabilna. Jeśli ktoś ma od razu na sprzedaż to byłbym wstępnie zainteresowany :) Pozdrawiam
  18. a gdyby dysk odlaczyc, podlaczyc do drugiego lapa i sformatowac? po wcisnieciu f1/f2 czy tam delete ukazuje sie ekran american megatrends. ambiios...entering setup...boot selection popup menu has been selectedthe mch is operating with ddr2 667/cl5 in dual channel interleaved mode.initializing usb controllers.. done.1016MBB OKauto-detecting pri master .. ide hard disk auto-detecting sec master .. atapi cdrompri master: hitachi ....... sbd0c70pultra dma mode-5, s.m.a.r.t. capable and status ok hm, chyba okej? zadnych errorow, aczkolwiek bios tu nie ma, chcialbym ustawic jakies booty czy cos ?
  19. do biosa własnie nie moge się dostac przez delete/f12. wciaskajac, lub przytrzymujac esc, nie otrzymuje zadnego efektu..
  20. Witam, Mam problem ze swoim laptopem. Po wgraniu windowsa 7 (instalacja czysta, nie aktualizacja) laptop zawiesza się na starcie na logo asusa. Laptop to asus f3f. Jak temu zaradzić? Pozdrawima, Tomek
  21. Witam, Mam taki mały problem w asusie x71sl. otoż podczas rozmowy wideo na skajpie obraz jest wyswietlany do góry nogami. o ile w viscie mozna go odwrocic w narzedzia/opcje/wideo/ustawienia/camera i zaznaczyc po prostu mirror: vertical to w xp tego nie ma. jak naprawic ten problem w win xp? z gory dziekuje za pomoc ;)
  22. Orientuje się ktoś może skąd można ściągnać program LifeFrame? Jest to programik dodawany do każdego laptopa asusa, pozwala między innymi odwrócić ekran w kamerze internetowej. Szukałem na google, znalazłem link na softpedia.com ale linki wygasły Oo Z góry dziękuję za pomoc ; )
  23. tom_tom

    ...

    eeee... pokaż jakąś swoją pracę bo Twoje fajne forum jest wyłączone ;)
  24. Nowy lay na forum będzie. ale to "zaraz" ;]
×
×
  • Create New...