Oleg_II
Content Type
Profiles
Forums
Events
Posts posted by Oleg_II
-
-
Try to use OfflineSysPrep to inject drivers.
Or look for PEIMG.EXE - usage is described in the same topic.
Or inject your driver manually - there is one example in the same topic too (look for a post by Ilko with regestry settings).
There is also one more tool I mentioned there but nobody reported how it works.
0 -
I use jdoe's CAB Tool for it (in fact usual install will install these shortcuts to Send To menu itself, but I use a bit modified old version and make shortcuts myself). Very good and very handy tool though
Find it here.0 -
Interesting solution. Thanks!Use a "dummy" .exe:http://www.hydrous.net/weblog/2007/06/23/d...windows-exporer
jaclaz
0 -
tain
No. I'm doing everything manually and change a lot of files from distro (including editing INF files and hex-editing binary files) and add some things from other Windows versions. Don't think it can be release as a fileset right now (and when it probably can be generalized nobody will be interested in XP
A hint: imagex.exe from VistaPE that compresses files works in XP
Just move some files from SYSTEM32 to SYSTEM folder (changing pathes for some of them in regestry of course), make WIM file from SYSTEM folder content and mount it during Windows startup - you will save a lot of space on your system partition 0 -
Chinese isn't showing either if you don't choose it during installation (or in WINNT.SIF). Maybe you need to choose "Install files for complex script..." first? If it doesn't work then you need to reinstall with Turkish language in options (during installation or through WINNT.SIF). Make sure you have LANG folder in your distro.
There is the other way but it is a bit complicated and time consumming - all language settings are in INTL.INF. Learn it, especially in Turkish language section. I've made installation file for Chinese that installs it with one input method without using Regional and Language Options applet.
0 -
I use Wireless Network Ignition. Very simple and effective. It doesn't rely on Windows wireless component, it has its own protocol. So if you like researching you can even take default wifi protocol and a few files out of your disk too
0 -
Application Layer Gateway (if Windows Firewall is involved)
Had this problem with wifi - everything seemed to be fine but can't see anything in network list and as a result can't connect.
0 -
Preparation step that may not be needed but it's better to make it anyway just in case:
1. Double click on My Computer > Tools > Folder Options > View and choose "Show hidden files and folders" > Apply > OK.
2. Go to your Windows directory and find INF folder. Open it and find HAL.PNF. Delete HAL.PNF (NOT HAL.INF!!!).
Steps to change the HAL:
1. Right click on My Computer and choos Properties.
2. Choose Hardware tab and press Device Manager.
3. Find Computer and press "+".
4. You probably have "Standard Computer" there. Click on it with right button of your mouse and choose "Update Driver...".
5. Tick on "Install from a list of specific location (Advanced)" > Next.
6. Tick "Don't search. I will choose the driver to install." > Next.
7. That one you choose yourself - it depends on your hardware. ON modern computers it should be ACPI Uniprocessor or ACPI Multiprocessor. > Next. That will install new HAL and require to reboot. After rebooting all hardware will be re-detected again.
If you have this behaviour in virtual machine you probably won't change the HAL - read documentation of your virtual machine first to find out if it supports ACPI functions.
0 -
I don't use hot keys but Grub4DOS menu ;0
As for recovery partition I prefer hidden system folder and give system rights to backup images so that a user can't delete them even he finds this hidden folder
0 -
cluberti
This seems working:
[NetServices]MS_Server=params.MS_PSched
At least I have only 3 items left in Connection Properties:
- Client for Microsoft Networks
- File and Printing Sharing for Microsoft Networks
- Internet Protocol (TCP/IP)
Now the question is how to get rid of them (maybe except TCP/IP protocol but it can be installed later too anyway).
0 -
cluberti
Thanks for your advices
I'll try them right away.But as for
I don't quite understand... I contrary don't want to install default components, I'd like to install only TCP/IP protocol or even don't install anything default (TCP/IP protocol, Client for MS Networks, File and Print Sharing and QoS Packet Scheduler).Also, considering that your network section is just providing defaults, try just using the following:Sorry for ignorance but I don't also get if this
helps me to get rid of QoS Packet Scheduler? Cause I don't need it.[NetServices]MS_Server=params.MS_PSched
I specified "InstallDefaultComponents=no" and only need TCP/IP protocol. It doesn't possible at all?
PS I install from the hard disk (from previously created share).
0 -
Just found: I miss this section[identification]
JoinWorkgroup=WORKGROUP
Could it be the problem?
Nope...
Added Identification section and deleted TCP/IP info (only InstallDefaultComponents=No is left, decided not to install at all) - no go, all default protocols-clients-services art still there
0 -
Just found: I miss this section
[identification]JoinWorkgroup=WORKGROUP
Could it be the problem?
0 -
Old thread
Here's my WINNT.SIF:
[Data]
AutomaticUpdates="No"
Autopartition=1
MsDosInitiated=1
UnattendedInstall="Yes"
[Unattended]
UnattendMode=FullUnattended
UnattendSwitch="Yes"
OemPreinstall="Yes"
OemSkipEula="Yes"
ProgramFilesDir="\Appz"
CommonProgramFilesDir="\Appz\Common"
ComputerType="Standard PC", Retail
FileSystem=LeaveAlone
WaitForReboot=No
DriverSigningPolicy = Ignore
NonDriverSigningPolicy=Ignore
Hibernation = No
OemPnPDriversPath="\Temp\drivers"
[GuiUnattended]
AdminPassword=*
AutoLogon=Yes
OEMSkipRegional=1
OEMSkipWelcome=1
ProfilesDir="%SYSTEMDRIVE%\Profiles"
TimeZone=210
[UserData]
ComputerName=***
FullName="***"
OrgName="***"
ProductId="***"
ProductKey="***"
[Shell]
DefaultThemesOff="Yes"
DefaultStartPanelOff="Yes"
[b][Networking]
InstallDefaultComponents=No
[NetAdapters]
Adapter1=params.Adapter1
[params.Adapter1]
INFID=*
[NetProtocols]
MS_TCPIP=params.MS_TCPIP
[params.MS_TCPIP]
DNS=Yes
UseDomainNameDevolution=No
EnableLMHosts=Yes
AdapterSections=params.MS_TCPIP.Adapter1
[params.MS_TCPIP.Adapter1]
SpecificTo=Adapter1
DHCP=Yes
WINS=No
NetBIOSOptions=0[/b]
[b][NetOptionalComponents]
Beacon=0[/b]
[WindowsFirewall]
Profiles = WindowsFirewall.TurnOffFirewall
[WindowsFirewall.TurnOffFirewall]
Mode = 0
[Components]
AccessOpt = Off
Appsrv_console = Off
Aspnet = Off
BitsServerExtensionsISAPI = Off
BitsServerExtensionsManager = Off
Calc = On
Certsrv = Off
Certsrv_client = Off
Certsrv_server = Off
Charmap = Off
Chat = Off
Clipbook = Off
Cluster = Off
Complusnetwork = Off
Deskpaper = Off
Dialer = Off
Dtcnetwork = Off
Fax = Off
Fp_extensions = Off
Fp_vdir_deploy = Off
Freecell = Off
Hearts = Off
Hypertrm = Off
IEAccess = Off
IEHardenAdmin = Off
IEHardenUser = Off
Iis_asp = Off
Iis_common = Off
Iis_ftp = Off
Iis_inetmgr = Off
Iis_internetdataconnector = Off
Iis_nntp = Off
Iis_serversideincludes = Off
Iis_smtp = Off
Iis_webdav = Off
Iis_www = Off
Indexsrv_system = Off
Inetprint = Off
Licenseserver = Off
Media_clips = Off
Media_utopia = Off
Minesweeper = Off
Mousepoint = Off
Msmq_ADIntegrated = Off
Msmq_Core = Off
Msmq_HTTPSupport = Off
Msmq_LocalStorage = Off
Msmq_MQDSService = Off
Msmq_RoutingSupport = Off
Msmq_TriggersService = Off
Msnexplr = Off
Mswordpad = Off
Netcis = Off
[b]Netoc = On[/b]
Objectpkg = Off
OEAccess = Off
Paint = Off
Pinball = Off
Pop3Admin = Off
Pop3Service = Off
Pop3Srv = Off
Rec = Off
Reminst = Off
Rootautoupdate = Off
Rstorage = Off
Sakit_web = Off
Solitaire = Off
Spider = Off
Templates = Off
TerminalServer = Off
TSWebClient = Off
Vol = On
WbemCrrl = Off
WbemFwrd = Off
WbemMSI = Off
WMAccess = Off
WMPOCM = Off
Wms = Off
Wms_admin_asp = Off
Wms_admin_mmc = Off
Wms_isapi = Off
Wms_server = Off
Zonegames = OffEverything should be working but... Client for MS Networks, File and Print Sharing and QoS Packet Scheduler are still there after installation
I'd even get rid of TCP/IP protocol (temporary of course, only during setup
if it can help not installing other things.0 -
When it ask you for CD you should provide installation CD or browse for i386 folder on you hard disks.
Language support can be added manually but it takes time and some efforts to study INTL.INF and gather some files needed from installation media.
0 -
Appz, Profiles, WINDOWS here
Like it cause it always works with BAT and CMD files (some of them have some problems with pathes like "Program Files" or I just can't make it right Found one Chinese IM program QQ Messanger that re-creates "Program Files" directory (installs some part of itself there), other programs work without problem.
And there is something like "C:\Program Files\Common Files\Stat\F89E7781.stt" (didn't found what creats it
0 -
There is a great tool from one of the board members - jdoe. It's here.
I use its previous version with batch files
It adds two lines to Send To context menu: "CAB expand" and "CAB make". And it makes File.ex_ from separate files and Folder.cab files from folders 0 -
Just remembered one more universal program - Boingo (look in download section).
It's free but not very light
0 -
This is my example of creating two shortcuts "Expand" and "Make" for two CMD files in SendTo menu:
[version]
signature="$Windows NT$"
ClassGUID={00000000-0000-0000-0000-000000000000}
LayoutFile=layout.inf
[DefaultInstall]
CopyFiles = Files
UpdateInis = Appz.links
[DestinationDirs]
Files = 16422,tools\cmd
[Files]
cabarc.exe
expand.cmd
makecab.cmd
modifyPE.exe
[Appz.links]
setup.ini, progman.groups,, "group1=""%16393%"""
setup.ini, group1,, """CAB Expand"",""""""%16422%\tools\cmd\expand.cmd"""""",,,,""%16422%\tools\cmd"",""expand.cmd"""
setup.ini, group1,, """CAB Make"",""""""%16422%\tools\cmd\makecab.cmd"""""",,,,""%16422%\tools\cmd"",""makecab.cmd"""0 -
Not exectly the answer to you question but I found a good program - Wireless Network Ignition from SingleClick Systems. It has it's own wireless protocol driver and is a universal front end for ANY wireless card. The interface is simple and clear. The program is very small comparing with most todays heavy loaded monsters. Works perfect on Windows 2000
0 -
For XP and Win2k3 you may prepare one universal image with all needed programs installed and deploy it on any computer (different HAL types and all kind of hard disk controllers) with OfflineSysPrep.
You may also add all kind of other drivers to the system before creating image. For example, place them all in on folder Drivers on C:
All registrations can be done during mini-setup and after it (for programs).
0 -
Try this. Free and effective
0 -
Turn on (uncheck the box) "Hide protected operating system files (Recommended)" in Control Panel > Folder Options > View and you will see the file on your system partition
0 -
There are two main difficulties in creating such image: mass storage drivers and system HAL (Hardware Abstraction Layer). If any of these two is not right you'll get BSOD.
All other additions (other drivers, hotfixes, tweaks, etc.) can be applied after system boots succesfully on a new computer.
There is a tool OfflineSysPrep for PE environment that can help solving HAL problem and the creator is working on mass storage drivers issue.
Mass storage drivers may be added manuall to the regestry of a system before clonning. A very good description of this method is done by ilko here. Only SYS files plased in system32\drivers folder and a couple of regestry entries will do the thing for the first succesfull boot (after that install regular drivers).
I found on Chinese Internet (described by Climbing) that ntldr from Longhorn (beta) is capable to detect and install during the boot the right hal (adding /DETECTHAL switch to boot.ini and placing a very simple dtecthal.inf file in INF folder).
0
Find it 
Just move some files from SYSTEM32 to SYSTEM folder (changing pathes for some of them in regestry of course), make WIM file from SYSTEM folder content and mount it during Windows startup - you will save a lot of space on your system partition 
Windows Setup Classic Style
in nLite
Posted
Ok, let me continue guessing
For classic setup style you need to delete WINNTBBU.DLL and WINNTBBA.DLL files from i386 folder.
What you see in the background of classic setup is inside of SETUP_W.BM_ file - change it to your BMP file and you'll see what you like during setup.
PS You can edit WINNTBBU.DLL (and WINNTBBA.DLL depending of installation media) file to have your own screens in usual XP setup rutine