bj-kaiser

in the end I used WPS, since I now have a router that supports this. keying in a 10+ character password on printer just with the cursor keys is no fun. If it at least had a Web-Interface I could have used the unencrypted ad-hoc network to do the setup. but no. and the Software Epson provided did for some reason not recognize it. For short, I wouldn't recommend that thing.

Hey, I'm trying to find a way to configure the WiFI settings of my new Epson SX430W through my PC. Epson advertises it with "automatic wifi setup with windows 7" etc. but I can't figure out how. All I managed so far is join it to an ad hoc network, I can reach the MFP through HTTP and SMB, but EpsonNet Setup doesn't find it. to bad it has no web-interface, all I get when I connect to it with my Browser is "Epson Stylus SX430". And I really don't like the idea of keying in a rather secure WiFi-passphrase with the cursor keys on that cheap thing. any idea/hint appreciated.

Those three ACPI HALs should be easy to get to work. Your first idea is exactly the way how it worked for me, just build the image on a PC or in a VM supporting the ACPI PC HAL. Sysprep / Plug'n'Pray does the rest, no special sysprep.inf settings needed.

I would like to add something here for people having the same problem as the original author of this thread. I dont see why a NAS is neccessarily slow. It depends on the hardware and personally I have this one: http://www.intel.com/design/servers/storage/ss4200/ In some reviews it scored transfer speeds of up to 40 Mb/s. While that isnt much and not even close to theoretical (100 Mb/s) and practical (70 - 80 Mb/s) limits in a gigabit network, it seems to be decent. currently it is running on FreeBSD with a ZFS mirror setup of 2 320 GB Enterprise SATA HDDs. Transferring a file of 2GB, which is definitely bigger than the system RAM, over FTP i got 9 Mb/s when the client was on 100 MB/s Ethernet. Then I tried gigabit ethernet, as both the NAS and my client PC have it. Result: 15 Mb/s FTP. Since the NAS system itself has scored better in reviews on tomshardware and other sites, I guess I have some sort of bottleneck. I am suspecting my clients 2.5" hdd here.

Errrm... is it just me or is PowerShell not really available in WinPE? (because of .NET)

All I can do is give you some links: http://technet.microsoft.com/en-us/library/cc748957%28WS.10%29.aspx http://technet.microsoft.com/en-us/library/cc766103%28WS.10%29.aspx http://technet.microsoft.com/en-us/library/dd744535%28WS.10%29.aspx BTW: All of this is in the CHMs coming with the WAIK. I guess thats most of the points where you can hook into the installation system, or at least the points where you are intended to do so. We haven't yet started deploying Windows 7 or the likes here, XP SP3 is still going strong.

1) there should be entry points in the setup phases of windows into which you can hook with custom scripts (read the WAIK docs for that) There should be a chapter about Windows Setup stages. also, there should be a wget build for windows too, or at least a similar tool. 2.) there are Syslog agents for Windows, I guess you could find one that runs on WinPE http://www.correlog.com/purchase/download-windows-agent-form.html

ok, now I'm curious, where is the documentation on that one?

http://www.autoitscript.com/autoit3/docs/functions/SplashImageOn.htm

ok, so I found a solution to this issue. apparently, windows 7 starter (as in the configuration I got with my EEEPC) will not resolve names without a domain through DNS. so a name like "beastie" won't resolve, except using nslookup. Instead of using DNS windows will try to resolve the name through WINS/workgroup. So a machine not running Windows file sharing or SAMBA won't resolve. the easiest solution to this seems to be to add a "." after the hostname which apparently forces windows to use DNS. "beastie." resolves, "beastie" doesnt.

errm... you got the help file with your AutoIt3 setup. also: http://www.autoitscript.com/autoit3/docs/functions/Send.htm

look into the documentation for "SendKeys" or "Send". HTH

long time since I had to ask a question, but I got a really stupid problem now. I got a BSD fileserver named "beastie". nslookup from my new Win 7 Starter netbook is ok, but I cant ping or connect to it with Putty/SSH or anything by the name. Despite that, I can reach it with the IP nslookup reports. I guess the clientname gets registered in the router, otherwise nslookup should fail. So why cant I reach the fileserver by name despite the fact that nslookup can resolve it?

I think the bootloader message together with your TFTP log is quite clear, isnt it? Something in the BCD file is wrong, as it can apparently load it and tell you that. And you never see the .wim getting requested from TFTP. so check your BCD config. "bcdedit /store BCDfile /enum" update: this is what a succesful boot of WinPE 2.0 looks like from the TFTP server side:

for all I know Windows 7 uses a system partition of some 200 MB or so for its boot files and Win RE. Also this way the system is prepared, if you ever want to use bitlocker, so you aren't forced to move the actual Windows installation partitio. This is because some parts of the system still have to be unencrypted, so you can boot the system.

I would recommend to read the docs again. this looks like a problem OemPreinstall="No"

The two links of you do not really help me. They describe how to use user/vendor classes to hand out different settings depending on the user/vendor class the DHCP client sends with its request. (example: hand out adresses of provisioning servers to IP phones and the like). This does not allow you to separate clients into different scopes/ip-ranges by user or vendor class. and on your iphone problem, take a look at your DHCP traffic with the network monitor and figure out if the iPhones send DHCP vendor class in their requests. My printer NICs apparently don't. And always remember, DHCP is a protocol from the good old times. you can always send a different vendor class if you can manipulate your DHCP client. So take that option of not handing them out IP adresses by blocking a certain vendor class with a grain of salt.

actually I would like to get around using reservations. if there was a possibility to filter for somelthing like "MAC adress begins with AA-BB-CC or AA-BB-DD" and limit the scope to that, that would be a great help. As right now the situation is that most of my printer NICs are from not more than 2 different manufacturers. (We got a pretty homogenous printer collection) edit: this looks interesting http://blogs.technet.com/teamdhcp/archive/...allout-dll.aspx

Here is a question to the experts: Is there any way to limit DHCP scopes to a certain type of device (in my case printers) by filtering MAC adresses or another property which is unique to a certain device type?

here's a cookie: label flash kernel memdisk initrd your_floppy_image you obviously have to get the memdisk module from the syslinux package. oh, and get the matching version to the bootloader. otherwise it will fail.

cool, i already have that from mounting DSL to a jump drive.... but would i package my DOS folder inside the syslinux directory and then compress to an .iso or have them in sperate directorys and then put both into one .iso? nope. youd need a floppy image with DOS (i prefer FreeDOS) and either a FAT(32) partition with your BIOS image and flash tool or you'd have to add the flashing tool and image to the floppy image. this could be helpful: http://www.ltr-data.se/opencode.html#ImDisk http://www.ibiblio.org/pub/micro/pc-stuff/...tributions/1.0/ (get fdboot.img from there and empty fdconfig.sys and just delete autoexec.bat)

cd or dvd boot: ISOLINUX from the SYSLINUX package and MEMDISK. you use the isolinux bootloader to load memdisk which then loads a floppy image to a virtual floppy drive in RAM and boots it. quite easy, isnt it?

Forgot to add, this is my case: http://www.mini-box.com/M350-universal-min...amp;category=87