In case anyone is interested I found a link to an article about Windows 8 Hidden tools:
101 2011-10-23 09:35:15
Re: Win 8 Dev. Preview is here! (37 replies, posted in Windows 8 Discussion)
102 2011-05-14 07:36:25
Re: Manual integration and installation question (29 replies, posted in Windows 7 tools)
directory7 wrote:
Yes There is an updated WAIK posted at the Microsoft download site - supposedly version 2.0.
Odd, I downloaded version 3.0 back in February. Something is amiss here.
103 2011-03-19 07:03:51
Re: DrivePacks = unstable images - Where to start ? (8 replies, posted in Universal Imaging)
I've used pretty much the same procedure since I started slipstreaming/integrating XP Pro.
Start with XP Pro w/SP3 CD - copied to hard drive.
[My instructions to myself include this. Looking at an XP Home CD \DOCS, \DOTNETFX, \SUPPORT, and \VALUEADD and an XP Pro CD \CMPNENTS, \DOCS, \SUPPORT, and \VALUEADD do not have to be included as a part of the source when using the RyanVM Integrator because no files/programs in these folders are updated when the Integrator is run and they simply consume space that could be used by other Addons included in the Integrator as part of its operation. (The user could always return to the source CD in the future if it was determined something here was required. Also, in \I386, the folders \LANG, \WIN9XMIG, \WIN9XUPG, and \WINNTUPG were also not effected by the Integrator and, depending on the end use of the final CD, one, two, three, or all of them could also be eliminated form the source as the Integrator was being used; thereby providing more space for additional Addons to be integrated.)
Searching Microsoft I determined that:
\LANG is required if languages other than English are to be installed.
\WIN9XMIG is required when migrating from Windows 95/98 to XP.
\WIN9XUPG contains entries for specifying an unattended install from Win98/SE/ME to XP
\WINNTUPG is required for a network upgrade to XP. (From Siginet: In the \WINNTUPG folder leave two files: NETMAP.INF and NETUPGRD.DLL to prevent an error message when attempt to install while in Windows.)
\CMPNENTS folder is required for Media Center / Tablet PC installs.]
Use RyanVM Integrator 1.6.1 beta 2.1 to slipstream updates and addons. Have the RyanVM Integrator 'call' DPs_Base.exe and wait while it does its thing. (Latest I've been using is: DPs_BASE_10111b29.exe)
After Driver Packs is run and before the .ISO is created: WINNT.SIF - delete the following three lines if you ever want to use the newly created CD to do a 'repair' install -
[Unattended]
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore
Create ISO.
At no time do I use nLite to change anything. I have been doing it this way for years and am very satisfied with the outcome.
104 2010-11-16 08:35:48
Re: [IMPL] Minimizing all of driverpack while streamlining (7 replies, posted in Feature Requests)
I, for one, don't mind the box staying on top and keeping me informed of what is going on; what I would like though is to be able to move it somewhere else on my screen - rather than smack dab right in the middle - let me move it to a corner (if possible).
105 2010-10-30 07:19:30
Re: Manual integration and installation question (29 replies, posted in Windows 7 tools)
There is an updated WAIK posted at the Microsoft download site - supposedly version 2.0.
106 2010-09-24 10:02:34
Re: RT Se7en Lite (10 replies, posted in Windows 7 tools)
Latest versions of RT 7 Lite have been modified to permit user to install things to partitions other than C:\> - have not yet had time to test - probably tomorrow.
Tried both 32-bit and 64-bit versions and they now allowed the user to have Win7 installed in drives/partitions other thna C:\ - so that issue has gone away.
107 2010-08-24 08:38:52
Re: Unable to make SATA controller/SSD combo bootable (10 replies, posted in Hardware)
Go to www.belarc.com and download The Belarc Advisor. After it's installed and then updates itself you will be presented with a comprehensive list of your hardware - see if that will give you motherboard and BIOS info and, therefore, a possible name to try a Google search.
And is's a SATA to IDE adapter - not IDE to SATA - which is different (at least that's how Cyberguys lists it).
108 2010-08-23 15:46:09
Re: Unable to make SATA controller/SSD combo bootable (10 replies, posted in Hardware)
bobcat250 wrote:
As I mentioned, I will probably pursue ChiefZeke's suggestion and purchase a better and (hopefully) bootable SATA controller.
On another topic: are any of you familiar with this so-called "interrupt 19 (INT19)" option which supposedly, if enabled, allows the BIOS to "capture" the controller?
Thanks again.
I did not say buy a bootable SATA controller - I recommended you purchase a SATA to IDE adapter which you can then use to plug the SATA SSD into the IDE connector.
A Google search on: interrupt 19 gives an explanation of what it does and it is a BIOS option - so if you do not have that option your are out-of-luck.
Also, from a book I have: "The BIOS Companion": An Interrupt Vector Table, which is 1K in size, including the name and address of the program providing the interrupt service. Interrupt vectors point to any of 255 routines in the BIOS or DOS that programs can use to perform low level hardware access.
109 2010-08-23 08:11:17
Re: Unable to make SATA controller/SSD combo bootable (10 replies, posted in Hardware)
If you can't change the BIOS to make an addin controller bootable then there is no way you are going to be able to boot from the SSD.
Is is safe to assume you have the lates update to the BIOS for the motherboard in use?
Check www.cyberguys.com for a SATA to IDE adapter - that could be one way around your problem.
Checked my Cyberguys catalog; connect SATA drives to IDE controller: 1 port device = item # 202 0252 $13.99; 2 port device = item # 202 0254 $17.19
Back to you
110 2010-08-16 15:30:22
Re: RT Se7en Lite (10 replies, posted in Windows 7 tools)
Win7 Customizer looks like it does not have the drive/partition issue I mentioned with RT7 Lite. More checking is required but I did get it to accept the initial locations as shown on the opening screen and it made no errors.
Look here: http://www.msfn.org/board/topic/139077- … windows-7/
111 2010-08-12 09:32:12
Re: RT Se7en Lite (10 replies, posted in Windows 7 tools)
At first I had no idea as to why the program was not working on my install of Win7; when I went to their forum I ran across a posting from someone else complaining about the same issue. The answer was basically: Tough - it's not my fault if you did not install to C:\> - don't expect me to change my program - you must change your install location.
So, I've decided to metion this whenever and wherever I find any mention of RT 7 Lite.
If you go here: http://www.rtwincustomize.net/web/viewt … amp;t=8292 you'll find the message that I mention above.
112 2010-08-11 09:51:51
Re: RT Se7en Lite (10 replies, posted in Windows 7 tools)
Tried it - doesn't work if the user has installed Win7 on a drive/partition not C:\>.
113 2010-08-10 08:59:09
Re: USB Install versus DVD (19 replies, posted in Other)
I tried Google and found this: http://wiki.eeeuser.com/windowsxpusb
Have not tried it - but a quick read is promising.
114 2010-07-31 08:01:16
Re: 7Lite? (11 replies, posted in Other)
I've been trying to use RT 7 Lite for about a month and have not been successful.
Many trips to various forums and sending messages to the authors went nowhere until I ran across a posting that provided an answer: RT 7 Lite will only run if Win7 has been installed on the C:\> drive - if the user is dual/multi-booting and installed Win7 on a drive not C:\ then RT 7 Lite fails to run.
My #1 system has Win7 32-bit on drive I:\> and Win7 64-bit on drive H:\> - RT 7 Lite fails.
My #2 system has Win7 32-bit also on drive H:\> - RT 7 Lite fails here too.
In the RT 7 Lite form the program author's response to this problem was it's the users fault not his. I guess his position is that to use his program you must install Win7 on drive C:\ - period.
115 2010-06-29 08:38:58
Re: [tool] RT7Lite Win7 tool (9 replies, posted in Windows 7 Discussion)
Downloaded both 32-bit and 64-bit versions and ran the installer in appropriate version of Win7 - program did not appear to be working correctly.
When it started I got a black screen with white lettering and a screen behind the opening screen indicating it was downloading/installing WAIK - which would be a waste of time as I had already installed WAIK in both versions of Win7.
When RT7 Lite is started should it not appear as the opening screens I see on their web site? Anyone know?
I filled out their problem report but no answer or test to perform yet so I figured I'd ask here.
Thanks
116 2010-06-27 16:25:30
Re: [tool] RT7Lite Win7 tool (9 replies, posted in Windows 7 Discussion)
Went to the MSFN forum and found mention of the progam there - followed the links and downloaded both 32-bit and 64-bit versions. Not to find time to run some tests.
117 2010-06-25 07:57:37
Re: [tool] RT7Lite Win7 tool (9 replies, posted in Windows 7 Discussion)
The link did not work.
118 2010-02-16 09:35:40
Re: Results using Base 10.01.24 from within RVM_Integrator_1.6.1 beta 2.1 (7 replies, posted in Feedback and Support - DriverPacks Base)
More info - I had mentioned AHCI here: http://forum.driverpacks.net/viewtopic.php?id=4029 and never saw an answer indicating AHCI had been added to Mass Storage, or I missed something somewhere.
119 2010-02-16 09:27:40
Re: Results using Base 10.01.24 from within RVM_Integrator_1.6.1 beta 2.1 (7 replies, posted in Feedback and Support - DriverPacks Base)
OverFlow wrote:
Well definately don't use both at the same time
.
If you have the hardware to test on that hardware please do (with our pack) and report the result
.
If it works then we can pass on the result to Ryan and RogueSpearI made considerable updates to the mass storage code in that release the problem may no longer exist, if it does let's get it fixed
PS Donors are automatically made members of the testing team
The Mass Storage driver pack I have is: DP_MassStorage_wnt5_x86-32_100125.7z dated Jan 2010 - (don't have one dated May 2008) - does this version include AHCI drivers?
I was unaware of the donor to tester being automatic.
120 2010-02-15 10:19:07
Re: Results using Base 10.01.24 from within RVM_Integrator_1.6.1 beta 2.1 (7 replies, posted in Feedback and Support - DriverPacks Base)
OverFlow wrote:
So this is a report of success with the Beta version of BASE? or did I miss something?
I notice you skipped mass text mode?Thanks for reporting sir!
PS please report on beta / test versions in the testing team forum
I wasn't sure on where to mention the results as I don't believe I am actually a member of the testing team so I figured feedback would work.
I'm guessing your question about mass text mode refers to DP_Mass Storage - that was omitted because the folks at http://www.ryanvm.net/forum/viewtopic.php?t=8101 when I asked about AHCI drivers said to use these from Rogue Spear: RogueSpearAddonsM2-XPSP3-NoKtD_8.09.7z and MassStorageAddons_IaStor_8.5.0.1032.7z and to make sure not to use Driver Packs Mass Storage. If the Driver Pack's Mass Storage suppprts AHCI then I can use and pass on the word in the Ryan and Rogue Spear forums.
121 2010-02-14 10:49:34
Topic: Results using Base 10.01.24 from within RVM_Integrator_1.6.1 beta 2.1 (7 replies, posted in Feedback and Support - DriverPacks Base)
Back in November I opted to make a new XP Pro w/SP3 CD updated as of that date to get ready for Windows 7. That failed when I got Fatal Error code 800b0100 and I had to do a repair install using a CD a had created almost a year earlier. (That worked.)
Doing a bit of reading in forums and some research I opted to try Microsoft's PC2007 Virtual Machine. That worked and I determined that the Fatal Error was caused by a corruption in the XP w/SP3 copy of the CD I had on my hard drive. It seems the FAT32 to NTFS conversion I had done on the drive partition that contained the copy of the CD was at fault. I deleted all of those files and re-copied the XP Pro w/SP3 CD to the same partition and tried again; this time successfully. What follows is the log file created when I ran DriverPacks Base to create the new CD. Note that no errors occured during the install of XP in the virtual machine.
2010-02-13 13:51:39 : <INIT> DriverPacks BASE 10.01.24 initialized.
2010-02-13 13:51:39 : <INIT> Host environment: WIN_XP Service Pack 3 X86 on a X64 CPU.
2010-02-13 13:51:39 : <INIT> Created temporary working directory.
2010-02-13 13:51:39 : <INIT> Imported proxy settings from Internet Explorer.
2010-02-13 13:51:39 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2010-02-13 13:51:39 : <INIT> Detected DriverPack Chipset 1002r1!
2010-02-13 13:51:39 : <INIT> Detected DriverPack CPU 912!
2010-02-13 13:51:39 : <INIT> Detected DriverPack Graphics A 1002r1!
2010-02-13 13:51:39 : <INIT> Detected DriverPack LAN 1002r4!
2010-02-13 13:51:39 : <INIT> Detected DriverPack Sound A 1001b2!
2010-02-13 13:51:39 : <INIT> Detected 3rd Party DriverPack HID 90204!
2010-02-13 13:51:39 : <INIT> Detected 3rd Party DriverPack Misc 90909!
2010-02-13 13:51:39 : <INIT> Detected 3rd Party DriverPack Monitor 908130!
2010-02-13 13:51:39 : <INIT> Detected 3rd Party DriverPack USB 80911!
2010-02-13 13:51:39 : <INIT> Finished scanning.
2010-02-13 13:51:39 : <INIT> Detected settings file "G:\DriverPacks\DPs_BASE.ini".
2010-02-13 13:51:39 : <INIT> Windows XP Professional - Retail SP3 detected.
2010-02-13 13:51:39 : <INIT> wnt5_x86-32_disc is the selected installation platform .
2010-02-13 13:51:39 : <INIT> Imported settings from settings file.
2010-02-13 13:51:39 : <GUI> Initialized GUI.
2010-02-13 13:51:39 : <GUI> Created a list of all available language files.
2010-02-13 13:51:39 : <GUI> Set the last used language, English, as the GUI language.
2010-02-13 13:51:48 : <GUI> Refreshed UpdateChecker with success.
2010-02-13 13:53:17 : <GUI> Saved settings!
2010-02-13 13:53:17 : <GUI> Closed GUI.
2010-02-13 13:53:17 : <SEL> Selected module: mod_slip_wxp_x86-32_disc_m2.
2010-02-13 13:53:21 : <PREP> Removed all attributes from \I386.
2010-02-13 13:53:21 : <PREP> Deleted old DriverPacks.
2010-02-13 13:53:21 : <PREP> Deleting old method 2 related files.
2010-02-13 13:53:21 : <PREP> Deleted \OEM\bin\DevPath.exe.
2010-02-13 13:53:21 : <PREP> Deleted \OEM\bin\7-zip32.dll.
2010-02-13 13:53:21 : <PREP> Deleted \OEM\bin\DPsFnshr.7z.
2010-02-13 13:53:21 : <PREP> Deleted \OEM\bin\DPsFnshr.ini.
2010-02-13 13:53:21 : <PREP> Deleted \OEM\bin\un7zip.exe.
2010-02-13 13:53:21 : <PREP> Deleted \OEM\DP_Install_Tool.cmd.
2010-02-13 13:53:21 : <PREP> Deleted \OEM\DPINST.exe.
2010-02-13 13:53:21 : <PREP> Deleted \OEM\DPInst.xml.
2010-02-13 13:53:21 : <PREP> \I386\winnt.org was not found, \I386\winnt.sif was not restored.
2010-02-13 13:53:21 : <PREP> Either txtsetup.org or dosnet.org was not found. The removal of
2010-02-13 13:53:21 : <PREP> any Service Packs we may have added with Driverpacks and or
2010-02-13 13:53:21 : <PREP> the removal of any Mass Storage textmode drivers was skipped
2010-02-13 13:53:26 : <PREP> Verified method 2 references don't exist in txtsetup.sif or dosnet.inf.
2010-02-13 13:53:27 : <PREP> Cleaned up \$OEM$\cmdlines.txt.
2010-02-13 13:53:27 : <PREP> Deleted \$OEM$\ROE.exe.
2010-02-13 13:53:27 : <SLIP> Necessary directory structure for method 2 already exists.
2010-02-13 13:53:27 : <SLIP> Copying files necessary for method 2.
2010-02-13 13:53:29 : <SLIP> Extracted additional files necessary for method 2.
2010-02-13 13:53:30 : <SLIP> expanded setup.ex_ to setuporg.exe
2010-02-13 13:53:30 : <SLIP> SETUP.EX_ Backed-up Successfully
2010-02-13 13:53:31 : <SLIP> Method 2 setup.ex_ installed
2010-02-13 13:53:31 : <SLIP> Created \I386\presetup.cmd file.
2010-02-13 13:53:31 : <SLIP> txtsetup.sif Backed-up Successfully
2010-02-13 13:53:31 : <SLIP> dosnet.inf Backed-up Successfully
2010-02-13 13:53:31 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2010-02-13 13:53:33 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2010-02-13 13:53:33 : <SLIP> Copied DriverPack Chipset to \OEM.
2010-02-13 13:53:33 : <SLIP> Copied DriverPack CPU to \OEM.
2010-02-13 13:53:37 : <SLIP> Copied DriverPack Graphics A to \OEM.
2010-02-13 13:53:37 : <SLIP> Copied DriverPack LAN to \OEM.
2010-02-13 13:53:41 : <SLIP> Copied DriverPack Sound A to \OEM.
2010-02-13 13:53:43 : <SLIP> Renamed DriverPack DPC1002r1.7z to DPC1002r.7z in \OEM.
2010-02-13 13:53:43 : <SLIP> Renamed DriverPack DPGA1002r1.7z to DPGA1002.7z in \OEM.
2010-02-13 13:53:43 : <SLIP> Renamed DriverPack DPL1002r4.7z to DPL1002r.7z in \OEM.
2010-02-13 13:53:43 : <SLIP> Renamed DriverPack DPSA1001b2.7z to DPSA1001.7z in \OEM.
2010-02-13 13:53:43 : <SLIP> Renamed DriverPack DP_HID_wnt5_x86-32_90204.7z to DP_HID_w.7z in \OEM.
2010-02-13 13:53:43 : <SLIP> Renamed DriverPack DP_Misc_wnt5_x86-32_90909.7z to DP_Misc_.7z in \OEM.
2010-02-13 13:53:43 : <SLIP> Renamed DriverPack DP_Monitor_wnt5_x86-32_908130.7z to DP_Monit.7z in \OEM.
2010-02-13 13:53:43 : <SLIP> Renamed DriverPack DP_USB_wnt5_x86-32_80911.7z to DP_USB_w.7z in \OEM.
2010-02-13 13:53:43 : <SLIP> Copied DriverPacks to \OEM.
2010-02-13 13:53:43 : <SLIP> Will not slipstream patches, Service Pack 3 was detected.
2010-02-13 13:53:46 : <SLIP> Updated \I386\winnt.sif to support method 2.
2010-02-13 13:53:46 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2010-02-13 13:53:46 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2010-02-13 13:54:48 : <SLIP> DP_Install_Tool was copied successfully
2010-02-13 13:54:48 : <SLIP> Slipstream finished in 1 minutes and 31 seconds.
2010-02-13 13:54:52 : <CLNP> Temporary working directory successfully deleted.
- = DriverPacks BASE ini settings used = -
[General]
; preferred language
prefLang = "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons = "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI = "yes"
[Settings]
; disc/bartpe/multibootDisc
instPlatform = "disc"
; trailing backslash is allowed, but not necessary
location = "G:\RyanVM\XPPro#1Integrated"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks = "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod = "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod = "GUIRunOnce"
; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD = "false"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation = "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC = "yes"
; you should only add this section if you've set [Settings]\DriverPacks to "select"
[SelectDriverPacks]
DP_Chipset = "yes"
DP_CPU = "yes"
DP_Graphics_A = "yes"
DP_LAN = "yes"
DP_Sound_A = "yes"
DPs_3rd_party = "yes"
DP_MassStorage_textmode = "no"
; this section is optional!
[OptionalSettingsOther]
; CCC/CCP/None, use ATI Catalyst Control Center or ATI Catalyst Control Panel (only relevant when slipstreaming Graphics DriverPack)
; 1/2/3/None, use Nvidia Control Panel - 1 = Old, 2 = New, 3 = Both, None
ATI_cpl = "CCC"
Nvidia_cpl = "None"
2010-02-13 13:54:52 : <CLNP> Create a DPs_Base.log backup @ G:\DriverPacks\LogFiles\DPs_BASE_10-02-13_13-54.log
2010-02-13 13:54:52 : <CLNP> Program terminated.122 2010-02-03 08:29:06
Re: New Intel Rapid Storage Technology - does it change Mass Storage? (10 replies, posted in Other)
OverFlow wrote:
Some of the AHCI issues have to do with load order...
IE the HWID is the same for both modes but the non AHCI driver is listed first. First come first serveThere is no possable way to tell how to fix your issue UNLESS you provide the HWIDs of the offending machine. or at least the HWIDs of the mass storage controller
My earlier questions and comments about AHCI and a posting of HWIDS can be found here: http://forum.driverpacks.net/viewtopic.php?id=4029
Also, copies I have saved here for my Win7 installation are from before the release of Win7 final. I can rerun the Save HWIDS program again on the final install of Win7 32-bit and 64-bit AHCI install if they are needed - not possible for IDE now.
123 2010-02-01 10:39:26
Topic: New Intel Rapid Storage Technology - does it change Mass Storage? (10 replies, posted in Other)
Intel Matrix Storage Manager (Intel_MSM) has been replaced by Intel Rapid Storage Technology (Intel_RST) - information I just happened to run across yesterday 30Jan10.
Go here for instruction on integrating Intel's SATA AHCI: http://www.msfn.org/board/index.php?showtopic=107504 which led me to check things out;
and here: http://www.station-drivers.com/ for the drivers - listed under Intel.
I asked at Rogue Spear if this new information requires an update to RogueSpear's IaStor MassStorage Addon V8.5.0.1032 - which was last updated on 20081011.
Question: if the AHCI drivers are incorporated into the XP CD does this mean the user could boot from it and the drivers installed by XP would be either IDE or AHCI - depending on the BIOS selection? Anyone know?
124 2010-01-10 07:35:16
Re: driverpacks for x64 XP (1 replies, posted in Installation Platforms)
Go here: http://forum.driverpacks.net/viewtopic.php?id=4228 and read my question and the nswer.
125 2009-12-26 06:22:56
Topic: [IMPL] Intel Inf installer 9.1.1.1025 released (2 replies, posted in DriverPack Chipset)
A Christmas present - it was released today.