Registry values reset after Reboot

[twelvegates]

Hello,

I'm trying to set some TcpIp parameters of an network interface in the registry. After closing the registry editor and restarting it again the changes seem to be effective.
But after reboot the old values show up again.
I'm running ReactOS in Qemu. I'm not quite shure which option is the rigth one to turn the host off. Usually I use "Log off..." from the start menu."Turn off..." doesn't seem to do anything,
How can I save registry entries accross reboots?

-Hanspeter

[Jaix]

Hello,

I'm trying to set some TcpIp parameters of an network interface in the registry. After closing the registry editor and restarting it again the changes seem to be effective.
But after reboot the old values show up again.
I'm running ReactOS in Qemu. I'm not quite shure which option is the rigth one to turn the host off. Usually I use "Log off..." from the start menu."Turn off..." doesn't seem to do anything,
How can I save registry entries accross reboots?

-Hanspeter

This is really strange, i have never lost a changed registry value like this. The only thing you really should need is to klick the ok button after you have changed the the registry and it should be active, check it by changing the subnet mask and type ipconfig /all at the command prompt. The values should be effective right away.

[GreatLord]

The PnP manger are parti in place. and new bugs have been show up. please mentor them in bugzila or talk with us at the channel if the problem still exists.

[twelvegates]

It seems I have encountered a new feature:
[ external image ]
Maybe I'll reinstall ReactOS.

[Ged]

That generally means your registry is corrupt.

Reinstalling is your best bet.

[hbirr]

It seems I have encountered a new feature:

Can you test it again with r19187 or later?

- Hartmut

[Ged]

Hi Harmut.

I tested it last night in vmware with R19240 and got the same error.

It was working for me once Ge fixed the memory corruption bug, but it's broken again within the last day or 2.

[Jaix]

It seems I have encountered a new feature:
[ external image ]
Maybe I'll reinstall ReactOS.

A new installation woan't help with this error, you have to refromat the partition, but if you have a dual boot system or just don't want to reformat there is another solution.

Boot up from a floppy boot disk or a other dual boot system and go to the c:\reactos\system32\config\ directory there you delete all files and then you reinstall ReactOS, this works.
Happy testing!

[twelvegates]

A new installation woan't help with this error, you have to refromat the partition, but if you have a dual boot system or just don't want to reformat there is another solution.

But now I have already installed again.

Boot up from a floppy boot disk or a other dual boot system and go to the c:\reactos\system32\config\ directory there you delete all files and then you reinstall ReactOS, this works.
Happy testing!

I have now made a dual boot system.
Then the first now gets into

Code: Select all

CSR:  CsrServerInitialization failed.

during boot
and the second gets into System Hive after I had tried to delete the files in c:\reactos\system32\config\. But there was some event file I couldn't delete.
[ external image ]

[twelvegates]

Can you test it again with r19187 or later?

Maybe. But I'll try again when 0.2.9 or 0.3 is available.

-Hanspeter

[Ged]

Get one of the prebuilt isos from here : http://svn.reactos.org/iso.

It could be a month or 2 before the next release.

[twelvegates]

Get one of the prebuilt isos from here : http://svn.reactos.org/iso.

And which branch? The trunk one?

[florian]

I would say trunk.

[Ged]

Yes, if you use branch:trunk (which is default), and then hit 'get latest' it will fill in the latest build for you.

Everytime there is a commit to the repo, Caspers SIN system builds the code and makes a new iso. 8)