Computing space requirements ableton что делать
Что происходит во время «Требования к вычислительным пространствам»?
Почти каждая настройка, которую я знаю, показывает что-то вроде этого в начале:
Это иногда выполняется всего несколько секунд, а иногда и значительно дольше.
«we are doing something here and won’t tell you what.»
Хотя не может быть общего ответа на все настройки, которые печатают «Требования к вычислительному пространству», что они на самом деле делают, возможно, существует правило большого пальца.
Мой вопрос:
Что происходит во время выполнения настройки, когда настройка занята, и записывает «Требования к вычислительному пространству»?
3 ответа
Определяет, какую часть программы он должен установить, и определить, какой размер будет на диске. Существует несколько факторов, например, функции, которые пользователь выбрал для установки, и состояние текущей системы.
Многие программы полагаются на общие зависимости, но если эти зависимости не поставляются с ОС или не поставляются с разными версиями этих библиотек, возможно, приложение должно будет установить их самостоятельно. Или, может быть, еще одна программа уже установила его.
Это означает, что фактическое воздействие диска на установку программы может сильно различаться. Требуется время для поиска на диске и в реестре, чтобы определить, доступна ли зависимость в системе, поэтому пользовательский интерфейс отображает это сообщение, чтобы сообщить вам, что он делает.
Одним из основных требований к установке программного обеспечения является Disk Space.
Чтопроисходитвовремя«Требованияквычислительномупространству»?
Посмотритенаэтуошибкуустановки,например:
Computing space requirements ableton что делать
So I just tried installinng calibre-0.7.24.msi and it got stuck at the «Computing Space Requirement» screen. I tried searching through the bugs but the advice there was rather unhelpful.
Turns out you need to uninstall the old version of Calibre first.
So I just tried installinng calibre-0.7.24.msi and it got stuck at the «Computing Space Requirement» screen. I tried searching through the bugs but the advice there was rather unhelpful.
Turns out you need to uninstall the old version of Calibre first.
I waited at least ten minutes. According to the bug database one person waited an hour. Clearly the install routine has a bug of some sort in it.
So I uninstalled and installed the new version. There was no wait of any sort on the install then.
This delay has been talked about before. Without a ticket number I can’t view exactly what bug report you’re referring to. Since this version has been out for 5 or 6 days and you’re the first to experience a longer than usual delay, I doubt there is any current bug, but anything is possible. My own experience was the normal minute or so.
Believe it or not they took an extensive look with programmer very familiar with this MS install package. Some things were tweaked and it went from a 10+ minute wait to a 1-2 minute wait. I can’t locate the thread but it was a very interesting read.
I’m not sure why your upgrade took so long. For that matter I’m going on feel, my upgrade time to get through the «Computing Space Requirement» area might have been longer. Just for fun I’ll time it next time.
Well, Microsoft is to blame, believe it or not. And, as mentioned before, a couple of people including a programmer with extensive knowledge of the installer system have tried to get rid of that. The reason the space requirements are taking so long is that the installer is optimized for executable files and DLLs, not Python files. The files normally packaged in an installer package contain a checksum of their contents for the purpose of quickly detecting changes, the many Python and other files Calibre brings don’t. Thus, the installer has to generate checksums of not only the files it contains, but also the entire Calibre directory to see which files have changed. This is, as you surely would point out, unnecessary, since you could just go ahead and overwrite everything, but, as it turns out, it’s impossible to turn off that behaviour. So, your options are either to do something about it (although I couldn’t say what one could do) or just deal with it.
Generally, if a ticket indicates that the bug won’t be fixed, it’s either for some technical reason like above or because it comes from a design decision that won’t change (or won’t change anytime soon). If you wish to know the reason behind it, a search in this forum should unearth the relevant thread(s). Were I a developer, I’d be pretty annoyed if people showed up out of thin air and concluded, that, since their pet bug won’t be fixed, clearly nobody is interested in doing so.
Manichean, thank you for the explanation. The responses I read in the two or three bugs was quite short and dismissive with no explanation of what was going on and the reasons why.
I have a total of four books in the Calibre directory. I suspect the installer is trying to do checksums on the entire drive then.
Why not use a different installer? Such as the freeware Inno.
What happens during «Computing space requirements»?
Nearly every setup I know shows something like this at the beginning:
There is a text saying:
This sometimes runs just a few seconds and sometimes significant longer.
Since checking for free disk space is to me the equivalent of simply calling fsutil volume diskfree c: which takes about one second maximum, the message seems to be an euphemism for:
«we are doing something here and won’t tell you what.»
I’ve already tried to use Process Monitor to see what’s going on but found nothing significant.
While there might be no general answer for all setups out there that print «Computing space requirements» what they are actually doing, maybe there is a rule-of-thumb.
(My example screenshot was taken randomly from Markdown Edit which uses the WiX Toolset)
My question:
What happens during setup execution when the setup is busy and writes «Computing space requirements»?
3 Answers 3
It is determining how much of the program it must install, and determining what the size on disk will be. There are several contributing factors, like the features the user has selected for installation, and the state of the current system.
Many programs rely on shared dependencies, but if those dependencies do not ship with the OS, or ship different versions of those libraries, the application may have to install them itself. Or, it may be that another program has already installed it.
This means that the actual disk impact of installing a program may vary widely. It takes time to search the disk and registry to determine if the dependency is already available on the system, so the UI displays this message to tell you what it is doing.