Jump to content

The-VOICE

Member
  • Posts

    35
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by The-VOICE

  1. A multi-platform image is a quicker deployment than an unattended install. Once you get the all of the MSD (Mass Storage Device) drivers and PnP drivers injected/pre-installed, the tricky part is allowing for multiple HAL's (Hardware Abstraction Layer). It can be done, and it does work, but don't expect Microsoft to support it in the current version of Sysprep. You'll have to go outside the Microsoft utilities to make it happen.

  2. My understanding is that VBScript isn't supported on Windows x64 Edition. What little information I could find on the subject when I was in a similar situation a few months ago was that VBScript was considered a 'legacy' technology by Microsoft.

    I was able to accomplish what I needed by rewriting my scripts in AutoIt.

    Forgive my ignorance, but do x86 printer drivers work in Windows x64?

    Oh, and welcome to MSFN! :)

  3. But while Booting it says something like Silicon 3114 controller then the name of my Hardrive.

    The Silicon Image 3114 controller is only SATA, not SATA-II. Perhaps you have the drive connected to the wrong port?

    According to the driver list from the link you provided, I would guess that you need to connect your hard drive to one of the Nvidia CK804 ports, not the Silicon Image 3114 ports, for compatibility with SATA-II. Make the floppy disk containing the 'F6' driver, and provide it when prompted by Windows during installation.

    BTW, I looked at your speed test. A STR (sustained transfer rate) of 60MB/s is good performance for a single 7200RPM drive. If you want it to be faster, you'll need to add more drives in a RAID-0, RAID-1, or RAID-10 configuration. I wouldn't recommend RAID-5 because you would need a true hardware array controller with its own XOR processor so as not to overutilize your desktop CPU.

    For what it's worth, I have an Asus P5AD2 Premium mobo which has both the Silicon Image 3114 array controller and Intel Matrix RAID. At least in the case of the P5AD2, the Sil3114 is connected to the PCI bus, and the Intel Matrix RAID is connected to the PCIe bus. If you have a choice with your mobo, choose the array controller which is connected to the PCIe bus for faster throughput and lower CPU utilization.

  4. It doesn't sound like you have a hardware problem. More than likely you have one or both of the following two issues.

    1) A mismatched setting between the BIOS setting(s) for ACPI and/or APIC when used with a PlugAndPlay Operating System (Windows 2000).

    2) An older version of the BIOS which may not properly support the P4.

    The latest revision for the mainboard is 2003-07-22:

    http://www.abit-usa.com/downloads/bios/bio...ries=1&model=35

    Please consider re-flashing the BIOS and resetting to BIOS setup defaults.

  5. I've read that you can easily tunnel RDP (Remote Desktop Protocol) over SSH (Secure Shell).

    I considered tunnelling VNC (Virtual Network Computing) over SSH for use with my Pocket PC Phone (Samsung I700) because the Terminal Services client on Windows Mobile 2003 Phone Edition is so poor. Currently, I'm happily using pcAnywhere Mobile, but I'd still like to try the VNC/SSH combo.

  6. see i told u lite-on wasnt all that good for dvd's

    I, myself, have a Lite-On CD-RW drive and a Lite-On DVD±RW drive among others. I have been very satisfied with both drives so much so that I purchased another Lite-On DVD±RW drive for another machine. I've had numerous brands/models of optical drives over the years, and Lite-On is the only one that has inspired any sense of brand loyalty in me.

    I must admit I'm a little confused by the bashing of Lite-On DVD±RW drives when in the same sentence folks will claim that a Sony is tops. I do remember reading from a reputable review site that some Sony drives were simply rebranded Lite-On's. What I don't remember is whether that comment was in regards to a CD-RW drive or a DVD±RW drive. Can anyone please clarify this? Does Sony release updated firmware more frequently than Lite-On to adapt the writer to new media?

    I realize that a successful burn requires a good relationship or level of compatibility among drive, drive firmware, and media. In my opinion this compatibility seems to be far more an issue with DVD±R media than it ever was with CD-R media. Are others seeing a different result?

    Like many people I am a bargain hunter and watch the advertisements for sales/rebates of media. For the most part I've found that I can get the cheapest DVD+R media at Office Max after a rebate. Usually this means that it will be Spin-X or KHypermedia. The Spin-X does not meet maximum error requirements to even be labeled a DVD+R, and the KHypermedia is hit or miss. Recently, I decided to up the money I was willing to spend on media and tried TDK 8x PrintOn DVD+R I found at a price club, Costco. The TDK's are excellent with a minimal error rate. Oh well, you get what you pay for is right.

    Correction: I have several spindles of the TDK 8x PrintOn DVD+R's. It seems that these are actually rebranded from two manufacturers, MBI from India and CMC from Taiwan. The MBI's are excellent, but the CMC's are on the border of quality (as can be expected from CMC). The country of origin is the easiest way to tell these apart on the spindle label. The CMC's are going to be returned, today.

    Correction to Correction: The MBI's are excellent at 8x, but the error rate increases a bit when written at 4x. The CMC's are the opposite. The CMC's are excellent at 4x, but when written 8x the quality is marginal. I suppose I'll keep the CMC's after all. I just have to remember to burn them at 4x. Geez, does this have to be so complicated!?! :}

    I've found this to be very useful in determining test techniques and media recommendations:

    http://www.xbitlabs.com/articles/storage/d.../dvd-discs.html

  7. well to let u know i did get it, and lightscribe is only for HP drives, and its not all that good anyways, it fades after a while and can damage the disc

    LaCie is another brand providing LightScribe.

    I had a feeling that LightScribe was a poor idea from the start, but you're the first person I've met to actually try it. May I ask if you were using the expensive LightScribe-compatible CD-R media when you noticed that it faded and/or damaged the disc?

    Any information is appreciated.

  8. I work in a large enterprise environment. In addition to the Dell's, I also have the following HP models: DL380 G2, DL380 G3, DL380 G4, DL580 G2, DL760, DL760 G2, ML370 G3, ML370 G4, ML530 G2, and ML570 G2. Any day now I'm expecting the DL580 G3 and ML570 G3.

    Yes, only HP systems management from the PSP (ProLiant Support Pack) v7.30 is supported for Windows Server 2003 with Service Pack 1. v7.20 was a beta for development use only.

    I took a freshly installed server sysprepped with Windows Server 2003 slipstreamed with Service Pack 1. Windows Firewall, DEP, etcetera are disabled. I installed PSP v7.10. I took a quick glance in the systems management homepage and found two issues.

    1) The systems management homepage could no longer recognize the model of server.

    2) The IML (Integrated Management Log) could no longer be viewed.

    At this point I just waited for the release of PSP v7.30.

    When PSP v7.30 was released, I downloaded and installed the firmware dependencies. I integrated the latest drivers into the Sysprep build. I configured the configurable PSP v7.30 executables with the environment-specific SNMP strings, Insight Manager / Repository console, etcetera.

    I re-sysprepped the server and confirmed that the new drivers were installing correctly on a slipstreamed Windows Server 2003 with SP1. All was well. I rebooted the server, installed PSP v7.30, and rebooted.

    I took this Sysprep image and tested it on most of the models listed above. So far I've found three issues with PSP v7.30 on Windows Server 2003 with SP1:

    1) The latest iLO firmware v1.75 causes a problem with models with an iLO (Integrated Lights-Out).

    2) I've seen the IML report errors correctly, but for some inexplicable reason the time will be off stating AM instead of PM. 24-hour military time is set correctly from the RBSU (ROM-Based Setup Utility), and Windows time is set correctly. I know it's an HP issue because the same errors appear in the Windows system log, but with the correct AM/PM time.

    3) In one situation that I've been unable to reproduce, HPSMHD.EXE, the system management homepage, generated application errors after every reboot.

    Yell if you need more details.

  9. Now if  only Dell would get their act together on their OpenManage software...

    Agreed! First Dell said that an SP1-compatible OpenDamage / OpenMangle would be available late May, but recently stated that it would be a June timeframe.

    HP's SP1-compatible ProLiant Support Pack v7.30 released over a week ago, but I've already found some issues with it and reported them to HP.

    Oh well...ya get what ya pay for. I have both Dell and HP to contend with. :}

  10. First, i want to thank everyone for thier examples, ideas and help here.  I've managed to get the beginnings of an XP install working with the help.

    I've run into a problem with the mass storage/RAID drivers in Text Mode setup of XP.  I think it's an easy fix, but I'm just not sure where to look now.

    I have an XP setup that has the drivers for a Promise FastTrak ATA RAID card slipstreamed in (using XPCreate to do the job).  Anyway, the WinPE portion works like a charm, but after it reboots into the XP install, setup halts when it cannot find the FastTrak.sys driver.

    The driver is sitting compressed (.SY_) in the I386 folder of the XP files.  I thought that I might just need to copy the uncompressed file there as well, but when I tested this in VirtualPC I fired it up using a basic WinPE disk and found that the compressed driver wasn't in the $WIN_NT$.~BT folder on the hard drive like I thought it would be.  Even if I put the uncompressed one in I386, it doesn't look like it's going to be copied over anyway.

    So, now I'm confused.  How can I get the driver to load, if setup didn't copy it to the hard drive?  The drivers work when I just use my original unattended CD, so I don't get why it isn't working now.

    Where am I going wrong?

    I, too, have had some issues with the Promise FastTrak100 RAID Controller. Take a look at Promise's TXTSETUP.OEM. Notice the folders where each different OS's drivers are stored. Keep to a consistent folder structure, and I think you'll figure it out.

    Snippet from TXTSETUP.OEM:

    [Disks]

    d1 = "Promise FastTrak Family Driver Diskette", \fasttrak, \

    d2 = "Promise FastTrak Family Driver Diskette", \fasttrak, \nt4

    d3 = "Promise FastTrak Family Driver Diskette", \fasttrak, \Win2000

    d4 = "Promise FastTrak Family Driver Diskette", \fasttrak, \WinXP

    P.S. Don't forget the tagfile "FASTTRAK" with no file extension.

  11. Have you confirmed the hardware ID's match those in your SysprepMassStorage section?

    Do any of the P4's have HyperThreading?

    When you perform a manual Windows installation, which ACPI does Windows select? You can view this in Device Manager -> Computer.

    The simplest answer for having a single image that works across multiple HAL's is to use the least common denominator hardware and upgrade the HAL before, during, or after Sysprep (it depends).

    Answer those, and we'll go from there.

×
×
  • Create New...