:) Tövis, it is not me, how tries to find solution ;) > Hi!
> Your posts luck of any clues. Give us some log, where is the process stuck. > The boot process is well written at syslinux wiki. Unattended starts after > booting the memdisk (for tftpboot) and starts the "master" bash script, > which is also well readable ... > Testing the RIP Linux PXE boot suggest that you have some problems around > mounting cifs //ntinstall/install - may be not. > Best regards > tovis >> hello >> >> really sorry to say this, but for me the only thing was to obtain the >> driver for the windows machine since the linux the unattended (4.8) >> used to boot and prepare the installation was able to initiate >> network. no i tried to reach that person for whom i installed his >> eeeeeepc (sorry, i dont really like them), but he cannot be able to >> come and bring his computer for me to investigate. the only reason for >> your problem can be a slight difference in the network adapter. as far >> as i remember they were the same model, but manufacturer can have two >> or more option for network cards. especially on different locations of >> distribution. so... who knows. maybe it is an ugly thing for only one >> computer, but try to install or run a live linux onto that machine and >> experiment with the network modules to see the difference. maybe you >> can have an init option as workaround. keep trying! >> >>> FwdTmp - can you explain me the process you adopted a little further? ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
