On Wed, 2004-04-07 at 23:30, Jordan Share wrote:
> A couple of bugs:
> 
> First, some of the directories under "os" have long filenames.  This is 
> fine with the dos boot disk, presumably because it mangles them the same 
> for winnt as it does for install.pl.
> 
> Under linux, though, the initial installer gets told to copy files from 
> "win2kServer", which doesn't work in dosemu.
> 
> ----
> 
> Another problem I'm running into is when it tries to copy my driver 
> files over.
> 
> I am getting the error:
> 
> Setup was unable to copy the following file:
> 
> IA32
> 
> o press ENTER to retry the copy operation
> [ etc. ]
> 
> I did a find in the os directory and this is the only hit:
> ./win2ksp4/I386/$oem$/$1/drivers/shuttle/LAN/Windows/Drivers/IA32
> 
> (IA32 is a directory)
> 
> I don't see anything immediatly wrong with this path, here's part of a 
> tree from  the shuttle directory:
> |-- LAN
> |   |-- CBCombo.exe
> |   |-- DIAG1000.EXE
> |   |-- Windows
> |   |   `-- Drivers
> |   |       `-- IA32
> |   |           |-- E1000NT5.SYS
> |   |           |-- Net82557.din
> |   |           |-- PROUnstl.exe
> |   |           |-- e100b325.sys
> |   |           |-- e100bnt5.sys
> |   |           |-- intelnic.dll
> |   |           `-- net8254x.din
> |   |-- diag100.exe
> |   |-- e1000.cat
> |   |-- e100bw2k.cat
> |   |-- net8254x.inf
> |   |-- neti557x.inf
> |   `-- verfile.tic
> |-- USB2
> |   |-- hccoin.dll
> |   |-- symbols
> |   |   |-- usbehci.pdb
> |   |   |-- usbhub20.pdb
> |   |   `-- usbport.pdb
> |   |-- usb2.inf
> |   |-- usbehci.sys
> |   |-- usbhub20.sys
> |   `-- usbport.sys
> 

I had this also but with another directory. The problem was that i
copied the files as root-user and did a chmod -x including the
directories (Stupid me). Are you sure it is at least 755 and the user is
the one you're samba server is accessing it with?

(I assume here you are using a Linux box with samba, but it should apply
to other situations too) 

> IA32 is the only one it complains about.  Perhaps it is too deep?
> 
> ----
> 
> When it first detects the drive (a 160gig drive), I get various errors 
> in the style of:
> Odd.  C/H/S does not multiply out to 312581808.
> 
> Setting C/H/S for hda to 19457/255/63...done.
> 
> The boot output is:
> hda: ST3160021A, ATA DISK drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> hda: max request size: 1024KiB
> hda: 312581808 sectors (160041 MB) w/2048KiB Cache, CHS=19457/255/63, 
> UDMA(100)
>   hda: hda1
> 
> These CHS values do not correspond to what the BIOS thinks the drive is.
> 
> Here's the BIOS settings, and what it ends up with for C/H/S with each 
> of them:
> 
> CHS -- 65535/16/255
> LBA -- 16643/255/63
> Large -- 4095/240/255
> Auto -- 65535/16/255  (same as CHS)
> 
> This might be related to the next problem...
> 
> ----
> Finally, (after skipping the copy of IA32), It reboots and I end up with:
> Setup cannot find the temporary installation files.
> 
> The hard drive on which Setup placed temporary files is not
> currently available to Windows 2000.  You may need a
> ...
> [ snip ]
> 
> ----
> 
> Thoughts?
> 
> Jordan
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> unattended-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/unattended-devel



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
unattended-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-devel

Reply via email to