Jump to content

Losnad

Member
  • Posts

    16
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Romania

Posts posted by Losnad

  1. Why don't you first add the language pack and then vlite your image ?

    A very good advice, but not for vLite... unfortunately. LIP cannot be integrated using vLite, especially (and I believe ultimately) into a 64-bit version of Vista. I experienced it myself a couple of times with Ukrainian LIP for Vista sp1 64-bit intergration, and I am not the only one with this unpleasant experience. C.p. http://www.msfn.org/board/Error-integratin...641#entry781641

    I have Vista Ultimate x64 SP1 and i integrate romanian just fine. But this must be do it on vista unmodified instal. If you try to do this on a vlited install will fail. I do it on this way: installed original vista, searh for updates, select romanian language pack, install and after the download is complete, during instalation process i go to C:\Windows\SoftwareDistribution\Download\Install and there is a lp.cab which i copy and save it where i have drivers and updates. Then i start vlite and i integrate that lp.cab, drivers and updates on the original untouched vista install. This will take some time... After you install a modified vista any other try to integrate a language pack will fail.

  2. Can anyone confirm that deleting these does no harm? It seems that all registry cleaners end up in strange loops with those entries. Pretty pathetic from Microsoft, to have a bug like that in a full-blown OS like Vista.

    Yet another reason why vista sucks.

    I can confirm it will not harm. Read here: http://www.msfn.org/board/registry-Wow6432Node-after-sp1-t121898.html , in short line: HKLM -> SOFTWARE -> wow6432node -> wow6432node (-> microsoft..windows.. etc ..iexplore.exe)just delete the last wow6432node...

    It's true that even Windows Live OneCare safety scanner have a huge loop because of this, i'm agree with you that this is pathetic, and untill now i wasn't found what is the cause of this bad entries and how to avoid this, but now i know how to fix this. I can not say vista sucks because of this...it's not perfect, but is much better than xp, xp give me much more headache. My only complaint is the size and inability to remove unused features, this was fixed thanks to Nuhi.After one year with vista ultimate 64 without any blue screen or any major problemm i say: i will never go back to xp, but you are free to make the change if you feel like this. I really can't understand all the negative advertising against vista, at the beginning i was influenced by this, but i say to give a try and i don't regrete this any second. After few tests with vlite i finaly make vista how i wish.

  3. Also, idk why, but when I'm burning images with 1.2RC, my DVD's won't boot. When creating ISO, the "Boot sector" option is "Default" and can't be changed (it's grey) and when I'm trying to reboot, there is no "Pres any key..." text apears, PC trying CD's, then going to boot from HDD. The first boot device in BIOS is CD-ROM, also I have 2 DVD-RAM (Asus DRW-1608P3S IDE 1.24 and Asus DRW-1814BLT 1.13 SATAII), I tried to burn disc on both of them and it wasn't bootable.

    Previously, when I used 1.6.6 to build an images, all worked correctly.

    I think maybe is because you try to burn on a dvd-r, try with a dvd+r or create(save on hdd) the .iso with vlite and burn it with another programm like this: http://www.imgburn.com/ (free, small and easy to use). At least in my case this was the problemm, i wasn't able to boot from a dvd burned with vlite on dvd-r, i really don't know why...because i didn't see to be mentioned somewhere that only dvd+r can be burned with vlite.

×
×
  • Create New...