nuhi

Ok let me put it this way: it doesn't work for you but it works for the majority. Use Nero after ISO is made. Don't get me wrong I would help but I don't have the code of that burning engine, it's used with license, legally but I don't have the code and they are slow in replying so I stopped bothering in reporting bugs to them.

I appreciate the positive feedback. Maybe their goal is that admins keep their jobs. If it's too easy then anyone would be able to do it (and potentially make a mess though)

Interesting, will check then. Let me know if you find out anything more.

Yeah that happens if it didn't detect that the cd was full and started writing, or the rw was corrupted (needed full erase), or simply corrupted, or the drive needed refreshing (eject - load or reboot), or simply drive isn't supported but that hasn't happened yet, it's usually one of the first glitches.

Progress bar going forth and back during erasing is normal, you should have waited. Works for me just fine. But of course if you want better burning software use Nero.

Cantloginin, I tried that the other day and the unattended settings weren't applied, is that true for that method? mj084, Application Experience is the component on English.

hehe I get the point.

I'm not familiar with that site but it sounds like it's a big deal so yey

ripken204, What he said

aviv00, right to the left writing, if I remember correctly your language is like that? If you can read from left to the right then ok, contact me on email.

aviv00, but it doesn't support RTL. d0p3y2k4, you can download Autopatcher Vista and once installed it will have all the fixes in one folder. McDoul, works fine here. shabador, please attach your preset, and if you can the last session_u.ini as well but first edit it and change sensitive data with some mumbo-jumbo and keep the same synthax.

Sometimes just uninstall helps, checked. It won't bsod for no reason. Then I would get the same issue as well. Also reset Temp folder option to default.

strotee76, ok. mj084, antivirus clash, known issue, not my fault unfortunately (as far as I know).

Run it and there should be lp.cab file in the same folder (or is it temp folder) once it starts installing it. Copy that LP.CAB aside and you can cancel LP.EXE.

And which part of the "you didn't use vLite so what are you searching here" didn't understand?

Hotfix and Language Pack integration! It can be maximized, it checks if your removal will break kept components... Changes and download.

Update it, I heard they fixed it in the newer version but maybe not. Download separate for Vista ver.

rudebwoy, no offence but please stop posting like it's a chat room. Think and write all at once then wait, or research.

Breathless19, out of luck, luckless19.

In that case we can't help you, that is an MS bug. I already said that the vLite is not the only cause, we only found our solution, sorry but you'll have to wait a new hotfix release or something. Check Microsoft forums for a possible solution.

inferno128, problem is this. You are on the 32bit os, right? And this is 64bit hotfix which is integrated normally, direct integration is not supported, but it's a next best thing. Anyway if you were to try this in the 64bit OS it would work. IrfCore, what kind of attitude is that?

Extract it to a specific location, lets say C:\ then go Start - Run (or Win+R) - type: regedit c:\fd.reg or whatever the reg file name was. It should popup something about merging.

That means that you gave your Virtual machine less memory. Vista, and any Windows in that regard, use more memory if it's available (certain percentage of total). That is why with more memory Windows feels faster, smoother.

Some removals don't break it but I haven't finished the search so it's best to not use it on the Server if you plan on adding features. It won't be fixed in the 1.1 beta but I will try to fix for 1.1 final.

This option works on RTM but not any more after the KB938979 so I won't be including this option into the next version.