salex

QUOTE (Morris @ Jan 7 2006, 21:43) QUOTE (salex @ Jan 7 2006, 18:34) NTFS не любит много мелких файлов и начинает на этом деле подтормаживать. Это не баг, а фича. Отключается простой поправочкой в реестре http://forum.academ.org/html/emoticons/huh.gif (Или запуском приложенного файла) Да знаю я про это http://forum.academ.org/html/emoticons/smile.gif и я не говорил что это баг.

NTFS не любит много мелких файлов и начинает на этом деле подтормаживать.

Нет неправда. Вернее не совсем правда http://forum.academ.org/html/emoticons/smile.gif

Спаять можно утюгом например.

Введение новых тарифов. В вз нет альтернативных сетей. Значит их придется сделать. В этом плане я полностью поддерживаю г-на aspopov.

Я так думаю, после проведения подобной акции, в вз такой контенгент появится.

Конечно нет.

А при чем тут программирование? Теме место в железе. Нажмите на кнопку включения и подержите так несколько секунд.

Скорее в BIOSе

Скорее всего это стандарт IEEE 1394. Сейчас есть и белее новые 1394а, 1394b. Если очень интересно, то можно почитать тут.

QUOTE (Amok @ Dec 15 2005, 20:56) у кого есть идеи где можно взять хорошие американские сериалы на русском языке? мне то может и хватит оригинальной озвучки, но как то это пошловато..... вот сейчас решил Buffy the vampire slayer собрать хочется Stargate (прохлопал), Farscape Да вот Stargate я бы судовольствием глянул, особенно новые серии.

Дату выпуска вряд ли удастся узнать. Только смотреть на самом чипе.

Да хрен его знает. У меня 2.0 corporate и оня точно не последняя. А в мануале для матери разве не написано?

QUOTE (::: @ Dec 7 2005, 22:14) PKS, слегка не догнал, на первых ревизиях P5GD1 стоял южный мост ICH5, если да, тогда вопрос исчерпан, а если ICH6, тогда всё сложнее...Можно ли програмно определить серийник у ЮМ? По крайней мере Сандра не умеет (или не хочет). CPU-z определил тип SouthBridge: 82801FB, Chipset revision B1. Поставьте Everest, там можно посмотреть информацию про мосты.

Попробуйте с этой веткой поэкспериментировать. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Hardware Profiles\0001\System\CurrentControlSet\Control\VIDEO

Похоже где-то дыра и память утекает. Вот только где.... Если это на уровне системы, то увы спасет только перестановка.

Не только. От 50 мегатон ударная волна 3 раза обошла земной шар. Делали какие-то расчеты, вродебы могла и расколоться(или сдвинуться с орбиты, точно уже не помню).

QUOTE (Dagaz @ Dec 6 2005, 13:29) QUOTE (Bugrim @ Dec 6 2005, 13:27) Предлагаю нашему государству помочь воплощением этой мудрой идеи в жизнь, чтобы немного услить прыжок и без того больших(толстых) и умных людей, направить к ним дружественную помощь, в виде всего ядерного боезапаса, ведь людям надо помогать, а чем мы еще можем?! а вот ядерным боезапасом наверное можно Землю пошевелить В) А почему Вы думаете 100 мегатон побоялись взрывать?

Вообще, любые микросхемы деградируют от повышеных температур и напряжений.

http://www.apcmag.com/apc/v3.nsf/0/90E6832...11?OpenDocument

QUOTE There are four top reasons that account for the vast majority of BSODs: Bad hardware Never a pleasant prospect to face, but the truth is that hardware — motherboards, hard drives, memory — ages over time and becomes less reliable. Windows 2000 and XP are far stricter about hardware than 98/Me, and what worked before may not work now. (This often shows up when someone upgrades a decrepit system to 2000 or XP and experiences a BSOD during or after the upgrade.) Often one particular component can be the culprit. Nine times out of ten it’s bad RAM — and again, RAM that was "good enough" for 98/Me may not fly in 2000/XP. If the BSODs seem to come and go with no rhyme or reason, bad hardware is usually the culprit — that, or... Environmental conditions Dirty or fluctuating power, dust and simple overheating can cause a system to BSOD. Put your system on a UPS to take care of power problems, and take a peek inside your computer if you haven’t lately. Are all the fans plugged in and turning? Fans can get choked with dust and die over time; if they don’t respond to being cleaned, consider replacing them. Also, is the internal airflow blocked by too many cables? You may want to gang cables together with twist-ties or use rounded IDE cables if you’re having airflow problems due to too many wires. Finally, if the room itself is too hot, that may be a contributing factor. Bad kernel drivers Drivers that work directly with the lowest level of the OS are called kernel drivers, and a badly-written one can give your system a BSOD. If you weren’t having BSODs before you installed a given software package, consider uninstalling the program and running the PC some more to see if the problem goes away. Antivirus products, video card drivers, low-level system utilities and media controllers are all possible culprits. Also, check with the maker of the program to see if there may be an update or a recommended workaround — some programs won’t work reliably in anything less than a given Service Pack, for instance. Hardware conflicts Newly-added hardware can sometimes conflict with other hardware already installed in the system. This sort of thing has become mercifully rarer over time, but every now and then it does happen. Some hardware even conflicts with the motherboard of a specific system itself. Hardware conflicts can sometimes be resolved with updated drivers for the conflicting devices, or with a BIOS revision for either the computer or the device itself. Let’s have a look at the BSOD itself. Generally, at the very top of the screen there is a line with the label *** STOP: followed by a series of numerical codes, called parameters, and a text description of the crash. The codes are used to provide additional information about the crash and vary from error to error. Below that is usually a list of the services and drivers running at the time of the crash, and the memory address of the crash (which isn’t too useful unless you’re a programmer). Here’s a rundown of the most common BSODs, their corresponding error information, and some possible resolutions. PAGE_FAULT_IN_NONPAGED_AREA Probably the most common error thrown when a BSOD pops up, this happens when the system tries to read memory that isn’t valid. This usually occurs when there is faulty hardware in the system causing data corruption — either bad RAM or a corrupt NTFS volume in Windows 2000/XP. However, it can also happen if a faulty system service or kernel-level driver has been installed. If this error pops up after adding new software, you may want to remove it and check with the manufacturer for possible conflicts with other programs, or whether or not the program needs to be run in conjunction with a particular Service Pack or hotfix. IRQL_NOT_LESS_THAN_OR_EQUAL Usually the result of a badly-written kernel driver or a hardware conflict. For instance, some early revisions of the SoundBlaster Live! driver for Windows 2000 had this problem, but only on certain varieties of motherboard. If this happens, try yanking any newly-added hardware and see if that changes anything; if you haven’t added anything in hardware, check your software. Another possibility is to check and see if your video or sound card drivers have been updated by the manufacturer — a newer driver may fix the problem. KMODE_EXCEPTION_NOT_HANDLED Most likely caused by an incorrectly configured device driver, but this can also pop up on machines that have a bug somewhere in their system BIOS. Check if your motherboard has a new BIOS available for it; if so, try flashing your system with it and see if that improves things. If you installed a newer device driver for something and got this error, roll back to the last device driver you installed and see if that changes anything. UNEXPECTED_KERNEL_MODE_TRAP Bad memory is almost always the culprit here. Make sure all your memory is seated correctly and clean (dirty contacts can cause memory problems). Off-brand or cheap memory can also cause terrible problems, so spend the extra money and buy from a reputable manufacturer like Crucial, Mushkin, Kingston or another name-brand memory maker. KERNEL_DATA_INPAGE_ERROR This happens if Windows can’t read from its own pagefile. Hard drive errors — bad cabling or a disk defect — are the usual suspects for this one. Cables actually develop defects more often than hard drives do, so try changing out your cables. ("Rounded" hard drive cables are apparently far less error-prone than "ribbon"-style cables, and clutter the inside of your system less, too.) INACCESSIBLE_BOOT_DEVICE As the name implies, this error comes up when Windows can’t find the hard disk used to boot the system. This usually happens if someone has tampered with the drives or cabling, or if the device driver that handles I/O to the boot drives is not loading. If you’ve installed a newer version of your disk controller drivers, for instance, you might get this if they’re not working correctly; boot to Safe Mode and roll the drivers back. Newly-added hardware might be conflicting with the controller or trying to usurp its functions. STATUS_CANNOT_LOAD_REGISTRY_FILE This is generally one of the worst possible BSOD errors, usually reported during boot. The Registry, the system’s repository of settings and system data, could not be loaded for some reason. Sometimes this is due to a simple communications problem with one of the hard disks (a faulty or unplugged cable), although it may also be due to data corruption. A corrupted Registry needs to be recovered through the use of the Emergency Recovery Disk, or via a System State backup. If you have no backup copy of the Registry, you’ll need to reinstall Windows — another reason to make Recovery Disks and System State backups. STATUS_IMAGE_CHECKSUM_MISMATCH Another possible disk-corruption or drive-cabling problem, this happens when the checksum for a system file doesn’t match the data in the file itself. If in fact the file in question is damaged (and you’ll get a report as to which file threw the error), you can often replace it by simply booting to the Recovery Console and copying out a clean copy from the CD-ROM. Alternatively, you can boot the Emergency Recovery Disk to perform the repair. Bad RAM can also cause this kind of data corruption. If you get this error a lot with different files, there may be something fundamentally wrong with the system’s hardware, since you’re probably looking at a widespread data corruption condition. P.S. а Google использовать несудьба? Куча ссылок на подобную проблему, поищите.

mihas.academ.local

Толькл перед этим сделать бэкап реестра, так, на всякий пожарный.

Посмотрите, какой процесс кушает процессорное время.

Вот, нашел тут программку, которая патчит винды. После этого можно спокойно все скачитвать и ставить. twk_winupdatepatch.zip