• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About RogueSpear

  • Rank
    trying to stay under the radar..
  • Birthday 08/16/1969

Profile Information

  • OS
    none specified
  • Country
  1. I've put together a package of scripts that do pretty much what you describe. It's an ongoing project I call the ScriptPack. You might find it to be useful.
  2. Something I found regarding VS2005.. when you slipstream SP1 into your install source there are several items which are not updated such as SQL Server 2005 and the PPC/WM device emulator. I have found that you can download these updated components from Microsoft and replace the old with the new. If I remember correctly, in the case of SQL, you need to rename the file you downloaded to match the older file. In the end this saves a fair amount of time and at least one reboot.
  3. I didn't notice it mentioned in this thread, so I will mention it just in case. If you download the drivers that Bilou_Gateux posted and follow his instructions, you will then need to restart the Boot Information Negotiation Layer (BINL) service on your RIS server. This step is necessary prior to attempting to use the new drivers.
  4. It used to be in the past that no one single RealTek NIC driver would support all versions of the NIC - in other words one driver needed for 3+ year old NICs and another driver needed for current NICs, but for the last several months it seems that they've gotten it together over there. For me anyway, the latest RealTek NIC drivers will properly RIS boot for all generations of NIC. Are making any modifications to the .inf file before using it for RIS?
  5. Not as easy as it sounds. I've had an ipaq 3975 for several years now and in my experience PDF files on the Windows Mobile platform are pretty close to useless. It is definately the exception to the rule when you find a PDF file properly formatted for "reflow" or whatevr Adobe calls it. Word documents are not much better. The only thing I've ever found useful are .CHM files. You can find a couple of freeware chm file readers and they work great. The trick is finding the books you want in that format. It is possible as I carry around 600MB worth of essential reference material on an SD card, but sadly there is way more material formatted as PDF. I've really enjoyed books in the .LIT format for Microsoft Reader but I've yet to encounter one single technical reference in that file format. And I'm not about to go through the trouble converting titles to it either.
  6. Agreed My favorites have always been Mark Minasi's books. By the time I'm done reading one there's a couple dozen of those sticky bookmark things hanging out the top
  7. I didn't see if anyone provided an answer to the question about auditing, so if I missed it, sorry about that. Auditing is generally used in a domain environment. You can have event log entries generated for a defined security related event such as changing permissions, deleting files, etc. It's pretty useful for finding out who is deleting a specific file that should not get deleted, people attempting to elevate their permissions or rights. I've used it in the past to discover that a program was changing my custom NTFS permissions on a directory which was transferring ownership and consequently breaking the application for other users.
  8. This is where I usually send people:
  9. FWIW .NET Framework 3.0 is a little bit misleading of a title IMHO. When you get down to it, it's really just some additional libraries that require .NET 2.0 Framework. Unfortunately one part of .NET 3.0, the Windows Communication Foundation, has some sort of issue with .NET 1.1 SP1 in terms of the installation routine. You must have a reboot after installing .NET 1.1 SP1 prior to installing the .NET 3.0 components because of a file lock issue. I spent far too many hours trying to work around the issue and finally settled on two step process if you want to have everything .NET installed. It's not optimal, but it works.
  10. If you have any background in basic at all, or even VBscript, then picking up on VB2005 is pretty easy. The learning curve at first can be a little daunting, but once you "get it" everything falls into place. I started using Visual Basic with the idea of porting over a VBscript I had made, AutoRIS, into a full application, AutoImage. It took me literally only a few weeks to do it. I've found that almost anything at all that depends on .NET is going to be an absolute pig when it comes to RAM. My program continuously reports at 30MB in Task Manager. There's just no reason for that. But it's easy and I can make changes without too much problem. One of the advantages to programming with "managed code", as VB.NET and C# are, is that you don't have to concern yourself with garbage collection, screwing around with memory, etc. Plus you get a ton of functionality in .NET that you would otherwise have to construct from scratch (unless you were to purchase custom libraries). Java shares these same benefits, but again you need the runtime environment and Java apps tend to be slow and cumbersome. If you want fast, small, tight code, etc. you're going to want to look into C/C++. If you want to make a command line utility, say to use during windows setup before .NET is installed, then VB is pretty much out of the question.
  11. You could always call AutoItX from a VBS in order to work with the clipboard. The only requirement is that AutoItX3.dll be registered with the OS.
  12. No Go I'm not sure when you're running PromptKey.vbs, but if it's during Windows setup you'll need to use cscript as wscript is not available yet.
  13. Unfortunately I can confirm this issue.
  14. No cmdow has nothing to do with that window. That is part of the OS. Cmdow simply hides the command windows, just as RunHiddenConsole does. EDIT: Another alternative would be to use NirCmd.exe. A Google of that filename will take you right to the publishers web site.