Speeddymon
Content Type
Profiles
Forums
Events
Posts posted by Speeddymon
-
-
Curious if the beta x64 drivers for the HP DeskJet 970cxi series printers is supported. When installing within Windows via the Device Mgr, the inf opens up an executable installer.
0 -
EDIT: This reply is pointless. The OP just realized that the last post in this topic before his was in 2001, how and why it showed up on his computer today is still a mystery. Anyways, MOVE ALONG.
0 -
Burn issue
in nLite
That much I know, I was just reporting the bug. The Direct Burn option does work if you don't make an image first, not sure about after you make image and then burn image, let alone just burn image. Either way, just figured I'd report it to nuhi
0 -
Burn issue
in nLite
Do nLite'ing as normal, then make an ISO image, then before hitting next, change the Mode to Direct Burn, and hit the button to start the process to burn. It goes through the MB's really fast, then says write successful, but never even messes with the CD drive. If you check the Verify checkbox, it says verification failed. If you change it to burn image, however, it will ask which image to burn, and then properly burns it.
This is in v1.4.1, but maybe also in 1.4.5 beta
0 -
Hi all.
I got these weird error when integrating WMP11 with nLite 1.4.1 and WMP11 Slipstreamer 0.96.
some help, please?
thanks
I can only guess that either the cd was corrupted while copying to your hard drive, or perhaps you ran out of space while the modification was going on, or maybe the versions of media player and ie7 that you are trying to integrate do not correspond to the localized version of windows. Last guess would be that this cd was modified once already and you are trying to modify it again, meaning you need to start from a clean source, such as the original cd you purchased. All just guesses though.
0 -
Yeah I guess I can see that. If you made the first one that added 100 hotfixes and then did another one later (using that modified XP source) that say added 5 more hotfixes, it would essentially be overwriting those first 100 hotfixes all over again (if you used the saved profile).
It would be cool if it was smart enough to know which ones had been done already and only added to that.
Also remember that the last session files only store what was done in the last session, so if you removed some components, and then modified the modified CD, those components would be already removed, and therefore the last session would not record that it removed them, so if you later needed to rebuild from scratch, you would have to go back and manually enter those items for removal.
0 -
Here is my situation. I have multiple computers through the entire house that all require different drivers.
1. Can I integrate all the drivers for all computers on 1 xp installation cd?
2. If I can, will they be properly installed on the right PCs?
I hope I was clear enough with my questions, if not please respond.
Thanks in advance!
You can, and should not have any problems, as the hardware detection phase of the install will determine which drivers to use. If you are really paranoid you could always make a backup of the current install on one machine, make your cd with all of the drivers for all of the machines, format, install, and if it craps out, restore the backup.
0 -
Only to add custom drivers and/or remove components or included drivers you can reuse the resulting files.
For other changes, it is better to use original files and (if needed) last_session.ini as template.
I agree. Personally, I set nlite to save the last session on the CD. Then when I need to make changes, I take my original XP CD, copy it to the hard drive, and then load up nlite, select the clean source for modifying, import the last session from the modified CD, and make all of the necessary modifications to that, and burn a new CD (after testing in a virtual machine).
0 -
I see in the guide it recommends to use a souce XP without any service packs. Is this really necessary?
No. I think the point is that it is better to integrate SP2 to the original XP than on top of SP1. I hope you see what I mean.
I'm not even sure there would be any difference.
Simply put, if you have an XP CD with no service pack, integrate SP2, if you have an XP CD with SP1, integrate SP2, if you have an XP CD with SP2, then do nothing. If you have an XP CD with no service pack or with SP1 that you have slipstreamed SP2 onto, then proceed as if you had an XP CD with SP2. Slipstreaming is the process by which you take your original XP CD and make it so it is an XP SP2 CD. When you buy current copies of XP from a store, those CD's are just the original XP that microsoft did the slipstream process for you.
0 -
Well, if you read the thread before posting, you probably expect the same answer: this has nothing to do with nLite.
not to mention that you have hijacked this thread. It is best if you start a new thread.
0 -
You obviously didn't perform any searching yourself, as there are plenty of topics regarding Microsoft .NET Framework on this forum which would have answered all your questions. I'm in a good mood however and I'll give you a short answer: the .NET folder in the root of your installation disc has nothing to do with the installation process; it doesn't get installed, it's not used by the installation process at all, you can compare it to the SUPPORT folder for example, it's safe to delete. Version 2.0 SP1 does not include version 1.1 SP1. Version 3.0 SP1 contains version 2.0 SP1. Version 3.5 contains version 3.0 SP1 and 2.0 SP1. If you want version 1.1 SP1 installed you'll need to install it seperately therefore. The version on your installation disc however is most likely an old version, so simply download the latest release of version 1 from the Microsoft web site. If you want the latest release of version 2, either install the latest release of version 2 as downloaded from the Microsoft web site or install the latest release of version 3 or 3.5, also as downloaded from the Microsoft web site. But you could have found all this easily yourself, so next time please search.
Also, it should be mentioned that .NET v2.0 is 100% backward compatible with 1.1 and 1.0.. Meaning that even though 1.1 is listed as something you need in WU/MU, you don't actually need it. As a test of this I (a while back) looked around for any programs that said they required 1.0 or 1.1, but not 2.0, did a clean install from an original cd, installed 2.0, and then installed those programs. Some complained that 1.1 or 1.0 wasn't installed, but let me continue anyways. I then was able to run those programs with no problems. That isn't to say that there aren't some programs that will REQUIRE you to have 1.0 or 1.1 installed, but they are few and far between.
0 -
Siginet's Integrator v1.5 is supposedly capable of direct integrating the RogueSpear switchless silent installers. I haven't checked into this because I prefer to use nlite, however, if this is the case, does nlite support the same, or will it in the future? RogueSpear dropped support of nlite addons because of this. I am trying to minimize the amount of time spent installing programs after windows is installed, and since all of his addons now are svcpack.inf or runonceex addons, it makes that a bit difficult.
Edit: I just tested with RogueSpear's Adobe Reader installer and J2SE6.0u4 installer, it tries to install them to my live machine, so apparently nlite doesn't support this method. I'd like to request that it be added for nlite 1.5
0 -
sorry i'm late
this kind of settings generally stored in windows registry, open regedit and searh for %PROGRAMFILES%. It may be helpful.Well if that is the case, do you happen to know if that is stored in the default registry hives that get populated during Windows install?
0 -
Just curious, where is the value of %PROGRAMFILES% stored?
I think it is stored somewhere because nlite can change it, so that you can have your Program Files directory on a different drive.
Basically, what I am trying to do is have windows install with program files set to the default location, and then after install, change the value of %PROGRAMFILES% so that any new installs go to a separate drive, so that if I need to wipe out the windows install, I can just format C: and not lose any other installed programs. Currently I achieve installing to a separate drive by changing C: to D: in every new install, but a lot of times I forget, and have to go back and uninstall and reinstall.
0 -
I have several new computers for some people the past few days and as part of the process I always create them a 'recovery' cd that will contain all the latest Windows updates (at the point of creation) as well as all the drivers integrated so that they can be up and running without my help if they ever need to reinstall Windows (there is more to my recovery cds to make it more user friendly, but no need to detail that)
One of my builds is using Windows XP x64 edition.
Everything works out just fine. Integrated service pack 2 (not with nLite though, as other topics have pointed out the same problem I was having, had to do it manually through cmd) integrated the raid drivers, chipset driver, audio driver, hd audio bus driver, lan driver, and video driver.
However, the video driver (158.22_forceware_winxp64_english_whql for GeForce 8800) is integrated, but does not install during windows setup. Once Windows has been installed I can bring up device manager, manually search for a driver, the driver I integrated comes up as a choice, and i can install it without issue. But why isn't it installing during windows setup?
When I manually install the driver, the window where I select which driver I want tells me that that driver is not signed, but doesn't give any actual warning or error prompts.
The driver is suppose to be signed, as its declared WHQL. The nv4_disp.cat is present in the driver.cab file.
My winnt.sif file contains the lines:
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore
Any ideas?
driver.cab as in the driver.cab thats in i386? might want to see if putting it in i386\svcpack will fix it.. just a stab in the dark tho really. personally I have always just made a silent install with the nvidia installer (extract the big exe, then run setup.exe -r in a running windows, copy the setup.iss into the installer folder, and then copy that folder to CD, using setup.exe -s as the install command at runonce), as I ran into problems with the geforce 7xxx series not installing when integrated, but that is another issue, not related to nlite.
0 -
Please add the following registry tweak:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\*\Shell\Makecab\Command]
@="makecab.exe \"%1\""
It makes it so when you right click on a file, you can compress it with makecab.. Easier than having to open a command prompt and then switch to the directory and then run makecab
0 -
Yes, even delete the \minint directory. All we really obtained from this build is NTLDR, this is where someone smarter than I could simplify the process and save some time if they could help obtain a proper NTLDR another way.
[-snip-]
Steps 7 and 8 are another place where a proper NTLDR file that does not point to \minint would help create a more correct method.
[-snip-]
Hope this works for you, please give it a shot. Any suggestions and improvements are more than welcome, I could really use help with the NTLDR issue so that the time-consuming PE build would not be needed. I'll be glad to answer any questions I can, but like I said, this was a blind squirrel/acorn "hit and miss" for me!
Ok, I figured out a MUCH simpler method for getting NTLDR, and for getting one that doesn't point to \minint assuming you have the prereqs.
NOTE: I havent finished my testing yet as I am remaking my installdir right now with the new patches, so if there is something that comes up later on in setup due to this then shoot me a PM so I know.
Prereqs:
- WinImage (http://www.winimage.com) (the shareware version works fine for this)
- Bart's mkbt
- A working copy of XP
- The 6 boot floppy images from the Original XP Install CD
1) Open WinImage
2) Click the Disk menu, and select Edit Master Boot Record Properties
3) Check the checkbox Include non removable Hard Disks
4) Select the Hard Disk that XP is installed on (Usually Disk 1), and click Save
5) Give the bootsector a name and save somewhere you can find it (I save it to the mkbt directory with the name bootsect.bin)
6) Open a command prompt and switch to the directory mkbt is in
7) Run mkbt as follows:
mkbt -x bootsect.bin j:
NOTE: Make sure you insert the path to the bootsector file if it is not in the mkbt folder. Make sure you change bootsect.bin to the proper file name. Make sure you change j: to the proper drive letter for your USB drive, else you will overwrite the wrong bootsector and MAY not be able to boot back into XP
8) Within WinImage, hit File -> Open and select the first XP Setup Disk image.
9) Copy all of the files there to the root of your USB Drive
10) Open your USB Drive in explorer, and rename SETUPLDR.BIN to NTLDR, and move BIOSINFO.INF to a new folder named $WIN_NT$.~BT
11) Open each of the other Disk Images, and copy all of the files in them to the $WIN_NT$.~BT folder in the root of your USB Drive.
The rest I have not finished testing, I will edit this post once I figure out where to put the rest of the CD files.
0 -
Could you attach your "Last Session.ini" file, as well as your WINNT.SIF. You may have to compress to get them to attach.
0 -
-
I did try putting it into the driver section but it didnt work. It was in windows as a driver but wouldnt work when installing. I read somewhere that it has to be a .txt file in the OEM directory but I couldnt find enough info on it.
If you download the entire driver from the promise website, and extract it to a folder on your desktop, nlite should be able to read the inf and the txtsetup.oem file, and will then give you the option to integrate it as a textmode driver or a pnp driver. Pick txtmode and then do the rest of the nlite process as you normally would.
0 -
Here you go, this is the one from my latest try.
Also, please attach your txtsetup.sif from the original DVD. I found the problem and need to see how the original is done so I can show you how to fix it.
The original file is 466kb, which is over the max allowed to upload to this site. Any other way I can upload it, or can I email it to you?
Try compressing it with any zip program.
0 -
alright might as well tell you what i use onthe forum
i use PROGRAMS OF USE! UNDER THIS LINE ________-
AIM
xfire
itunes
yahooo anti spy
zonealarm
nbalive 07
guild wars *IF GAMES COUNT*
ventrillo
mirc
nero 7
windwos media player
quicktime player *for itunes*
power iso
mozzilla firefox
OTHER COMPUTER GAMES LIKE CARDS AND THAT JUNK I HATE!
Tell me if u can build an xp off this removing anything else these are all the programs i use
I'm sure someone can manage something. Pretty much everything that is not red in color on the component removal page is ok to remove. It really is not hard to use nlite. Just dont remove services, or hardware support.
0 -
there is a cursorb.in_
here is the ini file
Well its not so much the entries file I was worried about, but open up txtsetup.sif in notepad, it's in your i386 dir (on the cd that gave you the error). Do a find for cursorb.in
If it comes back with an entry, look in the i386 dir for cursorb.in_. If it is not there then the multitheme pack is causing the problem, and you should contact siginet about it.
0 -
im not really sure what to take out proably WMP stupid games and trial things. unnessacry junk
There is a lot you can take out. The easiest way to figure out what to remove is to ask someone what is "safe" to remove and then list what all you use your computer for and some of the applications you use every day.
0
this kind of settings generally stored in windows registry, open regedit and searh for %PROGRAMFILES%. It may be helpful.
[RELEASE] Boooggy's WMP 11 direct integration solution
in Application Add-Ons
Posted
It appears that the latest version of WMP11 Slipstreamer doesn't support some of the same flags that it used to. When adding MP11 Slipstreamer to nlite, and then starting the process, I get an error about usage, and then when clicking OK, the command line argument list appears. This is with 1.4.1. I could just be using it wrong, in which case, it would be great to know where the instructions are for how to properly use the slipstreamer with nlite.