This post has been edited by jingder: 07 October 2005 - 08:22 PM
SOLVED: drivers from CD possible even without winnt.sif!
#422
Posted 25 October 2005 - 10:52 PM
I am missing somthing:
Where does this line go:
%CDDRIVE%\OEM\bin\SetDevicePath.exe %CDDRIVE%\OEM\drivers?
Could someone please enlighten me? I read through it and followed all the steps, and couldn't find it anywhere!
John
#423
Posted 26 October 2005 - 05:42 AM
RBCC, on Oct 26 2005, 05:52 AM, said:
I am missing somthing:
Where does this line go:
%CDDRIVE%\OEM\bin\SetDevicePath.exe %CDDRIVE%\OEM\drivers?
Could someone please enlighten me? I read through it and followed all the steps, and couldn't find it anywhere!
John
Try this article.
#424
Posted 19 December 2005 - 09:56 AM
has anybody an idea to install the monitor driver silent?
My problem is, that sometimes a window appear which ask me to install the monitor driver.
This window appears in the t-39 (driverinstallation).
Thx.
Björn
#425
Posted 24 December 2005 - 04:57 PM
I:\xpcd\$OEM$\$1\drivers
|
|---00-av
|
|---01-chip
what do I put here?
%CDDRIVE%\OEM\bin\SetDevicePath.exe %SystemDrive%\drivers
John
#426
Posted 28 December 2005 - 10:36 PM
#427
Posted 28 December 2005 - 11:25 PM
RBCC, on Dec 24 2005, 04:57 PM, said:
I:\xpcd\$OEM$\$1\drivers
|
|---00-av
|
|---01-chip
what do I put here?
%CDDRIVE%\OEM\bin\SetDevicePath.exe %SystemDrive%\drivers
John
Why do you need this method if you copy the drivers directory to your hard-drive?
And that line you posted is inside the presetup.cmd is it? you don't really know this method.
#428
Posted 07 January 2006 - 11:30 AM
I have a problem during an installation of a hp d230m
During the hardware setup in gui setup a blue screen appears with an error message, that there is a problem with the portcls.sys.
There is no way to install this computer with the driver pack.
I used the sound, graphics, chipset and lan packages in the newest version.
I hope, that anybody can help me.
Thx a lot
Björn
I removed the sound pack and the blue screen does not appear. But I don't want to solve the problem in this way.
This post has been edited by Björn_2: 07 January 2006 - 11:57 AM
#429
Posted 09 January 2006 - 04:15 PM
This post has been edited by 5eraph: 09 January 2006 - 04:17 PM
#430
Posted 20 January 2006 - 07:14 AM
5eraph, on Jan 9 2006, 11:15 PM, said:
I used DriverPacks_BASE v6.01 but the problem exists anymore. I tried to integrate the KB888111 Hotfix myself with the KB888111.exe /integrate: method and the integrate-method of base 6.01. But nothing work.
I think, that there is a wrong driver windows tried to install. Is it possible to get out which driver will be installed during T-35?
Thx
Björn
#431
Posted 02 February 2006 - 09:49 AM
#432
Posted 18 March 2006 - 03:52 AM
DisabledTrucker, on Feb 2 2006, 04:49 PM, said:
It's been converted to Windows x64 Edition months ago. There's even a tutorial.
#433
Posted 13 April 2006 - 11:02 PM
Actually i am using Pyrons method(presetup.cmd, updated setup.ex files and all stuffs) as it helps to inculde custom drivers and all.
Everything works fine till i found my svcpack.inf is not working.I was thinking like others that there was some problem with pyrons method.
Then as evilvoice suggested(not to me,but in the forum) i tried running setup form my orginal setup.ex removing pyrons setup.ex,but still couldn't have svcpak.inf running. So i understood there wasnt and it isn't because of any problem with pyrons method but there is some other basic problem that needs to be sorted out first
Then i went down to check everything from the scratch.That search ended in my svcpack.inf file where in the version part it was given as :
;Windows XP [Version] Signature=" NT$" MajorVersion=5 MinorVersion=1 BuildNumber=2600
which is incorrect and it was supposed to be like this for XP
[Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=1 BuildNumber=2600
Actually i have done all my initial work on unattended Xp from Alanoll unattended windows guide. Its a nice guide and i should thank allonol for his wonderful compilation work.
But this small error is there which needs to be corrected.
Allanol if you happen to read this hope you will correct that mistake.
Hope this experiece of mine will help someone else in their cause.
NB: I havent gone full throught this forum and if anyone has pointed out this earlier please ignore this.
This post has been edited by Shijilal: 13 April 2006 - 11:04 PM
#434 Guest_dpbarry_*
Posted 28 April 2006 - 04:22 AM
I've been trying to follow through the installation of the Bashrat's driverpacks and seem to have been successful in running the 'Run_me.cmd' file. I'm interested in integrating the whole set of driverpacks.
I followed through the steps required and I now have with a 'WinXPSp2_integrated' folder which is sitting a 722MB.
This is the bit I am stuck at.
How do I fit this on a CD? (or do I?)
I can use the RVM_Integrator to create an ISO which takes it to 747MB which obviously won't fit on a CD so do I put it on a DVD or is there something I missed in the initial setup of the integration.
Confused.
Declan
#435
Posted 29 April 2006 - 07:07 PM
http://www.ryanvm.ne...opic.php?t=2107
#436
Posted 13 June 2006 - 03:55 AM
but
anyone knows why when I use the Driverpacks and add them to my RIS installation it does not do the cmdlines.txt anymore. Therefore also does not run the RunOnceEx.cmd.
Does this has to do with the setup.ex_ and the setuporg.exe?
#437
Posted 22 June 2006 - 09:56 AM
I am asking for some advice, on remote Unattended installation.
I have been installing both Xp and Windows2000 remotely on to PC and laptop's recently with no problems at all, and it has made life a lot easier. Recently I was presented with a new PC to carry out a remote installation of windows 2000 plus other applications, and at the time thought this should be easy, how wrong I was!
The New PC uses SATA RAID disks, after reading through the doc's I installed win2000 remotely, so far so good, upon bootup, the Windows 2000 setup message F6, install third Party SCSI or Raid adapter. pressing F6 and "S" to select the A drive, the process of copying the files began, after a short while a message appear:
Quote
This happened for other files on the floppy : aar81xx.inf
aar81xx.cat
a81xxmgt.inf
a81xxmgt.cat
This I tried several times with new floppy disks with no success and eventually, I decided to install Windows 2000 server by hand directly onto the new PC, along with the floppy disk containing the driver, no problems were observed and the system booted correctly.
I have looked around the forums for a possible solution to my problem, and wondered if PYRONS method would resolve the above but ideally, I wish to save the files from the drivers floppy disk onto the remote server and install them automatically. I have done this with other drivers for network cards with no problems, it appears the SATA RAID driver needs more work to install and configure it remotely.
Any help on the above would be much appreciated, I can give more information on my configuration if this is needed right now.
Thanks
#438
Posted 13 September 2006 - 03:22 PM
Setup cannot copy the file: aar81xx.sys from the floppy[/q]
Please, do not use oempreinstall=Yes in unattenden anserver file.
If oempreinstall=Yes F6 not work.
#439
Posted 11 December 2006 - 03:48 AM
Would reduce the string length in the DevicePath in registry.
I have some problems where I have a lot of folders in my Drivers folder, making the SetDevicePath.exe not working.
If I remove some folders it works fine.
For example I have a audio driver for an IBM Intellistation where there are 20 subfolders with language files.
The same with an audio driver for an IBM M55.
I think I could remove some of those folders, but I not sure.
Anyway if the SetDevicePath.exe only added folders with an INF file in it, it would reduce the length of the string a lot.
For now my DevicePath in registry is 15077 characters long
EDIT:
I found this http://www.vernalex....tools/spdrvscn/
But dont know (yet) if it can be run from the presetup.cmd file.
This one only adds folders with an INF file in it.
EDIT2:
Just tested, it works flawless on Windows XP.
My DevicePath in registry is now 1804 characters
Other ideas are welcome
This post has been edited by booster: 11 December 2006 - 05:11 AM
#440
Posted 18 December 2006 - 04:27 PM
The driveletter of the CD is searched first:
CODE
set tagfile=\WIN51
for %%i in (c d e f g h i j k l m n o p q r s t u v w x y z) do if exist "%%i:%tagfile%" set CDDRIVE=%%i:
(thanks to serialsz for the shorter version, slightly modified)
Remark: note that the tagfile might be different for you. You might have to change it to '\WIN51IP' or '\WIN51.SP2'.
I have a question about this part. My installation source has WIN51 and WIN51IP and WIN51.sp2. Since it says I might have to change it, which of the three I listed should I use?



Help

Back to top









