Hi,
I had the same problem with the intel PRO 100 nic driver being in
a path too deep for the win2k setup to copy to the local machine.
I got round this by moving the files up a directory and then editing
the inf file to point to the modified path.
Also I added the new path to the OEMPnPDriverPath in site\unattend.txt
so win2k setup should find it there as well.
I did seem to be getting a problem with Win2k finding a driver in Oem.inf
that it thought was a better match with the hardware but didn't work.
Win2k setup identified the hardware as a PRO 100Ve card but if i changed
the driver for the Pro 100 then everything worked ok.
Ed.
-----Original Message-----
From: Kerin Millar [mailto:[EMAIL PROTECTED]
Sent: 04 December 2004 19:28
To: [EMAIL PROTECTED]
Subject: [Unattended] Stuck: linuxboot crashes, dosboot not creating
required files
*** WARNING ***
This mail has originated outside your organization,
either from an external partner or the Global Internet.
Keep this in mind if you answer this message.
Hi, I'm a new user and first off I'd like to say thanks for an excellent
product. Conceptually, it seems to be a paragon of elegance and simplicity
and I really appreciate the use of Perl :)
Having said that, I've run into some problems off the bat as it were.
First, a quote from an earlier post:
> We have some reports that our DOS-based boot disk is having trouble
> creating files, especially with smartdrv enabled.
> I use the Linux-based disk, and installations of slipstreamed XP SP2
> (volume license media) works fine for me.
> So I suggest trying the Linux boot disk :-).
That's all well and good, but the Linux boot disk doesn't seem to be
reliable. I did experience success with the 4.4 release on a Compaq Evo
desktop. Well, it was successful except for the dreaded long pathname
issue when trying to access 3rd party drivers from the OS installation
source. Due to the packaging of Intel's 100VM network driver (a somewhat
critical component!) I still haven't worked out how to keep the path
length within bounds, so obviously it bailed out just after installing
Windows.
The next time I tried the boot disk (4.4b), I couldn't for the life of me
persuade it to obtain a DHCP lease (for some reason the allocation of a
lease from my ISC-DHCP server was taking longer than usual and the timeout
was too strict I believe).
Currently, I'm trying to get an installation going on a Compaq Presario
S7300UK workstation and the Linux boot disk simply reboots while loading
the kernel on the 4.5 bootdisk. I tried the 4.4b bootdisk (kernel 2.6.8.1)
and the result was the same. I then tried using the DOS boot disk which
fared better initially. I then discovered, much to my chagrin, that I was
running into the same problem described in an earlier post on this list
(subject: [Unattended] WinXP Volume License CD). So obviously the
suggestion to use a Linux boot disk is out of the question :(
My usual approach with problematic Linux boot disks is to try feeding a
few custom parameters to the kernel (noapic and nolapic for instance) but,
as far as I can tell, it's not possible with the stock linuxboot images
provided.
I'm aware that I could attempt to build a custom boot disk, rolling out a
custom kernel and such. The issue for me is a matter of time, and whether
the improvments merit a possible revision or whether it's just so much
glue to try and get it to work on one particular box (during which time I
could have installed by hand ;). I think the mainstream Linux kernels are
slightly problematic these days (2.6.9 has caused me no end of issues in
particular; I have started using -ac branches) and that it can be pretty
tough to get a Linux bootdisk with a kernel that works reliably and
consistently on various boxes.
I suppose my point is that having a well supported DOS bootdisk is quite
important IMHO, even if using Linux is cooler. I'm not sure at which stage
the biosinfo.inf file is written. If it is near the end then perhaps it is
the write-caching feature of smartdrv that is causing a problem. A quick
test reveals that Microsoft are quite right, disabling write-caching makes
the initial install phase of Windows agnosingly slow.
Right now I'm stuck. I might try and "roll my own" as time permits but,
aside from that, is there anything I can do to help determine why the
kernel on the linuxboot disk is flaking out or to acquire more insights
into why dosboot is having trouble creating files?
Regards,
--Kerin Millar
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info
