koolmans Jūlijs 19, 2009 Share Jūlijs 19, 2009 Esmu testējis pāris spēles uz Windows xp un windows 7, divas no tām apmēram gāja līdzvērtīgi, bet spēle Need for speed most wanted uz windows 7 parādīja sevi ļoti slikti, fps ir apmēram 3x mazāks, kā tas ir izskaidrojams? Link to comment Share on other sites More sharing options...
Igelkott Jūlijs 27, 2009 Share Jūlijs 27, 2009 varbūt šai vakarā neesmu sevisķi attapīgs, bet.. atklāju, ka W7 piedāva izvēlēties visus layoutus, ka var manīt - bez visādiem apostrofiem, Tildēm un Winlatiem, tomēr netieku skaidrībā, kur slēpjas āķis - visvisādi izmēģinājos nomainīt uz ('), bet nekādā jēgā - paliek tas pats defolta Alt garumzīmes variants. Link to comment Share on other sites More sharing options...
Gufiys Jūlijs 28, 2009 Share Jūlijs 28, 2009 Pie default languages tev jaāliek atvian (') vai kaut kas tamlīdzīgs Link to comment Share on other sites More sharing options...
777hp Augusts 5, 2009 Share Augusts 5, 2009 Kādas ir iespējas Windows 7 ietvaros, ~15GB "unallocated" pievienot partīcijai? Ar disk management var tikai tad automātiski partīcija tiks konvertēta uz dynamic - tas nekam neder. Visu var redzēt bildē. http://img22.imageshack.us/img22/3255/capturehdd.jpg P.S pārsteidzoši, ka pēc partīcijas formatēšanas cita windows vidē boot menedžeris automātiski lieko OS ierakstu izdzēsa (windows7). Link to comment Share on other sites More sharing options...
zebieksterc Augusts 5, 2009 Share Augusts 5, 2009 lai gan vel oficiali nav pieejams, bet jau atrasta pirma kļūda RTM build 7600.16385 InfoWorld Link to comment Share on other sites More sharing options...
aldisniv Augusts 9, 2009 Share Augusts 9, 2009 Vēl kas dīvains,pārdēvējot kādu mapi uz desktopa gadās ka šī pazūd. Link to comment Share on other sites More sharing options...
Gestapo Augusts 9, 2009 Share Augusts 9, 2009 (labots) Pie default languages tev jaāliek atvian (') vai kaut kas tamlīdzīgs A vot man neiet, uz peedeejaa 7100 gaaja bez probleemaam, bet uz RC nevaru palaist, liku gan laacz to apostrofu gan veel kaut kaadus latvieshinaajumus, bet neiet neviens, ir kaadam padoms? Labots Augusts 9, 2009 - Gestapo Link to comment Share on other sites More sharing options...
neteiksu Augusts 14, 2009 Share Augusts 14, 2009 Mani ir piemeklējusi ķibele.. Esmu uzinstalējis uz sava stacionārā windows 7, bet gribētos tā kā savam radeonam draiverus dabūt virsū, bet to viņš man neļauj, labi tas vēl ir sīkums, jo no neta es vēl viņus varētu daūt, bet nākošā ķibele ir tāda, ka es netieku pie neta, diskā man ir tas draiveris, bet viņš to disku neņem? Ko man iesakat darīt? Link to comment Share on other sites More sharing options...
Zux Augusts 14, 2009 Share Augusts 14, 2009 Kāpēc netiec pie neta? Iepriekšējo widozi neatstāji? Link to comment Share on other sites More sharing options...
Grossmeister Augusts 14, 2009 Share Augusts 14, 2009 es netieku pie neta, diskā man ir tas draiveris, bet viņš to disku neņem?Ko man iesakat darīt? Diskā draiveri priekš XP vai Vista ? XP nederēs , būs kaut kā Vista draiveri dzelžiem jānovelk . Link to comment Share on other sites More sharing options...
neteiksu Augusts 14, 2009 Share Augusts 14, 2009 Priekā xp, sanāca baigais iepēriens, domāju pa ātro visu uzinstalēšu, bet izskatās, ka man pie tiem draivriem netikt.. Jāmetās atpakaļ uz xp.. Link to comment Share on other sites More sharing options...
Zux Augusts 14, 2009 Share Augusts 14, 2009 Vismas tīklenes draiverus varēji iepriekš novilkt! Link to comment Share on other sites More sharing options...
neteiksu Augusts 14, 2009 Share Augusts 14, 2009 Nepadomāju.. Kāds nevar man palīdzēt ar draiveru meklēšanu, jo man nesokās.. Man ir ASRock čipsets.. Palīdziet man lūdzu. :)b Link to comment Share on other sites More sharing options...
Zux Augusts 14, 2009 Share Augusts 14, 2009 (labots) Karoče, neprasi šeit vairs neko, kā izrādās, te tev neviens nevar palīdzēt. ASRock čipsets....! Labots Augusts 14, 2009 - Zuxters Link to comment Share on other sites More sharing options...
Grossmeister Augusts 14, 2009 Share Augusts 14, 2009 Ar tādu pieeju nevis nepalīdzēs , bet nespēs palīdzēt . Link to comment Share on other sites More sharing options...
neteiksu Augusts 14, 2009 Share Augusts 14, 2009 Ar kādu pieeju? Kas vainas čipsetam? Link to comment Share on other sites More sharing options...
Grossmeister Augusts 14, 2009 Share Augusts 14, 2009 (labots) Tu ko , domā , ka Asrock tikai vienu vienīgu čipsetu ražo ? Asrock ražo MB un pēc to burtu un ciparu kombinācijas var noteikt , kas par čipsetu . Labots Augusts 17, 2009 - Grossmeister Link to comment Share on other sites More sharing options...
Zux Augusts 14, 2009 Share Augusts 14, 2009 Tāda nav! Link to comment Share on other sites More sharing options...
neteiksu Augusts 15, 2009 Share Augusts 15, 2009 Nu beigās izmēģināju gan 32 bit gan 64 bit, no tā nebija nekāda starpība, vismaz manam prātam un acīm! Beigās es nonācu pie secinājuma, ka mans čipsets (ASRoch 775Twin-HDtv ...) ir pārāk vecs. Dators man ir labi kalpojis un par citām lietām nevaru sūdzēties. Šitais čipsets ir 2005 gada ražojums es netiku līdz netam, bet man draugam arī ir 2005 gada ražojums, nepateikšu kāds, bet viņam viss iet uz Urrāāā. Tātad secinājumi: ASRock čipseti ir nepārāk labi, neko nevaru pateikt par jaunajiem ražojumiem, bet manējais neder nekam labam! Link to comment Share on other sites More sharing options...
Guest Augusts 17, 2009 Share Augusts 17, 2009 (labots) Kā redzams Windows 7 jau sāk būt pieejams, bet kopsummā tā nemaz nav major versija, bet gan Windows Vista SE vai Vistas uzlabojums. Liela major versija iznāks tikai apm. 2012. gadā. Lasīt sīkāk: http://windows8center.com/ Kopsummā liekas nebūtu slikts produkts, bet daudz kas ir piemirsts (stratēģija,...). XP mode gan nav tas labākais ko varētu piedāvāt, jo visam atbalstam ir jabūt ietvertam iekšā OS, lai var palaist arī pašas pirmās aplikācijas. Kļūdas, kļūdas turpinās, bet ceru, ka Windows 8 nebūs sliktāks. Ģirts Labots Septembris 1, 2009 - Guest Link to comment Share on other sites More sharing options...
stendec Augusts 19, 2009 Share Augusts 19, 2009 Hei.. Iepirku portjiku ar win7. Versija 6.1 gribēju pajautāt vai win7 bus versija 7 vai tāpat kā ar 2000 un xp abjibons??? Link to comment Share on other sites More sharing options...
zaruba Augusts 20, 2009 Share Augusts 20, 2009 btw, amazon.co.uk paslaik win7 home premium preorder ar shipping uz latviju sanaak ~64 lvl. http://www.amazon.co.uk/Microsoft-Windows-Home-Premium-PC/dp/B002DUCMT2/ref=sr_1_1?ie=UTF8&s=software&qid=1250751990&sr=8-1 Link to comment Share on other sites More sharing options...
dzordz Augusts 28, 2009 Share Augusts 28, 2009 Win7 ir smuks bet tie draiveri... bet tie draiveri... visu laiku saņemu BSOD da par visu pēc kārtas. Kā lai saved kārtība to saimniecību lai PC normāli strādātu. Kā jūs saliekat visus atbilstošos draiverus jo tas device manager driver update ir absolūti nekam nederīgs. Spēles vispār nereāli paspēlēt ilgāk kā 30 minūtes. Kaut kāda **** izlec ārā vienmēr. Bet nu jau sāk lekt ārā BSOD arī ne pie spēlēm. Par kompi: ASUS S775 IP43 DDR3 SATA2 GLAN 8-CH HD INTEL E8400 CORE2D 3.0GHZ 1333/6M S775 4GB 1333MHZ DDR3 NON-ECC CL9 DIMM KIT MSI GF GTX 260 PCIE 896M GDDR3 2X DVI OC CHIEFTEC PSU 600W 14CM ATX EPS CAB.M WD CAVIAR 500GB SATA2 7200RPM 16MB Minidump nevar pievienot... neesot tādas tiesības. Tāpēc to rakstu šeit: Microsoft ® Windows Debugger Version 6.11.0001.404 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Documents and Settings\Administrator\My Documents\Downloads\082809-16801-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol 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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`03042e50 Debug session time: Fri Aug 28 04:44:08.164 2009 (GMT+3) System Uptime: 0 days 5:27:53.647 ********************************************************************* * 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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ .................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {fffff980280e4e80, 2, 0, fffff88003c2aa2e} *** WARNING: Unable to verify timestamp for mssmbios.sys *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* Unable to load image \SystemRoot\system32\DRIVERS\L1E62x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for L1E62x64.sys *** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ********************************************************************* * 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+ * ********************************************************************* ********************************************************************* * 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+ * ********************************************************************* Probably caused by : L1E62x64.sys ( L1E62x64+6a2e ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: fffff980280e4e80, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff88003c2aa2e, address which referenced memory Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ********************************************************************* * 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+ * ********************************************************************* ********************************************************************* * 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+ * ********************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. FAULTING_MODULE: fffff80002e05000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4a30a802 READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd fffff980280e4e80 CURRENT_IRQL: 0 FAULTING_IP: L1E62x64+6a2e fffff880`03c2aa2e 4d8b2424 mov r12,qword ptr [r12] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 LAST_CONTROL_TRANSFER: from fffff80002e76469 to fffff80002e76f00 STACK_TEXT: fffff880`07a6b378 fffff800`02e76469 : 00000000`0000000a fffff980`280e4e80 00000000`00000002 00000000`00000000 : nt+0x71f00 fffff880`07a6b380 00000000`0000000a : fffff980`280e4e80 00000000`00000002 00000000`00000000 fffff880`03c2aa2e : nt+0x71469 fffff880`07a6b388 fffff980`280e4e80 : 00000000`00000002 00000000`00000000 fffff880`03c2aa2e 00000000`00000000 : 0xa fffff880`07a6b390 00000000`00000002 : 00000000`00000000 fffff880`03c2aa2e 00000000`00000000 00000000`00000000 : 0xfffff980`280e4e80 fffff880`07a6b398 00000000`00000000 : fffff880`03c2aa2e 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: L1E62x64+6a2e fffff880`03c2aa2e 4d8b2424 mov r12,qword ptr [r12] SYMBOL_NAME: L1E62x64+6a2e FOLLOWUP_NAME: MachineOwner MODULE_NAME: L1E62x64 IMAGE_NAME: L1E62x64.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- 0: kd> lmvm nt start end module name fffff800`02e05000 fffff800`033e2000 nt T (no symbols) Loaded symbol image file: ntoskrnl.exe Image path: \SystemRoot\system32\ntoskrnl.exe Image name: ntoskrnl.exe Timestamp: Tue Jul 14 02:40:48 2009 (4A5BC600) CheckSum: 0054B487 ImageSize: 005DD000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 0: kd> lmvm L1E62x64 start end module name fffff880`03c24000 fffff880`03c36000 L1E62x64 T (no symbols) Loaded symbol image file: L1E62x64.sys Image path: \SystemRoot\system32\DRIVERS\L1E62x64.sys Image name: L1E62x64.sys Timestamp: Thu Jun 11 09:45:22 2009 (4A30A802) CheckSum: 00011259 ImageSize: 00012000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 0: kd> lmvm L1E62x64 Link to comment Share on other sites More sharing options...
marciss Augusts 28, 2009 Share Augusts 28, 2009 pats arii kaadu nedeelju atpaklaj paargaaju uz w7. Vislaik seedeeju uz XP, paaris reizes piespiezhoties meegjinaaju paariet uz Vista, bet nu pat piespiezhoties nespeeju iemiileet vinju. Taga ar w7 viss ir chikiniekaa, vis labi, viss patiik un straaadaa. Bet ja jautaa kaada atshkjiriiba vista un w7, nevaru atbildeet. Karoch, laikam pie w7 arii palikshu. Veel iespamoshu vienu jautaajumu - ir 4gb rams (2+1+1) un bet uzraada ka ir 4GB (3.5GB available vai usable) tjipa tavo. Cik googleeju tad 32-bit sisteemaam vajadzeetu liidz 4gb njemt, taalaak jau 64bit jaaliek? Nekaadas TurboCache videokartes nav kas shaareetu ramu. Kuraa virzienaa skatiities? Probleema ir dzelzhu liimenii vai softiska? Link to comment Share on other sites More sharing options...
Kashmars Augusts 28, 2009 Share Augusts 28, 2009 Vai vēl ir kāda vieta kur var novilkt win 7 rc. Nepieciešams,o nomainījās plate un neielādējas, jo nav win7. Link to comment Share on other sites More sharing options...
Playwriter Augusts 30, 2009 Share Augusts 30, 2009 Man patika win7 pirmā testa versija, visas pārējās ir vairāk un vairāk apkrautas ar traucēkļiem, ja vistu prātīgi apregulē nav ne vainas:) Link to comment Share on other sites More sharing options...
neteiksu Augusts 30, 2009 Share Augusts 30, 2009 Jautājums ir tāds, kādu versiju man likt virsū 32 vai 64-Bit? Man pc ir: 4 GB RAM Dual core 2.1 Ghz ATI Rad. 4570 Un ar ko vispār viņas atšķiras tās versijas? Link to comment Share on other sites More sharing options...
Yozz Septembris 13, 2009 Share Septembris 13, 2009 atšķiras tikai ar to, ka viena ir 32 bitu versija un otra 64. Tev jāliek tāda, kāda tev ir sistēma, paskaties to, spiežot labo ausi uz "my computer" un izvēloties "properties" 2 Link to comment Share on other sites More sharing options...
wilz Septembris 13, 2009 Share Septembris 13, 2009 Yozz, vakara nagla 1 Link to comment Share on other sites More sharing options...
Yozz Septembris 13, 2009 Share Septembris 13, 2009 Yozz, vakara nagla nagla ne nagla, bet pateicu to, ko zināju, ja jau esi tik gudrs, ka vari tā "zviegt," lūdzu, izskaidro cilvēkam savu zinātnisko viedokli par to, ar ko šīs sistēmas atšķiras. Varonīgi jau nav apsmiet citu, varonīgi ir argumentētu viedokli paskaidrot, kāpēc kāds cits nav pareizs vai gana precīzs.. Kāds varētu man, lūdzu, pateikt, kāds Deamon tools darbojas uz šī jaunizveidotā windows? paldies. 1 Link to comment Share on other sites More sharing options...
Slavixs Septembris 13, 2009 Share Septembris 13, 2009 Kāds varētu man, lūdzu, pateikt, kāds Deamon tools darbojas uz šī jaunizveidotā windows? paldies. par deamon tools nezinu, bet izmantoju mountoshanai Power ISO, viss ir ok, man tas Deamon tools skiet neparociigs, nezinu kapec! Bet bracka vinju izmanto ari uz WIN7 un pahodu vinjam viss ir chikiniekaa! Link to comment Share on other sites More sharing options...
itaalo Septembris 21, 2009 Share Septembris 21, 2009 Kāds varētu man, lūdzu, pateikt, kāds Deamon tools darbojas uz šī jaunizveidotā windows? paldies. Daemon Tools versijai nav nozīmes, Win7 visu nosaka SPTD draiveris, tam jābūt ne zemākam kā v.1.58.Tātad meklē Daemonu, kam iekšā ir SPTD 1.58 un augstāk, pats gan SPTD draivu lieku atsevišķi ( netā var atrast ) un tad pliku tūli Link to comment Share on other sites More sharing options...
zubsters Septembris 22, 2009 Share Septembris 22, 2009 Grasos likt virsū win7, bet nezinu kuru versiju - 32bit vai 64bit. PC specs - video karte ASUS HD 4870 procis - AMD Phenom II x3 710 un 2GB RAM. Ar ko īsti atšķiras abas versijas? Link to comment Share on other sites More sharing options...
artilery Septembris 22, 2009 Share Septembris 22, 2009 ir 4gb rams (2+1+1) un bet uzraada ka ir 4GB (3.5GB available vai usable) tjipa tavo. Cik googleeju tad 32-bit sisteemaam vajadzeetu liidz 4gb njemt, taalaak jau 64bit jaaliek? Nekaadas TurboCache videokartes nav kas shaareetu ramu. Kuraa virzienaa skatiities? Probleema ir dzelzhu liimenii vai softiska? 32bit līdz ~3.5Gb ņem pretim, virs ~3.5Gb jāņem 64bit. Link to comment Share on other sites More sharing options...
zubsters Septembris 22, 2009 Share Septembris 22, 2009 2GB RAM ir par maz 64 bitu versijai. Liec 32 bitu versiju. Bet kas taj 64bitu versijā tik ūbers ka viņai vajag vairāk par 2GB ? Kas to RAMu tur tā ēd ? Link to comment Share on other sites More sharing options...
itaalo Septembris 22, 2009 Share Septembris 22, 2009 2GB RAM ir par maz 64 bitu versijai. Liec 32 bitu versiju. Kādas muļķības - pašam 2Gb rams un x64 versija.Pirmās betas gan vēl liku x84, bet jau krietnu laiku izmantoju tikai x64, strādā daudz naskāk un produktīvāk nekā 32bitu versija Link to comment Share on other sites More sharing options...
Persiks Septembris 25, 2009 Share Septembris 25, 2009 Kā jau Kams teica, 3-3,5 GB ir zelta vidusceļš starp 32-bit un 64-bit Windows 7 operētājsistēmas. Kaut gan ar 3,5 jau silti iesaku ņemt x64, manuprāt, ir jūtama atšķirība. Nevaru sagaidīt iznākšanas datumu. Tā kārojas iegādāt un lietot jau svaigu, lai gan jāmeklē iekārta, kurā saglabāt pašreizējos datus. Link to comment Share on other sites More sharing options...
janis Septembris 26, 2009 Share Septembris 26, 2009 ES pirms 3 dienam Vindows vistu 32 bit upgradoju uz W7 32bit, teiksu nekadu paslaik atskiribu nejutu, ir 4gb ram bet uzrada 3,5 gb, ar laiku pariesu uz 64bit. Atradu ar 1 taka bugu vai ka cakarejas garumzimes, tad ir tad nava, bet ta visa visuma ir ok w7 manu kompi noverteja biskin augstak neka vista Starp citu man upgrades ilga kur 2,5h kamer visus failus tur parnes. Link to comment Share on other sites More sharing options...
ggg97 Septembris 26, 2009 Share Septembris 26, 2009 Vispār jau maksimālam efektam iesak W7 likt no nulles, nevis apgreidot no Vistas. Link to comment Share on other sites More sharing options...
Eudoxus Septembris 26, 2009 Share Septembris 26, 2009 ES pirms 3 dienam Vindows vistu 32 bit upgradoju uz W7 32bit, teiksu nekadu paslaik atskiribu nejutu, ir 4gb ram bet uzrada 3,5 gb, ar laiku pariesu uz 64bit. Atradu ar 1 taka bugu vai ka cakarejas garumzimes, tad ir tad nava, bet ta visa visuma ir ok w7 manu kompi noverteja biskin augstak neka vista Starp citu man upgrades ilga kur 2,5h kamer visus failus tur parnes. Labāku rezultātu būtu ieguvis, ja taisītu clean install un liktu 64-bit Windows 7. Es arī no sākuma apgreidoju savu Vista Business 64-bit uz Win7 64-bit. Bet nesen uztaisīju clean install. Ir mazliet žiperīgāka sistēma, pazuda daži gļuki un uzradās brīvi kādi 10 gigabaiti brīvas vietas uz HD. Tā ka tas ir to vērts. Tagad gaidu oktobra beigas, kad atnāks jau pasūtītais win7 disks no amazon.uk.com (silti iesaku, jo tur pilna instalācija maksā 64mārcņas). Link to comment Share on other sites More sharing options...
Recommended Posts
Izveido kontu, vai pieraksties esošajā, lai komentētu
Jums ir jābūt šī foruma biedram, lai varētu komentēt tēmas
Izveidot jaunu kontu
Piereģistrējies un izveido jaunu kontu, tas būs viegli!
Reģistrēt jaunu kontuPierakstīties
Jums jau ir konts? Pierakstieties tajā šeit!
Pierakstīties tagad!