<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Deploy Win2k3 using Scripting Toolkit Linux Edition? in ProLiant Deployment and Provisioning</title>
    <link>https://community.hpe.com/t5/proliant-deployment-and/deploy-win2k3-using-scripting-toolkit-linux-edition/m-p/3975621#M5012</link>
    <description>&lt;!--!*#--&gt;I'm not sure where the illegal OP code is coming from, though it could be from a mistake in the boot sector.&lt;BR /&gt;&lt;BR /&gt;The script has a line to correct the number of hidden sectors set by mkdosfs, the line starts with "echo -ne "\400" | dd". That line is setting the number of hidden sectors to 32, which is correct for most systems, but not all. Some systems report/use 64 sectors per track. DL380G4 w/ a P600 controller has that issue.&lt;BR /&gt;&lt;BR /&gt;I've also seen times when the hidden sectors are incorrect because sfdisk uses the existing partition information in the mbr when creating the new one. Add a sfdisk command to clear the partitions to work around that.&lt;BR /&gt;&lt;BR /&gt;When the # of hidden sectors is incorrect, the boot code cannot find the filesystem. It usually leaves you at a black screen, but could cause other issues.&lt;BR /&gt;&lt;BR /&gt;Using the NTLDR method requires a precise configuration of the filesystem, even if all the boot sectors are correct, it's really not well documented. &lt;BR /&gt;&lt;BR /&gt;Basically if you start a CD based install, then stop the install at the first reboot, copy all those files off. Those are what you'll need to make the NTLDR method work.&lt;BR /&gt;&lt;BR /&gt;After the script has prepared the partition, formatted it, made it bootable, copy those files down.&lt;BR /&gt;&lt;BR /&gt;I really recommend sticking with the FreeDOS method.</description>
    <pubDate>Thu, 28 Jun 2007 11:26:00 GMT</pubDate>
    <dc:creator>Chris Davenport</dc:creator>
    <dc:date>2007-06-28T11:26:00Z</dc:date>
    <item>
      <title>Deploy Win2k3 using Scripting Toolkit Linux Edition?</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/deploy-win2k3-using-scripting-toolkit-linux-edition/m-p/3975616#M5007</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;been a while since I've messed with the STK...and back then (~2+ years) everything was DOS.  WinPE is a &amp;amp;#@%&amp;amp; to get a hold of so I figure Linux is the way to go.  I've got everything working up to the point of creating the fat partition to drop the Win install files.  The sample script install_win.sh has a couple of lines where ntldr.bss and ntldr2.bss are referenced.  With the number of mistakes i found in these scripts i'm not sure if these are mistakes or if there are actually supposed to be two .bss files....regardless, the STK comes with one...freedos.bss.  What am I missing, i'm sure it's something trivial.&lt;BR /&gt;&lt;BR /&gt;Thanks!!</description>
      <pubDate>Wed, 04 Apr 2007 23:34:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/deploy-win2k3-using-scripting-toolkit-linux-edition/m-p/3975616#M5007</guid>
      <dc:creator>AlexF</dc:creator>
      <dc:date>2007-04-04T23:34:29Z</dc:date>
    </item>
    <item>
      <title>Re: Deploy Win2k3 using Scripting Toolkit Linux Edition?</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/deploy-win2k3-using-scripting-toolkit-linux-edition/m-p/3975617#M5008</link>
      <description>&lt;!--!*#--&gt;The .bss files are boot sectors. freedos.bss is the FreeDOS boot sector that can be used to create a DOS bootable filesystem.&lt;BR /&gt;&lt;BR /&gt;ntldr.bss and ntldr2.bss are the boot sectors used to perform NTLDR boots on a fat32 filesystem.&lt;BR /&gt;&lt;BR /&gt;They're not included in the toolkit because they belong to Microsoft. HP Includes a linux utility, "bootextract", that can extract those two boot sectors from ufat.dll, which you'll have to copy from Windows media or a running system.&lt;BR /&gt;&lt;BR /&gt;What other issues have you found? I'd like to get those addressed.</description>
      <pubDate>Fri, 06 Apr 2007 10:17:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/deploy-win2k3-using-scripting-toolkit-linux-edition/m-p/3975617#M5008</guid>
      <dc:creator>Chris Davenport</dc:creator>
      <dc:date>2007-04-06T10:17:28Z</dc:date>
    </item>
    <item>
      <title>Re: Deploy Win2k3 using Scripting Toolkit Linux Edition?</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/deploy-win2k3-using-scripting-toolkit-linux-edition/m-p/3975618#M5009</link>
      <description>Ah-hah...very helpful info.  All I'm trying to do is boot to DOS and kick off winnt.exe - in that case i would not require NTLDR, right?  So  using freedos.bss should be sufficient.  I'll see if I can't make that work.&lt;BR /&gt;&lt;BR /&gt;Thanks for your help.</description>
      <pubDate>Fri, 06 Apr 2007 12:26:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/deploy-win2k3-using-scripting-toolkit-linux-edition/m-p/3975618#M5009</guid>
      <dc:creator>AlexF</dc:creator>
      <dc:date>2007-04-06T12:26:29Z</dc:date>
    </item>
    <item>
      <title>Re: Deploy Win2k3 using Scripting Toolkit Linux Edition?</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/deploy-win2k3-using-scripting-toolkit-linux-edition/m-p/3975619#M5010</link>
      <description>got the ntldr and ntldr2 in there...now i'm getting an illegal OpCode error.  What else could i be missing?</description>
      <pubDate>Fri, 06 Apr 2007 18:44:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/deploy-win2k3-using-scripting-toolkit-linux-edition/m-p/3975619#M5010</guid>
      <dc:creator>AlexF</dc:creator>
      <dc:date>2007-04-06T18:44:42Z</dc:date>
    </item>
    <item>
      <title>Re: Deploy Win2k3 using Scripting Toolkit Linux Edition?</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/deploy-win2k3-using-scripting-toolkit-linux-edition/m-p/3975620#M5011</link>
      <description>So, i'm stuck at the red screen of death...Any insight on this??</description>
      <pubDate>Mon, 30 Apr 2007 21:32:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/deploy-win2k3-using-scripting-toolkit-linux-edition/m-p/3975620#M5011</guid>
      <dc:creator>AlexF</dc:creator>
      <dc:date>2007-04-30T21:32:05Z</dc:date>
    </item>
    <item>
      <title>Re: Deploy Win2k3 using Scripting Toolkit Linux Edition?</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/deploy-win2k3-using-scripting-toolkit-linux-edition/m-p/3975621#M5012</link>
      <description>&lt;!--!*#--&gt;I'm not sure where the illegal OP code is coming from, though it could be from a mistake in the boot sector.&lt;BR /&gt;&lt;BR /&gt;The script has a line to correct the number of hidden sectors set by mkdosfs, the line starts with "echo -ne "\400" | dd". That line is setting the number of hidden sectors to 32, which is correct for most systems, but not all. Some systems report/use 64 sectors per track. DL380G4 w/ a P600 controller has that issue.&lt;BR /&gt;&lt;BR /&gt;I've also seen times when the hidden sectors are incorrect because sfdisk uses the existing partition information in the mbr when creating the new one. Add a sfdisk command to clear the partitions to work around that.&lt;BR /&gt;&lt;BR /&gt;When the # of hidden sectors is incorrect, the boot code cannot find the filesystem. It usually leaves you at a black screen, but could cause other issues.&lt;BR /&gt;&lt;BR /&gt;Using the NTLDR method requires a precise configuration of the filesystem, even if all the boot sectors are correct, it's really not well documented. &lt;BR /&gt;&lt;BR /&gt;Basically if you start a CD based install, then stop the install at the first reboot, copy all those files off. Those are what you'll need to make the NTLDR method work.&lt;BR /&gt;&lt;BR /&gt;After the script has prepared the partition, formatted it, made it bootable, copy those files down.&lt;BR /&gt;&lt;BR /&gt;I really recommend sticking with the FreeDOS method.</description>
      <pubDate>Thu, 28 Jun 2007 11:26:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/deploy-win2k3-using-scripting-toolkit-linux-edition/m-p/3975621#M5012</guid>
      <dc:creator>Chris Davenport</dc:creator>
      <dc:date>2007-06-28T11:26:00Z</dc:date>
    </item>
  </channel>
</rss>

