• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About bj-kaiser

  • Birthday 12/20/1985

Profile Information

  • OS
    Windows 7 x86
  1. 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.
  2. 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.
  3. 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.
  4. 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: 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.
  5. Errrm... is it just me or is PowerShell not really available in WinPE? (because of .NET)
  6. All I can do is give you some links: 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.
  7. 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
  8. ok, now I'm curious, where is the documentation on that one?
  10. 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.
  11. errm... you got the help file with your AutoIt3 setup. also:
  12. look into the documentation for "SendKeys" or "Send". HTH
  13. 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?