What has sysprep to do with boot.ini parameters?
For loading the correct hal on startup. Isn't that why you stated "or the boot.ini"?? Using offline sysprep?? Did you forget you past posting ?
Posted 20 September 2008 - 11:06 PM
What has sysprep to do with boot.ini parameters?
Posted 21 September 2008 - 12:01 AM
Posted 21 September 2008 - 08:31 AM
Posted 14 November 2008 - 08:52 AM
Posted 14 November 2008 - 09:33 AM
Posted 14 November 2008 - 05:31 PM
Posted 14 November 2008 - 07:12 PM
Ok all...
Let 'er rip.
http://pantherxp.net
and btw--
--nice to be back.
Posted 15 November 2008 - 09:58 PM
Posted 16 November 2008 - 01:56 PM
:: Get last CD Drive letter FOR /F %%? IN ('MOUNTVOL ^|FIND ":\" ^|FIND /I /V "A:\"') DO (FSUTIL FSINFO DRIVETYPE %%? |FIND /I "CD-ROM" >NUL 2>&1 &&SET CDROM=%%?)
Posted 23 November 2008 - 11:52 PM
[*]1/ What are the other changes applied to winpe.wim in addition to drivers added for VMware support?
[*]2/ Replacing modified TXTSETUP.SIF in your kit with our own untouched TXTSETUP.SIF from source CD would break something or have you just removed unwanted stuff (Tour, etc...) you don't want to copy during install?
[*]3/ Would you like to describe what presetup.exe tool does (in addition to displaying a splash screen of current configuration phase before launching real mini-setup.exe ?
[/list]
A lot of questions but be sure we appreciate your hard work which will let us reduce deployment time of new boxes.
Posted 24 November 2008 - 12:18 AM
Hi Thuun,PM me if it gets to be too much.
Posted 24 November 2008 - 01:36 AM
Posted 03 December 2008 - 06:10 AM
Posted 03 December 2008 - 06:45 AM
... issue with sp2 source
But I already have a prepared wim image
Posted 05 December 2008 - 03:05 PM
2. Replacing the winpe.wim TXTSETUP.SIF may leave you with an unbootable image as the file contains entries required for the bootable WIM file system. Isolating the driver components would be the first order of business for you. PM me if it gets to be too much.
Posted 05 December 2008 - 07:46 PM
Thank you, so I corrected.The "Panther" XP/03 deploy kit uses the beta 1 wim format api.
Posted 07 December 2008 - 04:41 PM
PEIMG failed to complete the operation with status code 0x80360051Accordingly winpe.wim, created after the integration with errors - does not work.
Posted 07 December 2008 - 09:48 PM
Posted 11 December 2008 - 06:07 AM
Posted 08 January 2009 - 01:48 AM
Posted 31 January 2009 - 03:53 PM
hi guys the work of panther xp team is great...i try it, but i get some errors when i try to mount, install.wim of the panther studio, and i fixed this, now, when the mini setup of xp begin,
it show this error..."error to load fldrclnr.dll". when i press ok. the setup continue and finihs correctly the installation and i see the desktop.
see the Attached file
And sorry for my bad english i am mexican and i dont speak english.
thanks in advance.
rundll32.exe %SystemRoot%\system32\fldrclnr.dll, Wizard_RunDLLyou will get a message like yours.
expand -r <CDROM>\I386\fldrclnr.dl_ %SystemRoot%\system32
rundll32.exe %SystemRoot%\system32\fldrclnr.dll, Wizard_RunDLL
Posted 31 January 2009 - 04:12 PM
these are the cpu detect and cmdlines scripts...
-------------------------
CPU-Z version 1.49
-------------------------
Processors Map
------------------------------------------------------------------------------------
Number of processors 1
Number of threads 2
Processor 0
-- Core 0
-- Thread 0
-- Thread 1
Processors Information
------------------------------------------------------------------------------------
Processor 1 (ID = 0)
Number of cores 1 (max 1)
Number of threads 2 (max 2)
Name Intel Pentium 4 630
Codename Prescott
Specification Intel® Pentium® 4 CPU 3.00GHz
Package Socket 775 LGA (platform ID = 4h)
CPUID F.4.3
Extended CPUID F.4
Core Stepping N0
Technology 90 nm
Core Speed 2793.4 MHz (14.0 x 199.5 MHz)
Rated Bus speed 798.1 MHz
Stock frequency 3000 MHz
Instructions sets MMX, SSE, SSE2, SSE3, EM64T
L1 Data cache 16 KBytes, 8-way set associative, 64-byte line size
Trace cache 12 Kuops, 8-way set associative
L2 cache 2048 KBytes, 8-way set associative, 64-byte line size
FID/VID Control yes
FID range 14.0x - 15.0x
VID range 1.116 V - 1.420 V
Features XD
Hyper-threading is the ability of a single processor to perform as if it were two distinct processors.
:: :: Detect CPU type and update HAL if multi processor :: @start /wait CrystalCPUID.exe /s /e @if %errorlevel% neq 0 ver >nul @findstr /c:"Physical Core : 1" temp.txt @if %errorlevel% equ 0 ( echo presetup.exe -splash_uni ) else if %errorlevel% equ 1 ( @inimod.exe /F:"%systemdrive%\sysprep\sysprep.inf" /AC /S:"Unattended" /K:"UpdateHAL" /V:"ACPIAPIC_MP,%WINDIR%\Inf\Hal.inf" echo presetup.exe -splash_multi )
Physical Core : 1
presetup -splash_uni
Posted 22 February 2009 - 03:43 PM
0 members, 1 guests, 0 anonymous users