DisabledTrucker
Content Type
Profiles
Forums
Events
Posts posted by DisabledTrucker
-
-
As far as having two different directories for Raid and IDE, it may have been me that had it shown as that was how I was doing it before I went with the txtmode setup of the drivers and calling them from within WinNT.sif exclusively, (I have yet to test this method, but will soon.) In my setup prior I was using:
$OEM$\Drivers\
...
IDE\
...
RAID\
The IDE held all my files for the motherboards IDE drivers and the RAID held all my RAID drivers for the SATA-RAID controller on my hdd, which are different. In that I have an NVidia mobo which uses NVidia drivers for the IDE and a Promise controller to handle my SATA-RAID. I have since compiled them both into one folder and thus don't need to have both an IDE and a RAID section even in my external, (outside i386 folder,) $OEM$ folder. I have also since put the rest of my motherboard drivers in a PNPdrvrs folder within my i386\$OEM$ folder which contains the rest of my drivers for my motherboard. Since all my motherboards are Nvidia based, this solution should be best for my needs. Now to figure out how to get the ATI and Creative drivers to install the same way with their control panels, etc installed as well. Which would be especially nice if I can also gain use of the AIW's files as well that way. Though I only use the ATI/Creative drivers on one of my systems, it would still be nice if I can do away with the external $OEM$\Drivers folder altogether. Though I will still need the external $OEM$ folder to include other software it would tremendously save space on my UXPCD if all my drivers would work in the internal $OEM$ folder so it's automatically removed once everythings installed without having to make a seperate clean up script to do it.
FWIW, putting the drivers in the internal $OEM$ folder not only allows for instant deletion when installing from CD, but it also isn't supposed to require any inclusion of putting information into any other file but the WinNT.sif file as it's all automatically found in the \txtsetup and \pnpdrvrs path where Windows XP automatically looks for those drivers before looking elsewhere for them when they aren't found in the .cab files. Less work on my part if this works, and less strain on my single brain cell.
After further testing none of these methods I talked about in this worked at all for me, sorry for the confusion...
0 -
For my extensive list of favorites, I use the export function to make an .htm file out of the entire list then when the computer boots the first time, I import that list and copy it to the default user file, which allows for it to be used systemwide. Since I have yet to find a way to import it into the default users section while installing, yet.
0 -
um, I thought this board has rules against posting this sort of thing? Is this not a "hack"?
0 -
Though this will be a rather long post, I wanted to include what is being said in the FAQ's section for this patch, especially the portions in relation to the O/S and programs that are affected and it's responses. Without further ado:
Frequently asked questions (FAQ) related to this security update
Why are there several affected programs and components?
Windows XP, Windows XP Service Pack 1, and Windows Server 2003 provide an operating system version of the component that is vulnerable to this issue. Earlier versions of Windows did not provide an operating system version of this component. Therefore, when you install programs that require this functionality on earlier versions of Windows, this component is commonly installed. Typically, when these programs are installed on Windows XP, Windows XP Service Pack 1, or Windows Server 2003 they only use the version that is provided by the operating system, even if they install a copy of the vulnerable component.
The exceptions to this are Office XP, Visio 2002, Project 2002, Office 2003, Visio 2003, and Project 2003. To make sure that JPEG images are processed consistently across all operating systems, these programs use their own version of the vulnerable component. This version of the vulnerable component is installed on all operating systems that are supported by these programs. If you have installed these programs, you must install the update for these programs. You must also install an operating system update if you use Windows XP, Windows XP Service Pack 1, or Windows Server 2003.
Microsoft has created a tool that will also assist in detecting if you are running one or more affected products and components. Where can I get more information about this tool?
Microsoft has created the GDI+ Detection tool to assist customers in detecting if they are running one or more affected products that contain a vulnerable version of the JPEG Parsing component on their system. Microsoft Knowledge Base Article 873374 describes this tool as well as provides instructions on how to download this tool.
What does the GDI+ Detection tool do?
The GDI+ Detection tool scans your system for non-operating system products that are known to contain the vulnerable component. It then directs consumers to the appropriate locations for downloading an update to address the vulnerability.
Will the GDI+ Detection tool tell me if my system is at risk from this vulnerability?
No. The tool is only designed to scan the system and detect for certain installed products that are known to contain the vulnerable component. The tool is not able to determine if these products have already been updated to use a secure version of the affected component.
What is GDI+?
GDI+ is a graphics device interface that provides two-dimensional vector graphics, imaging, and typography to applications and programmers.
If I use Windows XP Service Pack 2 and use any of the affected software, what should I do?
Windows XP Service Pack 2 does not contain a vulnerable version of the affected component. However, if you have installed any of the affected Office, Visio, or Project applications you should install the updates for those applications. The easiest way to address this vulnerability is to install the updates provided by Office Update. If you have not installed any of the affected Office, Visio, or Project applications you do not have to install any other security updates because the other affected software and affected components use the operating system version of the vulnerable component on Windows XP Service Pack 2.
The exception for this is if you use Visual Studio .NET 2002 or Visual Studio .NET 2003 to develop applications that redistribute the Gdiplus.dll file. In this case you need to install the security updates for those programs even if you are using Windows XP Service Pack 2. See the Security Update Information section for these updates for more information.
If I use Windows XP, Windows XP Service Pack 1, or Windows Server 2003 and use any of the affected software, what should I do?
If you have installed any of the affected Office, Visio, or Project applications the easiest way to address this vulnerability is to install the updates provided by both Windows Update and Office Update. If you have not installed any of the affected Office, Visio, or Project applications the easiest way to address this vulnerability is to install the updates provided by Windows Update. You do not have to install any other security updates because the other affected software and affected components use the operating system version of the vulnerable component on Windows XP, Windows XP Service Pack 1, and Windows Server 2003.
The exception for this is if you use Visual Studio .NET 2002 or Visual Studio .NET 2003 to develop applications that redistribute the Gdiplus.dll file. In this case you need to install the security updates for those programs as well as the security update for Windows XP, Windows XP Service Pack 1, or Windows Server 2003. See the Security Update Information Sections for these updates for more information.
If I use Windows 98, Windows 98 Second Edition (SE), Windows Millennium Edition (Me), Windows NT 4.0, or Windows 2000, what should I do?
By default, these operating systems do not natively provide a version of the vulnerable component and are not affected. However, the vulnerable component is installed on these non-affected operating systems when you install any of the software programs or components that are listed in the Affected Software and Affected Components sections of this bulletin.
If you have installed any of the affected programs or components, you should install the required security updates for those programs or components. For example, if you have Internet Explorer 6 Service Pack 1 and Office XP installed on your Windows 2000 system, you have to install the Internet Explorer 6 Service Pack 1 security update and the Office XP security update. If you have not installed any of the affected programs or components, you do not have to install any security updates.
If I use versions of Internet Explorer that are earlier than Internet Explorer 6 Service Pack 1, am I vulnerable to this issue?
Internet Explorer 5.01 Service Pack 3, Internet Explorer 5.01 Service Pack 4 on Windows 2000, and Internet Explorer 5.5 Service Pack 2 on Windows Me have been tested and they are not vulnerable.
Internet Explorer 6 is only supported when using Windows XP, Windows XP Service Pack 1, and Windows Server 2003. Internet Explorer 6 on Windows XP, Windows XP Service Pack 1, and Windows Server 2003 uses the operating system version of the vulnerable component. When the Windows XP, Windows XP Service Pack 1, and Windows Server 2003 operating system update is installed, Internet Explorer 6 is not vulnerable. Windows XP Service Pack 2 includes Internet Explorer 6 Service Pack 2 and is not vulnerable to this issue. Internet Explorer 6 is no longer in support on other operating systems and may be vulnerable to this issue on those operating systems. Customers who do not use Windows XP, Windows XP Service Pack 1, or Windows Server 2003 and who use versions of Internet Explorer 6 that are earlier than Internet Explorer 6 Service Pack 1 should upgrade to Internet Explorer 6 Service Pack 1 and then install the Internet Explorer 6 Service Pack 1 security update provided in this security bulletin, or upgrade to Windows XP Service Pack 2 for Windows XP customers. To install Internet Explorer 6 Service Pack 1, visit the following Web site. For more information about the support lifecycle for Internet Explorer, visit the following Microsoft Support Lifecycle Web site.
If use Visual Studio .NET 2002, Visual Studio .NET 2003, the Microsoft .NET Framework 1.0 SDK Service Pack 2, or the Microsoft Platform SDK Redistributable: GDI+ to develop applications, what should I do?
When these programs are installed on Windows XP, Windows XP Service Pack 1, or Windows Server 2003 they use the operating system version of the vulnerable component. If you are using these programs on Windows XP, Windows XP Service Pack 1, or Windows Server 2003 make sure that you install the operating system version of the security update. If you are using these programs on other operating systems make sure that you install the update for these programs.
However, if you use these programs to create applications that distribute a version of the Gdiplus.dll file you need to install the appropriate security update based on the development tool you use, even if you have installed the Windows XP, Windows XP Service Pack 1, or Windows Server 2003 security update, or are using Windows XP Service Pack 2. If you use the Gdiplus.dll file for JPEG processing you should rebuild and redistribute your application using the updated version of the Gdiplus.dll file. For more information, see the appropriate Security Update Information sections depending on the developer tool you use.
Why is the security update for .NET Framework in a Service Pack?
This issue does not affect customers who have already deployed Microsoft .NET Framework 1.0 Service pack 3 (SP3) and Microsoft .NET Framework 1.1 Service Pack 1 (SP1). These service packs, released prior to the release of this security bulletin, already contain the security update for this issue as well as other security changes for all reported customer issues found after the release of these software components. Therefore, we highly recommended that customers using .NET Framework 1.0 or 1.1 install these Service Packs for increased security not only for this vulnerability but also for all reported customer issues found after the release of the Microsoft .NET Framework.
Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine if this update is required?
Yes. MBSA does detect if the update for this vulnerability is required for Office XP, Office 2003, Project 2002, Project 2003, Visio 2002, and Visio 2003. However, MBSA does not currently support the detection of several of the programs that are listed in the Affected Software and Affected Components section of this security bulletin. For detailed information about the programs that MBSA currently does not detect, see Microsoft Knowledge Base Article 306460. If you have installed any of the programs that are listed in the Affected Software and Affected Components section of this security bulletin you may have to manually determine if you have to install the required update. For example, a Windows 2000 or Windows NT 4.0 system that has installed Internet Explorer 6 Service Pack 1 will need to install the Internet Explorer 6 Service Pack 1 security update and MBSA will not detect the missing update in these configurations. Also, MBSA cannot use the Office Detection Tool to scan remote systems, it will only use this tool to scan a system locally for required security updates. For more information about MBSA, visit the MBSA Web site.
Note After April 20, 2004, the Mssecure.xml file that is used by MBSA 1.1.1 and earlier versions is no longer being updated with new security bulletin data. Therefore, scans that are performed after that date with MBSA 1.1.1 or earlier will be incomplete. All users should upgrade to MBSA 1.2 because it provides more accurate security update detection and supports additional products. Users can download MBSA 1.2 from the MBSA Web site. For more information about MBSA support, visit the Microsoft Baseline Security Analyzer 1.2 Q&A Web site.
Can I use Systems Management Server (SMS) to determine if this update is required?
Yes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site. SMS uses MBSA for detection; therefore, SMS has the same limitation listed earlier in this bulletin related to programs that MBSA does not detect. However, SMS can also use the Microsoft Office Inventory Tool to detect for required updates for Microsoft Office components.
Can I use SMS to determine if programs are installed that have to be updated?
Yes. SMS can help detect if any of the affected programs or affected components are installed that may have installed a version of the vulnerable component. SMS can search for the existence of the file Gdiplus.dll. For the affected programs and components listed in this bulletin you need to update all versions of Gdiplus.dll that are earlier than version 5.1.3102.1355. See the ‘Could I still be vulnerable even after I have installed all required security updates?’ FAQ in this bulletin for more information about other applications that may have installed the Gdiplus.dll file.
However, it is important to note that you should install the available security updates instead of manually updating the affected component. Manually updating the affected component could create application compatibility issues and is not supported. Also, applications that feature ‘Detect and Repair’ functionality will not receive the necessary information required to prevent these features from potentially introducing the vulnerability upon execution if the affected component is manually updated.
Installations of Office XP, Visio 2002, Project 2002, and Internet Explorer 6 Service Pack 1 (SP1) combine the features of the vulnerable component with other files. For Office XP and Project 2002 you would also have to search for the existence of the Mso.dll file. Update all versions of Mso.dll that are earlier than version 10.0.6714.0. For Visio 2002, you have to search for the existence of the Mso.dll file and the Gdiplus.dll file because Visio 2002 distributes both files, except on Windows XP, or Windows Server 2003 where it only distributes the Mso.dll file.
For installations of Internet Explorer 6 Service Pack 1 that are not running on the Windows XP or Windows Server 2003 operating systems, search for the Vgx.dll file. Update all versions of Vgx.dll that are earlier than version 6.0.2800.1411. Internet Explorer 6 Service Pack 1 uses the operating system version of the vulnerable component on Windows XP and Windows Server 2003. You do not have to update Internet Explorer 6 Service Pack 1 for those operating systems. These .dll files are documented in the Security Update Information section of this security bulletin. You can also deploy the updates provided in this bulletin using the Inventory and Software Distribution feature of SMS.
I use Software Update Services (SUS) to deploy security updates in my enterprise. Should I deploy the GDI+ Detection Tool to all of my systems?
While it is possible to deploy the GDI+ Detection Tool via SUS to all of the systems in an enterprise, it is not recommended or supported. The GDI+ Detection Tool will direct end users back to the Microsoft Windows Update site to scan their machines for updates.
What security updates will Windows Update offer to help address this vulnerability?
Windows Update will offer the required operating system updates for Windows XP, Windows XP Service Pack 1, and Windows Server 2003. Windows XP Service Pack 2 does not require an update because it does not contain a vulnerable version of the affected component. Windows Update will offer the Internet Explorer 6 Service Pack 1 security update to Windows 98, Windows 98 SE, Windows Me, Windows NT 4.0 and Windows 2000 operating systems. Windows Update will offer the .NET Framework, version 1.0 Service Pack 2 (SP3) and the .NET Framework, version 1.1 Service Pack 1 to Windows NT 4.0 and Windows 2000 operating systems. These security updates are not offered to Windows XP or Windows Server 2003 systems because these components use the operating system version of the component on Window XP and Windows Server 2003.
What security updates will Office Update offer to help address this vulnerability?
Office Update will offer the required updates for Office XP, Office 2003, Project 2002, Project 2003, Visio 2002, and Visio 2003. These security updates are required on all operating systems where these products are installed. Office 2003 Service Pack 1, Visio 2003 Service Pack 1, and Project 2003 Service Pack 1 are not affected and will be offered to customers using Office 2003, Project 2003, and Visio 2003 instead of the individual updates. Customers who have installed these service packs are not affected by this vulnerability from these applications.
What security updates will not be offered through Windows Update or Office Update to help address this vulnerability and should be manually installed?
Windows Update and Office Update do not provide support for the remaining programs. This includes the security updates for Visual Studio .NET 2002 (and all included programs), Visual Studio .NET 2003 (and all included programs), Greetings 2002, Picture It! (all versions), Digital Image (all versions), the Microsoft .NET Framework version 1.0 SDK Service Pack 2, Producer for Microsoft Office PowerPoint (all versions), and the Platform SDK Redistributable: GDI+. These security updates are required on Windows 98, Windows 98 SE, Windows Me, Windows NT 4.0 and Windows 2000 operating systems where these products are installed. Note Visual Studio .NET 2002 Enterprise Architect and Visual Studio .NET 2003 Enterprise Architect include Visio 2002. Visio 2002 is supported by Office Update.
Could I still be vulnerable even after I have installed all required security updates?
Yes. There are cases in which you might be vulnerable to this issue even after you install the required operating system update and the updates for programs or components that are listed in the Affected Software and Affected Components sections of this bulletin. The following examples document some of the possible cases:
• You may have installed a third-party program that has installed the affected component. If the Gdiplus.dll file is installed on your system, you may have to install an update for that program. It is possible that not every program that installs this file is vulnerable to this issue because it may not use the Gdiplus.dll file to process JPEG images. However, only the manufacturer of that program can make that determination. This could include third party applications that were developed using Visual Studio .NET 2002, Visual Studio .NET 2003, or the Microsoft .NET Framework 1.0 SDK Service Pack 2. Typically, even if the affected component is installed on a system that is running Windows XP or Windows Server 2003, the program still uses the operating system version of the affected component.
• On Windows XP or Windows Server 2003, it is possible for a developer or administrator to force a program to bypass the vulnerable operating system component and instead use a version that they supply. This feature is not likely to be used in most circumstances. You may want to consider contacting the third-party application manufacturer for an updated version of their program, if they verify that their program uses this bypass feature. Steps to determine if you are using such a program are located in Microsoft Knowledge Base Article 835322.
In these cases, you would only be vulnerable to this issue while using the affected program to process images. Installing the operating system update and the updates for the affected programs and components listed in this bulletin will help reduce the chance that you will be attacked from the most common attack vectors an attacker could use to exploit this vulnerability.
It is important to note that you should install the available security updates instead of manually updating the affected component, if possible. Manually updating the affected component could create application compatibility issues and is not supported. Also, applications that feature ‘Detect and Repair’ functionality will not receive the necessary information required to prevent these features from potentially introducing the vulnerability upon execution if the affected component is manually updated.
Can I manually script and deploy the required security updates?
Yes. We have released Microsoft Knowledge Base Article 885885 to assist with the manual installation of some of the available security updates. This article does not provide instructions for the installation of all available security updates and is provided only as a guide in the creation of custom scripts.From what I gather what it says, is you should install this patch, but keep in mind that programs other than what is mentioned here can overwrite the files in question and thus trigger the responses you all are getting. It also goes on to describe which files are in question so you can take appropiate actions to replacing the files if the program itself wont. It also says that it can be triggered even if you have the updated patches of those programs, probably because it's finding newer versions than what it's actually checking for, so it's going to report that it's needing an upgrade which shouldn't be the case. If you have all the latest updates for all your software, then you shouldn't have a need for this patch. Though you could go back and check the files in question and assure that they are the correct versions and if not, upgrade them to the correct versions and thus not have that problem in the first place. Correct me if I am wrong here.
0 -
How's this for a default file?
*Edit*
I should mention that some of the features of that file I have yet to test, so if they don't apply to you, you may want to delete them such as the networking features. The rest of it should be fine for you, if modified to fit your situation. Especially the First five sections, (ie. [section1], [section2], etc.) , [Components], [shell], [OEMBootFiles] (HAL works, not sure about the rest,) [PCHealth], [systemRestore], and the rest all work just fine as I have used the before. It will silently install everything, but it will allow for you to do your own formatting/partitioning of your drives. This is for XP with SP-2, though some of it may only be for server 2003, most noteably the networking features. I would recommend using the SetupManager.exe in your SystemTools folder in Program files, where you should have installed it and the deploy tools, to begin with then dissect it from there, to add what you need.
0 -
Has anyone tried to slipstream XP Pro that comes on the VPC for Mac? Will SP 2 even run on VPC in Mac? If it will run on it, how would one go about doing a slipstream for the version which comes with VPC for the Mac? Since the Mac version uses a different key, I was wondering how one would go about doing a slipstream of SP-2 for it, or if it would even be possible to do it. I haven't, as of yet, attempted to put SP-2 on my Mac as it's a critical system to me, so I haven't even beta'd it on it yet. I have as of yet to find any documentation for it about compatibility or anything.
0 -
Thanks, I was hoping I wouldn't need to put anything anywhere else in one of the other files so as to k.i.s.s. Going to try it soon, will post back if any of it actually works or not. Hopefully my cmdlines.txt file doesn't mess everything else up in the process. Wish I could use one of the VM's to do it, but I have used them both extensively in the past to where I cannot gain another "free" key to use them and I unfortunately, being disabled, cannot afford to purchase one of them. Unless someone knows of a VM which is free? Though I could attempt trying it on the Mac, it's unfortunately not going to do me much good as I don't have anything like what I am attempting to do on it, as it's a powerbook.
0 -
try to do slipstreaming on a clean xp manually...
He's absolutley correct. You need to do the slipstream from a "virgin" XP cd. It can't be a CD that already had SP1 integrated into it. For some reason if you try to slipstream on a source that had SP1 integrated (or a few updates integrated) then that corrupt error occurs.
Paul
I haven't had any problem yet out of the one I am using right now, which is slipstreamed SP-2 over a M$ slipstreamed version of a SP-1 disk. I don't notice any file errors, then again, I am using the hacked files pack from this thread to do a number on my sfc_os, uxtheme, tcp_ip, and termsrv files, which the sfc_os one alone could be the reason I'm not seeing any errors.
I should mention when I did it, I used the SP-2 CD version that I got in the mail the day after it went up on the net to do the slipstreaming with. Used xpsp2.exe \integrate:x:\VRMPFPP_EN.
0 -
Let me get this straight, M$ done something which will cause a buffer underrun in a JPEG now? And the fix for it is simply a reg hack?
*Update* If your not using M$ Office pre 2004 based software and are using XPSP2 this is not needed. Unless you haven't updated your .Net to 1.1sp1, then it points you to the 1.1sp1 update. Although I do see a patch as well for IE6SP1, but am unsure if it would be needed for it. Which means unless I would need it for IE6SP1, I have no need for this patch...YAY! One less headache to destroy what's left of my last brain cell.
0 -
also see this link for the post above
Thank GOD for AMD!
Also, I noticed that people were using:
script8825.exe /Q:A /R:N
Is this a necessity or is this not one of the quiet install files? Also, where are they getting this script8825.exe file from or am I missing something here, as I don't see mention of the download for this one, or was it scripten.exe that is being referenced?
0 -
[HKEY_USERS\New\Software\Microsoft\Windows\...
"shell:ControlPanelFolder"=dword:00000000
"shell:SystemDriveRootFolder"=dword:00000000
"shell:Windows"=dword:00000000
"shell:System"=dword:00000000[HKEY_USER\Software\Microsoft\Windows\CurrentVersion\...
"shell:ControlPanelFolder"=dword:00000000
"shell:SystemDriveRootFolder"=dword:00000000
"shell:Windows"=dword:00000000
"shell:System"=dword:00000000*edited for space considerations*
I would assume that one wouldn't need both of these?
0 -
I was wanting to make sure that I have everything set up properly to install my drivers for my sata/ide devices. I will be using this UXPCD to install on several similar computers and have broken down that I need only the sets of drivers I have listed below. I wanted to make sure they are called, and thought I would do it in WinNT.sif. Hopefully I have them done correctly, but I was wanting to know if anyone would check it out for me and let me know if I have any syntax errors in my configuration. This will be the only place I will be calling for these drivers and I need to know if they should work as they are, or if I need to fix them prior to trying to use them. Below is the code from both txtsetup.oem files, then I have attached the WinNT.sif file for review. TIA.
[Nvidia Driver (Edited for content)]
[Disks]
d1 = "NVIDIA RAID DRIVER (SCSI)",\disk1,\
[Defaults]
scsi = RAIDCLASS
[scsi]
RAIDCLASS = "NVIDIA RAID CLASS DRIVER"
BUSDRV = "NVIDIA NForce Storage Controller"
[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvraid.cat
[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,BUSDRV
inf = d1, nvatabus.inf
dll = d1,idecoi.dll
catalog = d1, nvata.cat
[Config.RAIDCLASS]
[Config.BUSDRV]
[HardwareIds.scsi.RAIDCLASS]
id = "GenNvRaidDisk","nvraid"
id = "*_NVRAIDBUS","nvraid"
[HardwareIds.scsi.BUSDRV]
id = "PCI\VEN_10DE&DEV_008E", "nvatabus"
id = "PCI\VEN_10DE&DEV_0085", "nvatabus"
id = "PCI\VEN_10DE&DEV_00D5", "nvatabus"
id = "PCI\VEN_10DE&DEV_00EE", "nvatabus"
id = "PCI\VEN_10DE&DEV_00E3", "nvatabus"
id = "PCI\VEN_10DE&DEV_00E5", "nvatabus"[Promise Fastrak Driver (Edited For Content)]
[Disks]
d1 = "Promise FastTrak 376/378 Driver Diskette", \fasttx2k, \
d2 = "Promise FastTrak 376/378 Driver Diskette", \fasttx2k, \WinXP
d3 = "Promise SATA378 Driver Diskette", \ulsata, \
d4 = "Promise SATA378 Driver Diskette", \ulsata, \WinXP
d5 = "Promise FastTrak 376/378 Driver Diskette", \fasttx2k, \Win2003
d6 = "Promise SATA378 Driver Diskette", \ulsata, \Win2003
[Defaults]
scsi = FastTrak_TX2K_xp
[scsi]
UlSata_net = "Win SERVER 2003 SATA378 (tm) Controller", UlSata
UlSata_xp = "WinXP Promise SATA378 (tm) Controller", UlSata
FastTrak_TX2K_net = "Win SERVER 2003 Promise FastTrak 376/378 (tm) Controller", fasttx2k
FastTrak_TX2K_xp = "WinXP Promise FastTrak 376/378 (tm) Controller", fasttx2k
[Files.scsi.FastTrak_TX2K_net]
driver = d5, fasttx2k.sys, fasttx2k
dll = d5, ptipbmf.dll
inf = d5, fasttx2k.inf
catalog= d5, fasttx2k.cat
[HardwareIds.scsi.FastTrak_TX2K_net]
id="PCI\VEN_105A&DEV_3376", "fasttx2k"
id="PCI\VEN_105A&DEV_3373", "fasttx2k"
[Files.scsi.FastTrak_TX2K_xp]
driver = d2, fasttx2k.sys, fasttx2k
dll = d2, ptipbmf.dll
inf = d2, fasttx2k.inf
catalog= d2, fasttx2k.cat
[HardwareIds.scsi.FastTrak_TX2K_xp]
id="PCI\VEN_105A&DEV_3376", "fasttx2k"
id="PCI\VEN_105A&DEV_3373", "fasttx2k"
[Files.scsi.UlSata_xp]
driver = d4, UlSata.sys, UlSata
dll = d4, ptipbm.dll
inf = d4, UlSata.inf
[HardwareIds.scsi.UlSata_xp]
id = "PCI\VEN_105A&DEV_3373","UlSata"
[Files.scsi.UlSata_net]
driver = d6, UlSata.sys, UlSata
dll = d6, ptipbm.dll
inf = d6, UlSata.inf
[HardwareIds.scsi.UlSata_net]
id = "PCI\VEN_105A&DEV_3373","UlSata"
[Config.UlSata]
value = "", Tag, REG_DWORD, 1
[Config.fasttx2k]
value = "", Tag, REG_DWORD, 10 -
Ok, let me see if I get this right, I:
1. Download the kit from the bottom of the first post.
2. Extract the ".**_ " files to the XPCD\i386 folder.
3. Put the termsrv.reg file in my XPCD\$OEM$\$1\Install folder
4. Call the termsrv.reg file in my CMDLINES.TXT file at the end of the installations.
This would be correct for doing it as an Unattended Setup from CD, correct? This would also keep me from having to place these files in my XPCD\$OEM$\$$\System32 and ~\System32\dllcache folder correct? If this is so, I am going to make an installer that will place these files where they need to go on an UXPCD, so next time I wont have to guess at it.
0 -
Thanks, now to grow another brain cell so I can learn this RunOnceEx or GuiRunOnce method
0 -
Thanks. Gonna try it in cmdlines first though, don't wanna confuse my braincell anymore than I have to @m...
0 -
@RyanVM,
I am assuming that I wont need to use any switches with your program and can call it from cmdlines.txt? Also, I would like to say thanks for pointing me to the right place to obtain your .net1.1 file as well, it's saving me some space and time.
0 -
Thanks, that will work doing it that way I can put it all in a folder on my UXPCD and call it from cmdlines.txt I take it?
0 -
Has anyone incorporated PLUS! for XP into an UXPCD? I have PLUS! and was thinking about incorporating it into one of my UXPCD's but I am unsure of how to do it. I tried to obtain an .iss file without any luck and I don't have any way of tracking my installations, even if I did, I am not sure how to use them as I have tried before without any luck with them. If it's possible to set up a UXPCD to do the PLUS! as a seperate disk without actually using a second disk would be a plus. Even putting it in $OEM$\Install\Apps would be sufficiant as long as I can call it after I have booted into XP and not having it forcably installed on each machine. I did my exahustive search for doing this without any luck, TIA for any assistance.
0 -
This may help, it helped me when I first started learning how to network: Introduction to Networking
Keep in mind I have not looked this over in a couple years, and not sure if what your looking for exactly is in there, but also, I used, (and sometimes still do,) Broadband Reports
HTH
No body even uses netbios anymore. IPx/SPX is for Novell, I seriously doubt that anyone is running a novell server @ home.I do, it helps keep my network secure. (Not running a server though, just using IPX/SPX.) Though I am having some problems on how to utilize this with my Apple Mac based laptop as well at the current moment, without the use of a third party utility. I should mention that some games use this when connecting together on a lan for lan based gaming, such as with Quake 2.
Also, Bi0haZarD, I have to question your use of two Wireless Lans? Why is it necessary, just having the one should be sufficiant. If your using a Router with a WAP, then I can concieve it, but if your using two Routers, one with wireless, then just remove the non-wireless one, unless you really have a need for it, (to seperate a buisness from the home for example, which you shouldn't have a need to see anyways,) as your Wireless Gateway/Router should have a few, (usually at least 4,) ports for hardwire use if needed.
0 -
DisabledTrucker
That's really weird. I'm not an expert so I can't comment on M$ techies but I recall a friend of mine managing some 15 computers with XPs . Each time he had to reinstall, he used the same key for any of the computers. I know he had a legit license so maybe it was a Corporate license and key, which may work differently from XP professional and home , not to mention Win TE and MCE.
Not being sure how they do it, but from what I was told from M$ the keys that are attached to the sides of the case from HP wont work with say an OEM disk that you can purchase from New Egg for example, so unless he was using a new key, or one that was from his MSDN account, then I am unsure how he was able to do it, to a system such as HP/Compaq. For those which have OEM disks such as you can purchase from New Egg included with their systems, using their key attached to the side of their cases, shouldn't have been any different than using one of his from his MSDN account.
They figure the "legit" user wouldn't care one way or another and wouldn't want to "personalize" their system beyond what the manufacturer has already done. Furthermore, they can't and don't control how the manufacturer supplies the files to restore the system, and from what they told me was that different compainies have "different licenses" which allow them to do it different ways.Anyway it doesn't seem too fair selling a computer without the possibility to reinstall and personalize the system (unless you don't care spending an afternoon doing stupid things like launching installation programs, typing keys in, and of course getting rid of bad OEM software in your laptop). If M$ does all this for piracy prevention, it does pop up to everyone's eyes that the sole person who they put in trouble is the legit user.Apparently companies such as HP/Compaq, get around the How To Tell (see also attached file,) by putting everything on a restore partition on your hard drive.
But if your HDD becomes corrupted you have nothing else to resort to when you replace it. HP/Compaq says that you should send your entire computer back to them and it could take up to 4 weeks for you to get it back, when all it was is a defective hdd, to replace the hdd along with the software. They will reblast a hdd for you and put it in, or at their descrepancy send you a new computer altogether.
That for me poses a problem, because if I have a p.o.s. hdd, I am going to ship it back to the manufacturer, and they aren't going to have the O/S to reinstall on it, which leaves it to me. So HP/Compaq, will for another fee send you disks that they, (didn't when I got my computer mention,) say you are responsible for not only providing, but doing yourself the copy of the restoration disks from a utility which, either isn't or barely, documented outside of their website. Someone who is in need of this information, isn't going to look for it untill it is needed, then you have to hunt it down through multiple searches to find it.
HP/Compaq feel if you want a copy of these M$ softwares on CD you'll either provide your own disks and use their utility to perform a "backup" of their system, or you can pay them, (about $20 U.S.,) for a copy of them. Which is a complete violation of M$ own policy, as M$ specifically states, that when a purchaser buys a computer that has M$ Windows "blasted" on it, it has to come with the actual CD's to replace that software with if it's destroyed on the HDD for whatever reason. HP/Compaq has since modified their installations so that now it tells you to start with to provide 7-8 CD's to copy this before it will let you into Windows.
But that still is not what it says on M$ website, that they are the ones responsible for providing the actual CD's that they used to burn it with to begin with. This is something HP/Compaq cannot do apparently because they only have a "few" copies of the original disks and modify it's installation to "suit them" so they cannot provide the individual owner with these disks.
So to me, the individual owner is screwed, unless they either return the entire computer and seek one elsewhere, go out and buy, (at full cost, around $200-300 U.S.) the full version again, or do as they say and live with it. Mind you, if you go the route of buying again the full version of M$ windows, your HP/Compaq's warranty is void and you have to do all the customizing yourself, along with attempting to find the non-existant to barely locatable drivers that your computer will need to install the O/S back.
Since your comptuer is an HP/Compaq, (for example of course,) your not going to get the actual manufacturer of the hardware to help you because HP/Compaq even screws around with the hardware to where the actual drivers from the actual manufacturer of the hardware wont work or wont work correctly, so you will need drivers from HP/Compaq to get it to work, which they wont provide unless you either pay extra for them or you somehow modify the drivers they initially shipped with their products to work.
That said, I think there should be a way out. First, anyone can suggest what l should look for in the TabletPC OEM recovery CD in order to slipstreaming it into a WinXP Corporate CD?Thank you in advance - gionames
I give you some advice in my previous post, but beyond that your on your own, unless someone is willing to allow for me to download from them an .ISO with the disk 2 from both MCE and Tablet for purposes of researching this. Yes, I do have an HP MCE, but I don't have the Disk 1 & 2 from M$, mines all in a "recovery set" that I got from HP to restore my system. It would take me a few days or so, but I believe I could debug it and figure out what it would take to produce a single CD/DVD to do what he is asking.
0 -
then a look here: Windows Movie Maker 2.1 Download says,Microsoft Windows Movie Maker 2.1 is included in Windows XP Service Pack 2 (SP2).This means that when you update to SP2, you'll get new security fixes, increased compatibility with other video and audio programs, and improved stability for Windows Movie Maker.
*Edited for content.*System RequirementsHere's what you'll need to use Windows Movie Maker 2.1.
Component Requirement Recommendation
...
Operating System
SP2 for Windows XP Home Edition or Windows XP Professional
Therefore one can only assume that it's not part of a download but an inclusion in Windows XP SP2, which is the only way it can be obtained at this time.
0 -
After i installed SP2 i get the following error:
Windows could not start because the following file is missing or corrupt:
System32\drivers\Ntfs.sys
What i tried to do is go and reformat and start from scratch again, but unfortunantly now that this file is missing my computer wont detect my hard drives as connected. ive tried re connecting them and booting up with a cd but that hasnt worked either, i could only assume that its not registering or doesnt have my RAID drivers installed and thats why its not recognizing the hard drives. Any one have any insite ?
It sounds to me like you have one of two problems,
1. Your hard drives are failing and need replaced.
2. You have corrupted the hard drives and need to completely reformat them.
My solutions:
- Unplug all other drives first, except the one your needing to put the O/S on.
- Go to whomever makes your hard drives and look for their utility that will allow for you to format their drives, most times it will also have a drive test utility built in, if not grab it as well.
- Download it, copy it per their directions to floppy, then start with the drive you need to load XP on, and wipe it.
- Once you have it wiped, try running it's test on the drive as well. If that works then continue the following steps otherwise go on down to final suggestion.
Now I am assuming it has passed the test, wipe it once more before reinstalling XP on it. Once you have booted into XP and are sure that everything is fine and stable, then try attaching one drive at a time until you either have:
A: found the one causing the problem,
B: can look at all the connected drives in Computer Management/Disk Manager.
Either way you should back up your important info from the other drives and shut off the computer, disconnect the hard drive with your O/S on it, and format those drives using their utilities, test them and reformat them again before using them any more. Make sure to reconnect your O/S hdd back before rebooting after these tests/formats and making sure the floppy isn't in the drive anymore. Do the O/S drive first, then reconnect the others back.
*Final Suggestion*
If none of these work then you obviously have a bad drive, contact your drive manufacturer if it's still in warranty and have them cross ship you a new one.
One final suggestion, check your mobo manufacturers website and make sure you have the updated bios for your mobo, if not download and install it via floppy as well, prior to doing any of the formatting/testing.
0 - Unplug all other drives first, except the one your needing to put the O/S on.
-
Thanks.
Right now, I know that the external driver cannot be installed WinXP Pro.
Because I always try to install WinXP Pro. in the external driver.
That 's why I cannot sucessfully install it.
Let me get this straight, you want to install Windows XP Pro on a firewire/usb type of HDD? I am not all to sure you can do that.
0 -
*Edited for content* the nice thing with dell if u break it, they pay for it within the warranty period. *edited*
Most reputible computer manufacturers have a warranty that will allow for replacement of their computers, some are just longer than others. Dell is not the only one with this kind of replacement policy, some you have to pay extra for this others comes with it. Just look when making a choice, if that is important to you. For that matter an Apple has the same type of warranty for example.
The difference between Dell, HP/Compaq, Gateway, Alienware, and most of the others I metioned is that the ones I just directly mentioned are propietary systems and usually don't come with the O/S on a disk such as you can purchase from New Egg for example, they have a different set up they use where you will need several disks to reinstall their systems, as their computers come with the O/S in a partition on the hard drive, not the best way at all to obtain a copy it.
The rest give you the OEM/Full disk from M$ like the disks that you can purchase from New Egg. Some of them even include the actual full version (colored non-oem boxed version,) of the software, dependant on the company purchased from and how purchased. Some over the phone orders from companies will get you the actual full versions instead of the OEM versions if you speak with an actual person when ordering from some of the companies I mentioned.
Keep in mind when your looking at the computers, if it actually includes the M$ OEM/Full version disks or not when purchasing, something neither HP/Compaq nor Alienware include with their systems. The best advice I can suggest is to find a company that has a great reseller rating and go from there.
Just because a company, (M$, HP/Compaq, Dell, etc,) have the larger base of customers doesn't make them better companies to go with. In HP's case, they have been around almost since the begginning of personal computers, that doesn't in any way make them better, same for the rest. What you really want to look for are complaints about tech support, and return policies, as well as customer support of their products. From what I have gathered from the past few months of research, the best ones to buy from are Cyberpower, Monarch, and the more expensive ones. The more expensive ones are more geared for the enthusiast market, which I assume your not a part of, at least not yet, and would have no use for these more extravagant solutions, unless you have the money to just blow on them for prosterity reasons.
In extravagant I am referring to custom cooling solutions, custom cases with or without extreme paint jobs some of which rival those on a Rolls Royce, also they do custom installations as well. Most any custom computer manufacturer will do these customizations if you call them for fee's, but the ones I mentioned such as Voodoo and Falcon NW do them on a more frequent basis, which is why you'd pay more for them. Mostly people who want and can afford the best, who want someone else to build their system, and also want not only the prestige of ownership, but also the most top of the line computing solution for gaming/customizations go for one of these more extravagant solutions. I probably went over your head here, but that is what I am meaning by extravagant.
Going beyond all this, $ 4 $, you will do just as good getting a Cyberpower or Monarch system as you would getting a system from Falcon NW, without all the fancy and expensive customizations and it will come with the software on an OEM cd just as if you went to New Egg to purchase it. And I believe you will be happier in the long run.
0
VPC Win XP Pro SP2 On Mac
in Unattended Windows 2000/XP/2003
Posted
I was curious because I didn't know if my Key from my OEM version from my Mac VPC, will work with my slipstream of XP with SP-2 disk which isn't made from the one which comes with my Mac VPC, it's made from my retail version.