aquarius

Hi! This is an old thread now, but I thought I'd offer another solution that might help in the wireless scenario we were discussing. If you turn off "Windows XP Professional Fast Logon Optimization", Windows XP will wait for network to be available, and run login-tasks synchronously instead of asynchronously, but the network thing is interresting. It can be deployed using GPO, but you can test it with the local policy; Run gpedit.msc Find "Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon" More info: KB305293 Cheers!

FORM FORK DORK DARK BARK PARK PART FART FAST VAST VASE BASE CASE CAST CART DART DARE CARE FARE MARE MALE TALE SALE SOLE SOLD MOLD TOLD GOLD FOLD FOLK FILK MILK MILE MALE MATE MAZE DAZE DOZE DONE NONE NOSE POSE POLE PORE MORE SORE SURE PURE PARE RARE RACE FACE FACT TACT PACT PAST FAST CAST CASE BASE VASE VISE VISA VESA VEST BEST JEST TEST TEAT MEAT NEAT SEAT SEAR FEAR NEAR DEAR BEER BEEP PEEP PEER LEER LEEK LEAK LEAP LEAN BEAN BEAD LEAD LOAD LORD CORD FORD WORD WOOD GOOD GOAD GLAD CLAD CLAP SLAP FLAP FLAT FLAX FLAY FLAB FLAK FLAW FLOW BLOW BLOT PLOT SLOT SLOP SLOB BLOB BLUB CLUB CLUE GLUE GLUG GLUM PLUM PLUG PLUS FLUS FLUX FLEX FLEE FLEE FREE FRET FRAT BRAT BRAN BRAG DRAG FRAG FRAY PRAY PREY TREY GREY GREW BREW CREW CROW BROW GROW GLOW GLOB SLOB SLAB STAB STAY STAR STAP STAG STOG STOP STEP STEW SHEW PHEW CHEW WHEW WHEN THEN Yes, but is it better THAN some other threads?

FORM FORK DORK DARK BARK PARK PART FART FAST VAST VASE BASE CASE CAST CART DART DARE CARE FARE MARE MALE TALE SALE SOLE SOLD MOLD TOLD GOLD FOLD FOLK FILK MILK MILE MALE MATE MAZE DAZE DOZE DONE NONE NOSE POSE POLE PORE MORE SORE SURE PURE PARE RARE RACE FACE FACT TACT PACT PAST FAST CAST CASE BASE VASE VISE VISA VESA VEST BEST JEST TEST TEAT MEAT NEAT SEAT SEAR FEAR NEAR DEAR BEER BEEP PEEP PEER LEER LEEK LEAK LEAP LEAN BEAN BEAD LEAD LOAD LORD CORD FORD WORD WOOD GOOD GOAD GLAD CLAD CLAP SLAP FLAP FLAT FLAX FLAY FLAB FLAK FLAW FLOW BLOW BLOT PLOT SLOT SLOP SLOB BLOB BLUB CLUB CLUE GLUE GLUG GLUM PLUM PLUG PLUS FLUS FLUX FLEX FLEE FLEE FREE FRET FRAT BRAT BRAN BRAG DRAG FRAG FRAY PRAY PREY TREY GREY GREW BREW CREW CROW BROW GROW GLOW GLOB SLOB SLAB STAB STAY STAR STAP STAG STOG STOP STEP STEW SHEW PHEW CHEW WHEW That means it's time to WHET the appetite for more words?

FORM FORK DORK DARK BARK PARK PART FART FAST VAST VASE BASE CASE CAST CART DART DARE CARE FARE MARE MALE TALE SALE SOLE SOLD MOLD TOLD GOLD FOLD FOLK FILK MILK MILE MALE MATE MAZE DAZE DOZE DONE NONE NOSE POSE POLE PORE MORE SORE SURE PURE PARE RARE RACE FACE FACT TACT PACT PAST FAST CAST CASE BASE VASE VISE VISA VESA VEST BEST JEST TEST TEAT MEAT NEAT SEAT SEAR FEAR NEAR DEAR BEER BEEP PEEP PEER LEER LEEK LEAK LEAP LEAN BEAN BEAD LEAD LOAD LORD CORD FORD WORD WOOD GOOD GOAD GLAD CLAD CLAP SLAP FLAP FLAT FLAX FLAY FLAB FLAK FLAW FLOW BLOW BLOT PLOT SLOT SLOP SLOB BLOB BLUB CLUB CLUE GLUE GLUG GLUM PLUM PLUG PLUS FLUS FLUX FLEX FLEE FLEE FREE FRET FRAT BRAT BRAN BRAG DRAG FRAG FRAY PRAY PREY TREY GREY GREW BREW CREW CROW BROW GROW GLOW GLOB SLOB SLAB STAB STAY STAR STAP STAG STOG STOP There's still many "trival" words to come up with, so STEP up to the challenge! (Hope noone is entering the same word while I write this, though I have no problem sharing credit with a Doe

FORM FORK DORK DARK BARK PARK PART FART FAST VAST VASE BASE CASE CAST CART DART DARE CARE FARE MARE MALE TALE SALE SOLE SOLD MOLD TOLD GOLD FOLD FOLK FILK MILK MILE MALE MATE MAZE DAZE DOZE DONE NONE NOSE POSE POLE PORE MORE SORE SURE PURE PARE RARE RACE FACE FACT TACT PACT PAST FAST CAST CASE BASE VASE VISE VISA VESA VEST BEST JEST TEST TEAT MEAT NEAT SEAT SEAR FEAR NEAR DEAR BEER BEEP PEEP PEER LEER LEEK LEAK LEAP LEAN BEAN BEAD LEAD LOAD LORD CORD FORD WORD WOOD GOOD GOAD GLAD CLAD CLAP SLAP FLAP FLAT FLAX FLAY FLAB FLAK FLAW FLOW BLOW BLOT PLOT SLOT SLOP SLOB BLOB BLUB CLUB CLUE GLUE GLUG GLUM PLUM PLUG PLUS FLUS FLUX FLEX FLEE FLEE FREE FRET FRAT BRAT BRAN BRAG DRAG FRAG FRAY PRAY PREY TREY GREY GREW BREW CREW CROW Gotta sweat to your BROW

I'm longing for the GREY Havens...

FORM FORK DORK DARK BARK PARK PART FART FAST VAST VASE BASE CASE CAST CART DART DARE CARE FARE MARE MALE TALE SALE SOLE SOLD MOLD TOLD GOLD FOLD FOLK FILK MILK MILE MALE MATE MAZE DAZE DOZE DONE NONE NOSE POSE POLE PORE MORE SORE SURE PURE PARE RARE RACE FACE FACT TACT PACT PAST FAST CAST CASE BASE VASE VISE VISA VESA VEST BEST JEST TEST TEAT MEAT NEAT SEAT SEAR FEAR NEAR DEAR BEER BEEP PEEP PEER LEER LEEK LEAK LEAP LEAN BEAN BEAD LEAD LOAD LORD CORD FORD WORD WOOD GOOD GOAD GLAD CLAD CLAP SLAP FLAP FLAT FLAX FLAY FLAB FLAK FLAW FLOW BLOW BLOT PLOT SLOT SLOP SLOB BLOB BLUB CLUB CLUE GLUE GLUG GLUM PLUM PLUG PLUS FLUS FLUX FLEX Allmost ready to FLEE...

@ethanmcf: I know you have told us before, but I'm just thinking: is it only the router which is far away from the offices? Is it possible to wire the clients to the serverroom, and use a wireless bridge from there to the router? Do they only use cell phones or are there telephone lines that can be used? If the net is not several decades old, it might be be Cat5 which is OK for 100MB ethernet. A CAT5 cable often has 4 pairs, of which the PC needs 2 (100MB max) and 2 left that you can use for a telephone and a spare. (In norway and europe I think, at least with RJ45 sockets, usually have all 4 pairs are connected at the socket even for 1 telephone outlet, to facilitate future expansions.) Then you'd have wired access to the servers and DC, and only the router would be connected via the bridge. Either that or use nmX.Memnoch's tip. Users might find it irritating though, if they have to re-login if they where too fast and stuff like that.

You must "Allow Windows to handle the wireless connection" instead of the vendor driver, This way the network starts in time to let you log in with it... Some WLAN cards may not let you do this, and Windows XP or later is required on the client. Anyway, that is not a problem with the DC.

Allso, if you have other 2k3/2k servers in the domain (defined as domain servers), I think they will cooperate as Backup Domain Controllers should the DC fail. Still, I would treat the Domain Controller as a critical component, a dedicated server, and no multiboot or other stuff that complicate things. Make good backups!! Keep it as simple as possible, it will become complex enough soon! Don't install any kind of application or code that does not pertain to it's role as a Domain Controller!!! (goes for any kind of server) Regards, )chicken fish(

Sure, use the other router! Just eliminate the wireless for the test. It must be set up with DHCP and the necessary stuff of course. If it still fails with the test router you can begin searching for causes other than WiFi. Basic networking first. (Remember that ping might be blocked by client firewalls) Time to log out for me, good luck!

Hello! The DC is just another device in that respect, just set it up with automatic IP, gateway, DNS as you would any laptop. You don't need to associate the DC with the router. I really think you should move the DC and a test computer to the router room (or within the reach of 10m cables to test it! When adding a client to the domain, and logging on to a client with a domain user works using wired LAN, then move it to the wireless net. Keep it simple!

Hello! Warning: No step-by-step here, just a few comments! From what I read in your post, the server is not online the whole time, and wireless might have glitches or whatever, so I would use the DHCP capabilities of the router instead of the DC. Generally, give wired connection to the DC and as many computers as possible. Make sure encryption is in place. WPA, not WEP. (Configure the router. recent routers have a lot of capabilities in this area!) I recommend giving the server(s) static IP address. The router is the default gateway, firewall (if it can do it, enable it!), DHCP-server. The DC is the server with the user accounts database and stuff like that. You join your servers to the domain, and give permissions to domain users. DC has nothing to do with internet access! The DHCP parameters should give the clients the proper settings. Adding clients to the domain: Wireless or wired connection should not matter. (to be onest, I havent tried a wireless DC myself, and by the number of replies you are getting... not many others either :-) On the client, right click My Computer/Properties/Computer Name/Change and join the domain. Use a Domain Administrator account defined on the Domain Controller to authorize the add. If this doesn't work, I strongly feel you have other issues than the wireless scenario. You can easily eliminate the wireless as a cause by connecting the computers (DC + a test client) with a normal switch and ethernet cables to test the domain. Of course, if it doesn't work while wired, it will not when wireless either! If you give more details, you might get better help! Good luck!

Hello! If you can print it, then you can make PDF PDFCreator (A SourceForge project, free) Then File/Print/select PDFCreator (Or maybe you have another PDF-printer allready) Of course this will not save any of the invisible message headers (server stamps, Sent/received etc.) For backup I would still use the database. Note: If the mail has attachments, using PDFCreator you can add these to the same PDF: 1. Print the mail, click "Waiting" instead of "Save" in the PDFCreator dialog, to tell it to wait for more jobs. 2. Print attachments. These will be placed in the PDFCreator queue, waiting for further actions. 3. When all attachments are in the queue, select all and then click the "Combine" button. (At this moment, the PDFCreator window might be minimized to the system tray) 4. Click the red printerbutton to resume the operation, and click Save in the PDFCreator dialog. The result will be one PDF with the mail and attachments. Cheers!

Hi! I promised to check out the keyboard state in a multiuser environment, i.e. with several sessions running. Only tested shift key state. Remote PC was Windows 2000 SP4 Tested for VK_SHIFT (Any shift key, left or right) VK_LSHIFT (Left shift key) VK_RSHIFT (Right shift key) Citrix on NT4 and Remote Desktop on Windows Server 2003: Remote users VK_SHIFT, VK_LSHIFT and VK_RSHIFT works, and no "leak" from the console or other remote sessions. Netmeeting Remote Desktop: (W2K/XP) (Which is not very multiuser, it just takes over console and disables local input) Remote user shift is detected (VK_SHIFT), but it does not detect the difference between the Right or Left shift keys in this scenario, i.e. a test for VK_LSHIFT or VK_RSHIFT would not work. TightVNC: (W2K Server) Same as Netmeeting. You can enable local input in VNC, in which case both remote and local user is detected, as should be expected. Cheers!

Seems to fit the bill for me, jaclaz Markus' program checks out OK in XP (and probably others), is 29 Kb, GNU GPL freeware. Supports a lot of key combinations too, not only shift key, and realtime (fast enough for a batch program anyway). It detects shift key state even if the user is in another program (expected of course). I will test the multiuser performance with remote desktop to see if it detects only the console keys when run by a remote user, or if all users input is detected, but I have a feeling the OS handles it. It's a Win32 program made in delphi. (It might work in Win9x, but I guess it needs the 32bit subsystem installed first.) @LLXX: The tiny machine code was very, very neat, but I think this is allso what I was looking for and more! Thanks for your effort and hope this noob haven't wasted too much of your time... Cheers jaclaz and LLXX!

Yes, exactly, the shift keys doesn't repeat, but the test pattern on both Windows 2000 SP4 and XP SP2 matched the typical "rythm" of repeating keys . Now TESTED on NT4 server, same result! (So it's not only XP, maybe it's a problem with the 16 bit subsystem or something and I guess Win32 code will work better.) Haven't touched asm since 386, so I'm in a little over my head here, to say the least! (This problem explains why I had such a hard time finding compiled code, only script examples in VB6 and so on...) If you're in the mood it would be very interesting to see if the Win32 approach could work! But if it turns out to be a lot of work, or small hope of success, please don't!.....

Very good, and really small! This is a good startingpoint! (Now this topic should be moved to programming I guess?) I have a problem with detecting the state, though. It seems to behave like a repeating key (like if you press and hold a normal letter) instead of the keypressed state of a shift key. Tested like this: @echo off :loop shiftkey& echo %errorlevel%& goto loop It prints the errorlevel (exitcode from your program) 0's when no shift keys is pressed. When I push and hold for example the left shift key, it displays '2' once, then 0's for about a second, then more 2's mixed with 0's. A "real" batch program will do the test at the start, and might likely miss the exact times when the key is detected. Nevertheless I think what you suggest is the best way to do it (a small asm code) I guess it should test maybe other bits in the AND statement or another address, but knowing it will take me some time to test and read some, I wanted to thank you at once for this way of doing it! Cheers LLXX!

Hi! I'm looking for a (free and small) command-line utility to detect shift key status and returning it in exit code. Has anyone seen something like that on the net? When executed from a batch program, it should be possible to check errorlevel to see if the user was pressing SHIFT for instance. Regards!

Introducing Aquarius! I know it's a lame username, but I am a Pisces and my real name sort of rhymes with aquarius, so it's kind of fitting. I allso like swimming, up to 32 metres deep (with scuba, I admit) allthough mostly freediving to a few metres. With a job and family, scubaing opportunities has gotten rare in the late years, but any time I have a chance I bring my snorkle. The swimming season in Norway is pretty short allso, a few months, but beautiful! Nice work by a lot of people here! I am using WPI, not for the unattended setup but as a tool for installing new software. (For unattended setup (RIS) I use my own scripts, not as clever, but controlled by customized OSC-pages in RIS.) Cheers! Aquarius

Nah, this idea was not to stop the task starting, but to edit it, enabling it to exit without doing anything (skip), but yes, it works with scripts started from Task Scheduler. (The tasks I put in servers Task Scheduler is normally specialized batch programs or vbs/js scripts I create myself.) This strategy gives you complete control over which tasks will run and which don't (skips), without having to change the Schedule Task properties programatically, which might be complicated. (You can use the AT command instead which is easy to control from batch programs, but lack the more advanced options) Maybe you want to stop all tasks. You can do that by stopping the schedule service, which will of course stop all scheduled tasks while you are away. The scheduler service is named slightly differently in different OS'es, but assuming XP: net stop "Task Scheduler" When you are back and want to resume the tasks, net start "Task Scheduler" So I have three strategies for you, depending on your needs: To stop all tasks: stop the scheduler service temporarily To stop not all, but just a few tasks in the form of editable scripts: Add the "skip once" strategy to the script(s) (no change in the schedules) Or use the at command Edit: Maybe it's not easy to use the at command from a script to change a schedule, but it's doable. You can't set next execution date, but knowing the ID of the job, you can delete the schedule, and you can have the script reschedule itself later. You could find the current ID of a task by using FOR, AT and FIND. To stop the job with ID 1: at 1 /delete

Someone might know how to change the next execution schedule of a job, but this works as well: (So simple I'm allmost embarrased but I'm lazy and it works :-) I usually make a temporary file, e.g. C:\temp\skipjob.flg or whatever, and make the scheduled program check if it exists. If it exists, delete it and exit. Next time it will run as normal. The schedule has not been changed, just the behaviour of the program. Make a small script that justs creates this little "flag file" when you need it. (Change your program to accept an argument, for example /skip, to tell it to create the flag and exit, if you don't want more scripts in your folder. ) If you want it to skip the job until you are back from a holiday, just check for existence, but don't remove the flag. Then you remove it when you are ready.

Hello! You can redirect STDERR to nul allmost like in Unix. Redirect a commands stderr (channel 2) to nul (yes there are a couple more channels :-) dir sdlkfn 2> nul You can do this for the whole batch by starting it this way: yourprog.cmd 2>nul To conclude, your program can restart itself, with stderr redirected to nul, in this manner, so that you don't have to start it like above: @echo off if not %1!==/go! %0 /go 2> nul shift REM Put the rest of your program here, errors will not be displayed on STDOUT REM Example - dir without error: dir a-dir-that-doesnt-exist-ksjdhf-werwe Have a nice day!

Hello all! Here is a script for you that I made to avoid using CMDOW with Windows Post-Install, hope it will help! Upgrading to WPI 5.0 might allso help, since it eliminates wpi.cmd, but you might still want this :-) You can use it to start programs (e.g. wpi.cmd from Autorun) like this: OPEN=WScript.exe wpi\lh.vbs wpi.cmd Note: To avoid putting a long path in there twice, the cmd file is assumed to be in the same folder as the script. (\WPI in the example) I know it's not very good when it comes to handling arguments, because you will lose quotes... Here is it: ' rh.vbs - Run (a cmd batch) hidden - aquarius 11:58 14.12.2005 ' Example: WScript.exe wpi\rh.vbs wpi.cmd ' Assumes wpi.cmd is in same folder as rh.vbs ' quoted arguments not handled well... Dim objArgs, WshShell Dim strWindowStyle, DebugWait, strCMD, strShellRun, ProgFolder, Prog, strApp, I Set objArgs = WScript.Arguments Set WshShell = WScript.CreateObject("WScript.Shell") Const nDebug = false ' nDebug=true for Debug mode strWindowStyle = 0 DebugWait = false strCMD = "Cmd /c " If nDebug then strWindowStyle = 1 DebugWait = True strCMD = "Cmd /c CLS & " End If if WScript.Arguments.Count = 0 then msgbox "strApplication requires an argument" & VbNewline &_ "Example: WScript.exe wpi\rh.vbs wpi.cmd" WScript.Quit (-1) End If ' Find folder and program to launch (arg 0) in the same folder as the script ProgFolder = Left( WScript.ScriptFullName, InStrRev( WScript.ScriptFullName, "\" )) Prog = objArgs(0) strApp = """" & ProgFolder & Prog & """" ' Add all arguments (following arg 0 which is the cmd file) For I = 1 to objArgs.Count - 1 strApp = strApp & " " & objArgs(I) Next strShellRun = strCMD & strApp If nDebug then if wshShell.Popup( "Do you want to execute " & strShellRun & " ?", 10, "Confirm", 1 ) <> 1 then wScript.Quit(1) End If End If WScript.Quit (WshShell.Run( strShellRun, strWindowStyle, DebugWait )) As you can see, you can set the nDebug to true to verify it's actions. Allso, instead of using CMDOW @ /VIS for handling error messages, here is another script to display error dialogs etc. 'dialog.vbs - Aquarius, 23:32 15.06.2006 'WScript.exe dialog.vbs "Message" [/T:"Title"] [/S:type] [/W:SecondsToWait] 'The returned errorcode will be like Windows Script Host Popup Method ' except if no arguments where passed, in which case it returns -2 'Put strings with spaces inside quotes (message and title) Dim WshShell, DlgTitle, nSeconds, nType Dim argsNamed, argsUnnamed nSeconds=0 nType=0 set WshShell = WScript.CreateObject("WScript.Shell") if WScript.Arguments.Count = 0 then WshShell.Popup "Syntax: wscript.exe dialog.vbs " + chr(34) + "Message" + chr(34) + " [/T:" + chr(34) + "Title" + chr(34) + "] [/S:type] [/W:SecondsToWait]", 0, "Dialog.vbs", 4112 WScript.Quit (-2) end if Set argsNamed = WScript.Arguments.Named if argsNamed.Exists("t") then DlgTitle=argsNamed.Item("t") if argsNamed.Exists("s") then nType=argsNamed.Item("s") if argsNamed.Exists("w") then nSeconds=argsNamed.Item("w") WScript.Quit (WshShell.Popup( WScript.Arguments.Unnamed(0) , nSeconds, DlgTitle, nType)) Here is an example: ifmember.exe administrators && ( WScript.exe %wpipath%dialog.vbs "You are not an administrator. Log in with admin rights to use this program" /T:"WPI" Exit ) It does pass on errorcodes from the dialog, so you can use it to do some decision making in the batch. The full syntax is in the script :-) I hope these may help you further! Aquarius