[no subject]

It mostly works, but there are a few gotchas with regards to signed drivers,
and changes in the SCSI/IDE interfaces. Unfortunately the majority of my job
responsibilities are in maintaining this stuff.

PLENTY of resourse available online, though some will contradict each other.

For starters: <a  rel="nofollow" href="http://www.appdeploy.com";>http://www.appdeploy.com</a> and <a  rel="nofollow" href="http://microsoft.com";>http://microsoft.com</a>

bnm


On 9/21/05, Jeff Hubbs &lt;hbbs at comcast.net&gt; wrote:
&gt;
&gt; Back in my age of pre-enlightement, the rule of thumb was that disk
&gt; images made from one NT (or subsequent derivative) machine could be
&gt; installed on outwardly identical machines, but doing so was discouraged
&gt; because NT made installation decisions based on the hardware it saw at
&gt; install time and that small running changes (e.g., different rev level
&gt; within a mobo chipset) between outwardly identical machines would be
&gt; detected at install time and different binaries would go on disk, so as
&gt; to result in a deviation between the OS installed on an image-created
&gt; machine and the OS that would be there had it been installed on the
&gt; exact same unit. As a result, you could wind up with a machine that's
&gt; crash-happy and you'd never be able to figure out why.
&gt;
&gt; Does anyone know if this is still the case with current releases of
&gt; Windows OSses?
&gt;
&gt; As an aside, supposedly, Linux wasn't *as* susceptable to this because
&gt; you could make allowances at kernel-config-time and beyond that, the
&gt; kernel and modules would decide what they saw when they were first
&gt; invoked, particularly at boot time. In other words, if you compiled an
&gt; everything-but-the-kitchen-sink kernel and booted to it and/or started
&gt; the modules, they would sense rev-level issues and switch themselves
&gt; appropriately (such as the CMD640 IDE bug).
&gt;
&gt; As other people have, I ask here off-topically because of the general
&gt; sharp-cookie quotient.
&gt;
&gt; Jeff
&gt; _______________________________________________
&gt; Ale mailing list
&gt; Ale at ale.org
&gt; <a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
&gt;
-------------- next part --------------
An HTML attachment was scrubbed...



</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00469" href="msg00469.html">[ale] OT:  NT/XP/2K/2K3 Disk Imaging</a></strong>
<ul><li><em>From:</em> hbbs at comcast.net (Jeff Hubbs)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00470.html">[ale] OT:  NT/XP/2K/2K3 Disk Imaging</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00472.html">[ale] Sync a Palm Tungsten T5 with Linux</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00469.html">[ale] OT:  NT/XP/2K/2K3 Disk Imaging</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00470.html">[ale] OT:  NT/XP/2K/2K3 Disk Imaging</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00471"><strong>Date</strong></a></li>
<li><a href="threads.html#00471"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>