
oao
MemberContent Type
Profiles
Forums
Events
Everything posted by oao
-
Is it possible to slipstream IE7 into xp64 SP2 and its subsequent updates in one nLite session? IOW, will nLite integrate the files in the correct sequence such that the updates are applied after the IE7 itself? If not, can IE7 be applied manually with the /INTEGRATE switch first, then apply the updates and tweaks with nLite? Thanks.
-
I used nLite to eliminate various windows xp x64 features and it looks like somehow I must have eliminated the help system, though I don't recall that I did. in any case, I have no access to help. is there a way to restore it? thanks.
-
Seemingly, but there is a workaround -- I did it before and it works. There is a thread somewhere around here thatdiscusses it. If you search by oao you'll find it. The problem seems to be the writing by my old computer.
-
It integrated the correct Intel Storage Matrix. When I did it without it, there was booting and there was an error: no recognition of the HD. I wrote another CD on my old laptop and I noticed this time that nLite reported a verification failure. I managed to install nLite on another Vista 32 computer and wrote the CD there and verification was successful. The new laptop booted and seemed OK.
-
Hhhhhmmm, I tried to install vLite on the Vista 64 laptop and got the same rejection: file is not compatible with the version of Windows. What is going on?
-
I ran into a problem producing the CD. I have nLited the xp64 CD on my old win2K laptop. The CD is intended for downgrading my new laptop from Vista 64 to XP64. The problem is that my CD drive on the old laptop seems to burn faulty XP64 CDs and my new laptop does not boot from them. I already wasted 3 CD's this way. I thought of producing the CD on my new laptop, but when I try to install nLite of it, Vista 64 says it's not a compatible program. I know there is a vLite version for Vista. Will it install and work on Vista 64 and can I use it to produce the XP64 CD? If not, can it be done on a Vista 32 system? Thanks.
-
I searched for Kurt Aust, but it's not clear to which thread you're referring.
-
True. But some people figured out the solution for the SP's. There should not be that much difference from the hotfixes, so maybe somebody figures them out too.
-
Thanks. Any ideas about 1 and 2, though? I am curious, as I may need that in the future.
-
Back in August I initiated this thread: http://www.msfn.org/board/lofiversion/index.php/t121555.html and I confirmed the following: ========= I copied the the update binaries from the x86 sp2 UPDATE folder to the x64 sp2 UPDATE folder and used the UPDATE /INTEGRATE command to splistream SP2 into XP64 on my win2K system. ========= I now need to slipstream a hotfix into a nLited version of XP64 and I used the same method, but it this time it did not work. When I run the UPDATE /INTEGRATE command I get the following error: Extracted packages cannot be integrated. The /INTEGRATE switch must be used with the original software update package. Questions: 1. Why does this procedure works with SP's, but not with hotfixes? Are they different? 2. Since I cannot recreate the EXE package from the extracted folder, is there any workaround that would allow me to slipstream the extracted folder into xp64? 3. The hotfix is the high definition audio (KB901105). I already nLited all the fixes available for the xp64. Do they include the HDA hotfix and, therefore, I actually don't need to slipstream it anew? ANy help will be appreciated.
-
There is nothing wrong with your explanation. Regarding the SATA gain, yes, I am aware that the gain is negligible, but it's the best I can do. A better option is probably a 7200rpm drive, but they max at 160GB and mine is 250GB. At that size a 7200 would be too expensive anyway. In the case of this computer, Gateway has responded to my question as follows: "The Gateway T-6836 Notebook do not have ATA ports it only has SATA ports available for hard drives, that is why the option SATA/ATA Compatibility Mode is unavailabl on the BIOS setup." Now if that were true, it leaves me no option but to integrate the AHCI driver; and if it lowers performance, then I'll be up the creek without a paddle. But I find it hard to believe that there are no ATA ports. When I look in Device Manager, I see 2 IDE channels and, if I recall correctly, an Ultra-ATA one too. I'll have to check again. Be that as it may, I managed to integrate the SATA drivers into XP 64 via nLite and it should work. I hope that performance will at worst not improve, but if it slows things down I hope I am right to doubt their answer.
-
Back in August I initiated this thread: http://www.msfn.org/board/lofiversion/index.php/t121555.html and I confirmed the following: ========= I copied the the update binaries from the x86 sp2 UPDATE folder to the x64 sp2 UPDATE folder and used the UPDATE /INTEGRATE command to splistream SP2 into XP64 on my win2K system. ========= I now need to slipstream a hotfix into a nLited version of XP64 and I used the same method, but it this time it did not work. When I run the UPDATE /INTEGRATE command I get the following error: Extracted packages cannot be integrated. The /INTEGRATE switch must be used with the original software update package. Questions: 1. Why does this procedure works with SP's, but not with hotfixes? Are they different? 2. Since I cannot recreate the EXE package from the extracted folder, is there any workaround that would allow me to slipstream the extracted folder into xp64? 3. The hotfix is the high definition audio (KB901105). I already nLited all the fixes available for the xp64. Do they include the HDA hotfix and, therefore, I actually don't need to slipstream it anew? ANy help will be appreciated.
-
I purchased a Gateway T-6836 which is an Intel T5750 system. It came with Vista 64. I want to downgrade it to XP 64. I managed to find all the drivers, but ran into a problem with SATA support. There is no BIOS switch for ATA compatibility mode/SATA mode. The installed Vista 64 sees the drive as SATA. However, XP 64 does not and when I try to install it, it does not see the HD. I read all the stuff about SATA driver integration via nLite, but as far as I can tell for that to work there must be a BIOS switch. Do I understand it correctly that without that switch I cannot install XP on this computer at all? Even in ATA mode? I find that hard to believe? Can I go ahead and integrate the SATA drivers and install even without the switch? If indeed the BIOS switch is required, how come Vista does not need it and XP even with the drivers integrated does not work? Some clarifications will be appreciated. Thanks.
-
I found another site and it worked. I still think that the reason for this problem should be found.
-
Well, since I had downloaded the file more than once and got the same result for both versions, it's weird. Anyway, I deactivated both the firewall and the antivirus, I downloaded it again and I got the same result.
-
My windows is up to date. I downloaded and installed HashTab, but have no clue what to do with it. Here are the MD5s: 3C29656A99295E819FA2FE44F814AE42 nlite installer 4ADFA0D4BEB690A9D9BDF34E8CD4F9ED downloaded file CB0EFF52EE9AB11D63D5D6000116E334 nlite self-extracter 4ADFA0D4BEB690A9D9BDF34E8CD4F9ED downloaded file Note that both downloaded files have the same MD5 -- is that correct? What does this mean? Yes, as stated earlier I downloaded from the nLite site.
-
That's the error I get for the installer. For the DL I get: Error Enable your referrer and download from the Download page, if it doesn't work with the left click try the right click - 'Save Link As' If you're not sure how it is blocked then temporary disable Firewalls, Antivirus or some other Privacy tool you might currently have active. Here is a guide on this topic.
-
>NS7 - NetScape 7? Yes. >Do you have a DL accelerator? If so, turn it off and try again. Nope. >Perhaps your security SW is interfering with the DL and/or the install. Did you check the MD5 after DL, if not re-DL and check the MD5. Perhaps. But apparently NS7|Save as is not affected, so I doubt it. I have downloaded both versions twice with same result. >Is nLite or the installer set to run in 16 bit compatibility mode? I did not do anything of the kind. Something puts it in that mode, either itself or something else. >What error do you get on the IE6 DL? Event Type: Information Event Source: Application Popup Event Category: None Event ID: 26 Computer: FABIAN Description: Application popup: 16 bit MS-DOS Subsystem : C:\DOCUME~1\FABIAN~1\MYDOCU~1\DOWNLO~1\NLITE-~1.EXE The NTVDM CPU has encountered an illegal instruction. CS:054a IP:0207 OP:63 6f 6e 74 65 Choose 'Close' to terminate the application.
-
I am using CCleaner on a regular basis, so I doubt that is the reason. Nevertheless, I checked and deleted all temp files. and the error persists for both the installer and zip versions. Also, you did not answer my 2nd question: why I cannot download either version of the program with IE6, but only with NS7 and using the "save as" option.
-
I posted this problem in the 1.4.9.1 thread, but got no reply: With both new versions of the download when I try to install it in Win2000, it pops a DOS cmd window and issues the following: Event Source: Application Popup Event Category: None Event ID: 26 Date: 9/11/2008 Time: 12:19:25 PM Application popup: 16 bit MS-DOS Subsystem : C:\DOCUME~1\FABIAN~1\Desktop\NLITE-~1.EXE The NTVDM CPU has encountered an illegal instruction. CS:054b IP:0207 OP:63 6f 6e 74 65 Choose 'Close' to terminate the application. Also, I am unable to download 1.4.9.1 with even "Save as" via IE6. I can only do it with NS7. Pls advise.
-
With both new versions of the download when I try to install it in Win2000, it pops a DOS cmd window and issues the following: Event Source: Application Popup Event Category: None Event ID: 26 Date: 9/11/2008 Time: 12:19:25 PM Application popup: 16 bit MS-DOS Subsystem : C:\DOCUME~1\FABIAN~1\Desktop\NLITE-~1.EXE The NTVDM CPU has encountered an illegal instruction. CS:054b IP:0207 OP:63 6f 6e 74 65 Choose 'Close' to terminate the application. Also, I am unable to download with even "Save as" via IE6. I can only do it in NS7.
-
Actually, I was wrong. ZA has a configuration feature which allows specifying the printer's IP. So now I can print.