Добрый День! Хотя какой он к черту добрый,уже месяц не могу нормально работать в компьютере,все программы которые сохраняют данные в .ini .cfg и тд форматы свои настройки,выдают ошибку «Unable to write to %dir с файлом настроек/config.ini(.cfg)%» Дополнительная информация: Права администратора. Пытался делать через cmd-> attr Через Total commander. всё безуспешно. Очень прошу помочь с решением проблемы.
И тут еще одна проблема. Не могу установить NET Framework. При установке любой версии выдает ошибки,причем при установке разных версий ошибки разные.
Прошу ответить на оба вопроса. Но помогите лучше с первым!
Сообщения: 51908 Благодарности: 14931
Конфигурация компьютера
Материнская плата: ASUS P8Z77-V LE PLUS
HDD: Samsung SSD 850 PRO 256 Гб, WD Green WD20EZRX 2 Тб
Звук: Realtek ALC889 HD Audio
CD/DVD: ASUS DRW-24B5ST
ОС: Windows 8.1 Pro x64
Прочее: корпус: Fractal Design Define R4
Unable to write to %dir с файлом настроек/config.ini(.cfg)%
Проявляется ли проблема в безопасном режиме?
И тут еще одна проблема. Не могу установить NET Framework.
Если же вы забыли свой пароль на форуме, то воспользуйтесь данной ссылкой для восстановления пароля.
HDD: Samsung SSD 850 PRO 256 Гб, WD Green WD20EZRX 2 Тб
Звук: Realtek ALC889 HD Audio
CD/DVD: ASUS DRW-24B5ST
ОС: Windows 8.1 Pro x64
Прочее: корпус: Fractal Design Define R4
Что происходит при ручном (в текстовом редакторе) редактировании и попытке сохранения INI-файла?
Как с вирусами обстоят дела?
Скачайте ResetPermissions.zip, распакуйте в отдельную папку и запустите ResetPermissions.cmd (выполняться будет долго, дождитесь окончания). Если система английская, в скрипте надо заменить строку Администраторы на Administrators.
Попробуйте удалить файрвол и антивирус.
Выполните проверку диска.
С помощью утилит FileMon/RegMon или Process Monitor можно помониторить, что происходит при ошибке.
Решил проблему отключением Про-активной защиты Avira Спасибо за уделенное время.
А в процесс манаджере сразу не разобрался т.к привык что новые действия появляются сверху,а тут наоборот снизу,потом увидел процесс и понял что к чему
Сообщения: 51908 Благодарности: 14931
Unable to write files on Windows
I am trying to save some files using C, with this code:
It should set playerinput to the end variable, which works on Linux, then set the file location to the homearea/.notend, then make or edit the file, and put it out. In Linux (gcc), this works fine. The same code, however, on Windows (i586-mingw32msvc-gcc, does not work. Am I doing something wrong, or is another header file needed? Currently I have:
as my headers and defines. If you need more information, just ask.
2 Answers 2
The environment variable HOME is not a default environment variable on Windows so:
will return NULL . You need to use a different function to obtain a user’s home directory on Windows, SHGetFolderPath will provide this:
C:\Documents and Settings\admin\Local Settings\Application Data
To which location are you trying to write your file? Does the application have the right permissions to write to that location?
EDIT: Looking at the path style you just defined C://Documents and Settings//. , you should try it with C:\\\\Documents and Settings\\. . Note that there’s double backslash for each slash in the path. I’m not sure if fopen() would convert / to \ , so it’s worth a try.
If you’re sure that this would be running on Windows Vista and above you can get this path using getenv(«HOMEPATH») . I would suggest a macro definition like:
followed by: getenv(HOME_ENV) to get the home directory for the user.
Using OpenSSL what does “unable to write ‘random state’” mean?
I’m generating a self-signed SSL certificate to protect my server’s admin section, and I keep getting this message from OpenSSL:
What does this mean?
This is on an Ubuntu server. I have upgraded libssl to fix the recent security vulnerability.
8 Answers 8
In practice, the most common reason for this happening seems to be that the .rnd file in your home directory is owned by root rather than your account. The quick fix:
For more information, here’s the entry from the OpenSSL FAQ:
Sometimes the openssl command line utility does not abort with a «PRNG not seeded» error message, but complains that it is «unable to write ‘random state'». This message refers to the default seeding file (see previous answer). A possible reason is that no default filename is known because neither RANDFILE nor HOME is set. (Versions up to 0.9.6 used file «.rnd» in the current directory in this case, but this has changed with 0.9.6a.)
So I would check RANDFILE, HOME, and permissions to write to those places in the filesystem.
If everything seems to be in order, you could try running with strace and see what exactly is going on.
/.rnd made everything work out. – HalfBrian Jun 4 ’10 at 16:19
I know this question is on Linux, but on windows I had the same issue. Turns out you have to start the command prompt in «Run As Administrator» mode for it to work. Otherwise you get the same: unable to write ‘random state’ error.
One other issue on the Windows platform, make sure you are running your command prompt as an Administrative User!
I don’t know how many times this has bitten me.
Apparently, I needed to run OpenSSL as root in order for it to have permission to the seeding file.
I had the same thing on windows server. Then I figured out by changing the vars.bat which is:
then redo from beginning and everything should be fine.
You should set the $RANDFILE environment variable and/or create $HOME/.rnd file. (OpenSSL FAQ). (Of course, you should have rights to that file. Others answers here are about that. But first you should have the file and a reference to it.)
Up to version 0.9.6 OpenSSL wrote the seeding file in the current directory in the file «.rnd». At version 0.9.6a you have no default seeding file. OpenSSL 0.9.6b and later will behave similarly to 0.9.6a, but will use a default of «C:\» for HOME on Windows systems if the environment variable has not been set.
If the default seeding file does not exist or is too short, the «PRNG not seeded» error message may occur.
The $RANDFILE environment variable and $HOME/.rnd are only used by the OpenSSL command line tools. Applications using the OpenSSL library provide their own configuration options to specify the entropy source, please check out the documentation coming the with application.
Профиль | Отправить PM | Цитировать 
