Hi,
> if you are willing to test it, I will commit it but please report back
> so I know that we are in a good shape
Ok, I've tested this a little further and would like to report all my findings
in one batch. This report again is not limited to bugs within the driverscan
code bits but all the bugs I found during testing.
By default $u->{'_meta'}->{'ntinstall_cmd'} is set to 'nt5x-install'.
Using nothing but what currently in the repository I got the following errors:
Unable to open /tmp/dhcp.out: No such file or directory at /z/dosbin/install.pl
line 1014.
Use of uninitialized value in concatenation (.) or string at
/z/dosbin/install.pl line 1157.
Use of uninitialized value in substitution (s///) at /z/dosbin/install.pl line
833.
Use of uninitialized value in string eq at /z/dosbin/install.pl line 834.
Use of uninitialized value in pattern match (m//) at /z/dosbin/install.pl line
727.
Use of uninitialized value in pattern match (m//) at /z/dosbin/install.pl line
727.
Use of uninitialized value in pattern match (m//) at /z/dosbin/install.pl line
727.
Use of uninitialized value in pattern match (m//) at /z/dosbin/install.pl line
727.
Use of uninitialized value in string ne at /z/dosbin/install.pl line 1821.
After quite some work I finally got everything to work and also fixed all the
"Use of unitialized value" errors that prevented the driverscan script from
working.
There are however still a few of them which I wasn't able to fix.
Unable to open /tmp/dhcp.out: No such file or directory at /z/dosbin/install.pl
line 1014.
Use of uninitialized value in concatenation (.) or string at
/z/dosbin/install.pl line 1157.
Use of uninitialized value in pattern match (m//) at /z/dosbin/install.pl line
727.
Use of uninitialized value in pattern match (m//) at /z/dosbin/install.pl line
727.
Use of uninitialized value in pattern match (m//) at /z/dosbin/install.pl line
727.
Use of uninitialized value in pattern match (m//) at /z/dosbin/install.pl line
727.
I really don't understand how this script could have ever worked before.
I had to replace the "ln -s" with a "cp -r" because it refused to create any
symlinks on /c/. Not to mention that those are completely useless? Windows
Setup wouldn't be able to access the drivers, no?
Using "cp" has the disadvantage that for every damn file we get a "Operation
not permitted" error message because the file permissions couldn't be kept. The
files are still copied fine.
So after applying the patch attached I think there is only one more major issue
to address. The usage of "cp" means that the system will exit and drop to shell
with a "out of memory" error if you try to copy a batch of drivers bigger than
the RAM in the machine.
And then there is the mis-detected hardware device...
# Unmatched devices: 6 devices
# - They do not match even without their SubSystem part
# - they might be handled directly by Windows or indirectly by the matching
drivers.
# unmatch: PCI\VEN_1106&DEV_3104&SUBSYS_72531462 (desc: 'VIA Technologies, Inc.
USB 2.0 (rev 86)')
# unmatch: PCI\VEN_1022&DEV_1100 (desc: 'Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] HyperTransport Technology Configuration')
# unmatch: PCI\VEN_1022&DEV_1101 (desc: 'Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] Address Map')
# unmatch: PCI\VEN_1022&DEV_1102 (desc: 'Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] DRAM Controller')
# unmatch: PCI\VEN_1022&DEV_1103 (desc: 'Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] Miscellaneous Control')
# unmatch: PCI\VEN_1106&DEV_3288&SUBSYS_32881106 (desc: 'VIA Technologies, Inc.
VIA High Definition Audio Controller (rev 10)')
Above is the tail of search-win-drivers.log from that machine. The "VIA High
Definition Audio Controller" is a little odd though... because it is actually a
"RealTek High Definition Audio Controller". No matching driver seems to be
included in any of the driverpacks.net packages. Copying the matching driver
into the win_drivers folder and updating the cache file didn't help either. The
driver works perfectly fine for this hardware when I add it to the
oempnpdriverspath myself.
So for now I have two places to store my drivers. One for auto-detection and
one for "copy this driver to the machine every time".
-
jens
p.s.: If you have questions about the patch, just ask. Also, if you apply the
patch and fix the other remaining error msg, give me a call and I'll test it
again. :)
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
unattended-devel mailing list
unattended-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-devel
