Comments for Cloudwisp

Comment on Ubuntu Graphical Boot by Alex

Alex — Wed, 30 Jun 2010 14:54:59 +0000

Thanks much Rols, I think I’ll just bite that bullet.

Btw just to clarify, I do actually still use my Windows partition; it just gets detected twice (so my choices are Linux-Windows-Windows, where both Windowses are exactly identical).

Comment on Ubuntu Graphical Boot by Rols

Rols — Sat, 19 Jun 2010 18:36:25 +0000

If you don’t want to edit burg.cfg, the easiest solution would be to format the partition that contains your old XP. If you want to keep the data on that partition, you could also try deleting the windows folder and the boot.ini file. But I’m not 100% certain that will stop the OS prober from detecting it.

If you want the option to at sometime in the future boot into that dormant XP, you would have to bite the bullet and edit burg.cfg

Personally I suggest just disregarding those warnings in burg.cfg, and edit the file. As long as you follow the instructions and only delete the portion shown in step 3, nothing will go wrong.

My guess is that the warnings are there to make it clear to people that things have changed since the original grub. Because there’s still plenty of guides online that talk about editing the config file to add new menu items and change settings.

As a footnote, if you are good at scripting (I think it’s linux shell script), you could edit /etc/burg.d/30_os-prober, and catch the old OS and stop the script from including it in burg.cfg

This is also a more permanent solution, but something beyond my abilities, and probably more risky than just editing burg.cfg

Comment on Ubuntu Graphical Boot by Alex

Alex — Sat, 19 Jun 2010 13:51:50 +0000

Thanks a lot, this is exactly what I needed. I still fear comments in text files like “DO NOT EDIT THIS FILE” so I haven’t done Step 3 (it recognised some dormant XP installation of mine), is there some way around that (apart from blatantly ignoring the warning)?

Comment on Ubuntu Graphical Boot by Shakir

Shakir — Fri, 18 Jun 2010 04:22:27 +0000

Very Nice.. Good job.. Thanx a lot.

Comment on VB.net and Visual Studio 2008 by eating-for-children

eating-for-children — Sun, 13 Jun 2010 08:31:42 +0000

eating-for-children…

eating-for-children…

Comment on DAoC Settings Switcher by Rols

Rols — Mon, 12 Apr 2010 17:28:47 +0000

Unfortunately no. But I can tell you how you’d back them up.

Get a USB memory stick or something to back them up to, and then find the folder that holds your settings.

If you’re using windows XP, it’s: (make sure you have enabled hidden folders and files)

Documents and Settings\(your user)\Application Data\Electronic Arts\Dark Age of Camelot\LoTM\

In Vista and Win7 it’s:

Users\your user)\AppData\Roaming\Electronic Arts\Dark Age of Camelot\LoTM\

Copy all the stuff in this folder.

When you reinstall your OS and DAoC, log into DAoC and log out/exit, and it will create the folder again.

Then navigate back to that folder, and paste all your files. Next time you log in, all your settings should be back.

Comment on DAoC Settings Switcher by Fred

Fred — Mon, 12 Apr 2010 13:25:44 +0000

I want to reinstall my OS, can this save all my settings to restore after I’m done with reinstall?

Comment on DAoC Settings Switcher by Rols

Rols — Wed, 24 Mar 2010 20:56:03 +0000

I have uploaded a new release that should solve your problem. Let me know if you still have troubles and I will have to get back to the drawing board.

Comment on DAoC Settings Switcher by Tarrell

Tarrell — Tue, 23 Mar 2010 09:58:30 +0000

Yep I am running Windows 7

Comment on DAoC Settings Switcher by Rols

Rols — Mon, 22 Mar 2010 05:24:07 +0000

I did some reading up about this. If you’re using Windows Vista (or maybe even 7?), I believe that the OS won’t allow programs to write to the program files directory after the install is complete.

The files are supposed to be placed in the app data directory. So I will have to fix this.

In the next couple of days I will change the program and post a new version. So keep an eye out.

After i’m done, existing users whose program works fine will probably have to run the restoration tool built into the program to get their characters registered into the program again. It’s quick and painless.

Thanks for the bug report!