Search options (Page 47 of 58)

Did you already contact them in order to make them aware of the problem?

Just wondering.

Obviously, this is an unaccpetable solution but if they don't know they can't fix it

Nope, sorry.

Besides, I've shared all information I have about this with you already.
There's really nothing else I could tell you.

Correct observation!

Forum rules (basically Bâsh's wish) say only English as that's what basically everyone can read.
Therefore, no German talk...

Nope, Pro here.
Though I will be using Home in a week or two on my cousin's PC.

I never found out what it was due to.
It certainly wasn't caused by anything on my side, as it happened when I created a CD with everything the same as on the previous one, just a newer BASE version.

And so there is 1.2 RC now:

http://nliteos.com/download.html

v1.2 RC
fix: Verify burned files 
fix: Desktop Theme integration when only one .theme file integrated 
fix: Desktop Theme import 'InvalidArgument' error 
fix: Cluster service removal was breaking Windows 2003 Enterprise edition 
fix: Windows 2000 command prompt tweak title 
fix: Proper burner selection with multiple drives 
fix: Tweak: 'Remove Help and Support' from start menu was missing 
fix: Services showing after removed 
fix: ISO page crash if no recording device in the machine 
fix: Mouse cursors leftovers if removed 
fix: Domain Group User and Password textbox disabled 
fix: NTFS.SYS boot error if more than one SP and merged 
fix: Windows 2000 Update Rollup 1 integration 
update: 16-bit support component not needed for DirectX install 
update: Allowed asterisk for Computer Name 
update: Direct integration for KB918899 non-English 
update: Printer Support compatibility now protects Smart Cards component

Sicherlich, ist ja auch meine Muttersprache!

Ich hätte auch nichts dagegen, wenn alle Deutsch sprechen würden, aber da das nicht der Fall ist...

Heh, yeah

I'm still using Nero, though, since using that short leadout setting I am able to squeeze an additional 15MB on the CD which nLite is unable to achive.
Also, it does not support overburning (generally not needed but you never know...), so it's really just for those folks that want a quick burn instead an ISO file.
For me, it's rather useless since it does not offer enough "pro" settings.

I'd rather see ISO creation in the BASE, though

Ok, The Input Pack indeed contained both the LogiTech drivers.

Hence, I updated that pack with SetPoint 3.1 and removed the redundant LogiTech pack.

The new link is:
http://3rdpartydriverpacks.thesneaky.co … 2_60928.7z
MD5: 3931E71CAE4F298F41224583E9469FE6
Size (comp): 2.65MB

Hm, that is strange, because I had it on my HDD and it was properly named and had the right folder structure...
And this is the first time I touched it, simply because I saw the release of the new driver on a news site.
I don't have Logitech devices myself so I never bothered with it before

RGR.
Personally, I'm using all lowercaps myself, but that's fine by me.
I guess I only wrote it "Lo" instead of "LO" because the "o" is noseperate syllable.
If we were to use LogiTech (LT), then the T would be uppercase
Whatever, not that it's important, just trying to explain how I do this stuff

Then it contains the same stuff as the Logitech pack...
I'll look into that.

Is that version newer than that of RC2 and if so is it recommended using it for beta testing as it will give a more comprehensive feedback?

What would your MoBo have to do with your SC?
On-board or what?

Basically, you don't need to know what HW you have since this involves no manual input.
Only when drivers are not getting installed (little yellow exclamation marks in the device manager) you will need to obtain your HWIDs as well as find out the actual product to help Bâshrat the Sneaky get it to work

Don't thank me, I had nothing to do with this, I swear