GrofLuigi

I have a problem with that thread. Although he seems to go 'myth busting' he gives no actual evidence except 'that and that speed is better supported by the drive/media'. What does supported mean? In which way one is supported better than another? I agree with what he wrote that there is much misinformation and word of mouth about this carried over from the old times (times of CD writing). But CD/DVD writing (I'm not talking about anything higher, i.e. BluRay, as I have no experience with that) has been an evolution - over time only the choice of materials and speeds changed, everything else is pretty much the same. And we still live in the same universe where the laws of physics haven't changed (more speed = more jitter). And I haven't heard of any claims by the manufacturers of 'new technology' - that would be major selling point for them, worth at least a press release. So I cannot imagine how in the world any higher speed can be better than any lower speed (under ANY circumstances). If it is true, it can be only due to bad/unoptimized write strategy of the burner. GL *Edit: That thread isn't so bad after all. All I had to do was turn a page.

With PCs of that era, I had great success with Motherboard monitor. (The original site of MBM seems to be down). GL

I think it would be better not to integrate both drivers (synaptics and Intel Inf) at least until you resolve the issue (with experimenting, if you have the will to do it). Experimenting = what happens if you install synaptics driver on a full windows installation? Does it work then? Also, on nlited installation but without synaptics integrated. They are non-essential for the operation of windows. You can install them later after installation. About your question about Intel Inf - I don't know, as I've never integrated it. Maybe someone else can tell, I'd like to know too. Good luck and happy nliting. GL

The least time consuming options are: 1. Put the hard disk in another working PC as secondary drive or 2. Do a repair installation of XP GL

I've heard many praises about Venta Fax for this purpose. (I haven't used it myself). But if you are asking about something that works with your speciffic hardware (router) then I don't know... GL

I found nLite pretty good at adjusting to new settings. I have one configuration that suits my needs that I basically carried over for years. When a setting is depreciated (or spelling mistakes corrected!) it is silently deleted or modified. At one time I experimented with recreating same configuration from scratch and it was identical. OK, there is still pretty big chance I haven't hit the right (or wrong ) combination of settings, but it's enough for me. Sometimes I still encounter minor glitches (not applying tweaks), but as long as installation completes, most of them can be corrected, and I believe it's Windows fault, not nLite's. Plus, I think (I'm not 100% sure as I've never used it or I used it long time ago) you can import last session.ini on a page by page basis. GL

I think the only way to know for sure is to do a (test) install of full XP. Restore the original file from the original CD. But which file was it... portcls.sys? Google tells me it's usbport.sys (unless Nlite does it differently). GL

From my experience, NOTHING can break mouse support. Even if you removed everything in nLite (and lived to tell ). I examined your last session ini and nothing stands out. Maybe USB polling patch. Other candidates (VERY slim chance): Multifunctional, Serial Pen Tablet, Multi-port serial adapters. One thing I would suspect is you have the wrong driver and/or one that depends on something removed. GL

Hi Tripredacus, Sorry I don't have anything to add to your issue, but this has caught my eye: Do you (or someone else) know whether it's possible to edit this database on a normal Windows installation? For the purpose of removing items. I think Microsoft Application Compatibility Toolkit doesn't let you remove, just add things (it was a long time ago since I looked into it). Also, does something else exist that is capable of editing it? GL

You have a go! (Well, since you asked...) B) GL

False positive? I've seen fair share of driver problems with both manufacturers. Just google "ati hotkey" for example. GL

One line of thinking (not necessarily true) would be that it is a CD read/write error, since that is the largest file and most easily hit by a bad bit. Don't worry, I'm sure he had plenty of time to sort it out (almost two years). But welcome to you to this forum. My advice would be to re-copy the files from your original XP CD, and/or verify the CD's integrity. Check your computer for viruses, and (as a last resort) temporarily disable your antivirus while working with nLite (there were some reports in the past that AV programs interfered with nLite's operation). GL

Hi grandmaster, and welcome to the forum. First of all, are you sure it's freeze and not blue screen (0x0000007B)? You didn't list your motherboard (or the full name of the laptop), but if it has a SATA controller, it needs drivers to be integrated into XP setup. That is by far the most common reason for XP instalation failure on recent computers. Also, please note that nLite's license doesn't allow it to be used in business environment. Of course, there might be numerous other reasons (hardware failure of other components, defective or inappropriate CD)... GL

ahmad2080, Yeah, that are your drivers (ICH9M). Just follow Fernando's excellent guide right in this forum. You need the driver johnhc pointed out (32-bit Floppy Configuration Utility), which are the same as those in Fernando's guide (under 2a). You need also "INF Update Utility - Zip Format" from johnhc's link, which can be either integrated with nLite or installed afterwards. GL *Edit: afterwards = after windows is installed and fully booted

...to fragment RAM? /me runs away... GL

So the mechanism on the key has three connection points. Come on, you'll figure it out! GL

If you mean this, then it's already included in SP3. No need to do anything. GL

Funny thing, just in yesterday's Patch Tuesday's security bulletin a new file appeared for the first time: xpsp4res.dll (Service Pack 4 Messages). Inside KB923561. At least I see it for the first time. So there is still hope? GL

As always, jaclaz to the rescue! RYU81, study the links carefully and disregard everything about membrane (I think that's not your problem), but the little mechanism (two plastic frames (brackets) that connect and provide tension) - most of it is in the third link. Good luck and please tell us how it went. GL

They need to show Vistaids are better (or just different) than XP so people would not stick with XP and splash hard-earned money. -> So they make changes in the GUI. -> If people revert those changes, they could rightfully say Vistaids are no better than XP(oids) -> So they ban reverting. GL Edit: stick this whereever you like in betwen the sentences above -> During the development of Vista, all the good and really useful changes were dropped, so all that is changed is GUI. -> Edit 2: and another -> Shareholders and management pressurize Windows team to release Windows versions as often as possible in order to maximize income. ->

RYU81, As I said, if no piece was broken off, it should be possible to mount them. Just take some time (a lot of time sometimes) to see which part (piece, arm?) of the key goes where. I.e. the arm should get hooked on that metal thing I suppose (usually slide it beneath). Then there should be a part (in the center) that just pops in under pressure (it should click). Try to feel it - sometimes much pressure is needed, but too much can break it (if other parts didn't fit properly). If needed, approach from several directions. On your first picture I see a key that: 1. wasn't attached right so can't snap in place. (The arm wasn't connected correctly) or 2. is attached right and just a little pressure is all that is needed. On your second picture I see there are possible three hooking points. I'm sure the lower big metal part is one, please if you can post a picture of the key from its lower side. GL

There was something unrelated that broke user accounts. It was in that component's description inside nLite, just look carefully. Sorry I don't have enough time to run Nlite now. GL Edit: about those things you asked (and this is only my opinion; might be wrong): you need Local Security Settings Active directory you don't need Auditing Resource Dlls Certificate Management (maybe) IPSEC Policy Agent

I hope it's not a HP. But seriously, if there are no broken pieces, they should easily pop in. Laptops are a little more difficult, but still can be worked out (with lots of patience and steady hands). GL

You'll have to set a stakeout. Wait for the computer to lie idle for several hours... GL

Because you have a smard card reader? GL