bourny Posted January 18, 2006 Share Posted January 18, 2006 Can anyone think of a way of detecting a workgroup name .... I can use @logondomain or @logondnsname to pick up Domain but not workgroup. Basically I want to prevent my script running outside od 1 named domain and 1 named workgroup,. Thanks Bourny Link to comment Share on other sites More sharing options...
blademonkey Posted January 18, 2006 Share Posted January 18, 2006 Can anyone think of a way of detecting a workgroup name ....I can use @logondomain or @logondnsname to pick up Domain but not workgroup.Basically I want to prevent my script running outside od 1 named domain and 1 named workgroup,.ThanksBournyInstead of running it against the name of the Domain/Workgroup, why dont you have the script authenticate based on the Windows SID of the user?-Blademonkey ---"Educate the Mind, Make Savage the Body" -Mao Tse Tung Link to comment Share on other sites More sharing options...
bourny Posted January 18, 2006 Author Share Posted January 18, 2006 No good registering against sid of user as this brings too many variables and is subject to changing. I need to keep this as simple as above - Only work on 1 named workgroup and 1 named domain. Link to comment Share on other sites More sharing options...
PsaltyDS Posted February 1, 2006 Share Posted February 1, 2006 Can anyone think of a way of detecting a workgroup name .... I can use @logondomain or @logondnsname to pick up Domain but not workgroup. Basically I want to prevent my script running outside od 1 named domain and 1 named workgroup,. Thanks Bourny If NetBIOS is up, then this DOS command will show workgroup: REM Display all NetBIOS records nbtstat -n REM Display only workgroup record (same as domain name to NetBIOS) nbtstat -n | find /i "<00> GROUP" I'm not sure what the slickest way is to get that text back into an AutoIT string, any hints? Valuater's AutoIt 1-2-3, Class... Is now in Session!For those who want somebody to write the script for them: RentACoder"Any technology distinguishable from magic is insufficiently advanced." -- Geek's corollary to Clarke's law Link to comment Share on other sites More sharing options...
seandisanti Posted February 1, 2006 Share Posted February 1, 2006 If NetBIOS is up, then this DOS command will show workgroup: REM Display all NetBIOS records nbtstat -n REM Display only workgroup record (same as domain name to NetBIOS) nbtstat -n | find /i "<00> GROUP" I'm not sure what the slickest way is to get that text back into an AutoIT string, any hints? StdOutRead() ? Link to comment Share on other sites More sharing options...
PsaltyDS Posted February 1, 2006 Share Posted February 1, 2006 StdOutRead() ?Yeah, I saw that before... problem is, it's Beta only. I have to stick to Prod until I get a bug with GuiCtrlCreateButton figured out. Looks like redirect to a file and read it from there for now.Thanks for trying though. Valuater's AutoIt 1-2-3, Class... Is now in Session!For those who want somebody to write the script for them: RentACoder"Any technology distinguishable from magic is insufficiently advanced." -- Geek's corollary to Clarke's law Link to comment Share on other sites More sharing options...
seandisanti Posted February 1, 2006 Share Posted February 1, 2006 Yeah, I saw that before... problem is, it's Beta only. I have to stick to Prod until I get a bug with GuiCtrlCreateButton figured out. Looks like redirect to a file and read it from there for now.Thanks for trying though. what is the bug with GuiCtrlCreateButton? Link to comment Share on other sites More sharing options...
PsaltyDS Posted February 2, 2006 Share Posted February 2, 2006 what is the bug with GuiCtrlCreateButton?No exactly bugs. Resolved in this thread: Combo Box Options Not Pulled Down I had a perfect storm of problems with a script that was very dependant on Prod vs. Beta in its symptoms.All solved with the excelent support from this forum! There are two parts I might call "bugs": One is that installing Beta overwrites your Prod include files. The Gurus are working that issue, and don't consider it a bug. You can use F5 or Alt-F5 to run, and Ctl-F7 or Alt-F7 to compile, in Prod or Beta from SciTE. But with the Prod include files overwritten with Beta versions some things don't work in Prod any more (Array.au3 in my case).The second one is that when creating a Combo Box using GuiCtrlCreateCombo() the pull down list doesn't display unless a control height of at least 100 is assigned. This seems to be OS dependant, presenting in 2000 but not XP. I'm not sure what status is on fixing that, but the workaround is easy.The last part of the problem, with GuiCtrlCreateButton, was with unexpected symptoms of a coding error on my part, again dependant on Prod vs. Beta. In earlier lines creating the GUI, I meant to enable pasting information into some Input Boxes. I put in GuiSetState() instead of GuiCtrlSetState() to do it. In Prod, the bad lines were ignored and did nothing, not producing any error. In Beta the bad lines caused a funky state in the GUI that would not allow the Buttons to be created later on. The Buttons failed to create and returned a ContolID = 0, but the actual problem was several lines earlier, and depended on Prod vs Beta versions.Very educational for me at the least! Valuater's AutoIt 1-2-3, Class... Is now in Session!For those who want somebody to write the script for them: RentACoder"Any technology distinguishable from magic is insufficiently advanced." -- Geek's corollary to Clarke's law Link to comment Share on other sites More sharing options...
PsaltyDS Posted February 2, 2006 Share Posted February 2, 2006 New answer -- I posted two UDFs: _GetWorkgroup() and _GetWorkgroupList() in the following thread:_GetWorkgroup and _GetWorkgroupListEnjoy! Valuater's AutoIt 1-2-3, Class... Is now in Session!For those who want somebody to write the script for them: RentACoder"Any technology distinguishable from magic is insufficiently advanced." -- Geek's corollary to Clarke's law Link to comment Share on other sites More sharing options...
Valik Posted February 4, 2006 Share Posted February 4, 2006 There are two parts I might call "bugs":You might but we don't and this is why: One is that installing Beta overwrites your Prod include files. The Gurus are working that issue, and don't consider it a bug. You can use F5 or Alt-F5 to run, and Ctl-F7 or Alt-F7 to compile, in Prod or Beta from SciTE. But with the Prod include files overwritten with Beta versions some things don't work in Prod any more (Array.au3 in my case).This was by design. It was a poor design, but it was by design. As you've already noted, this is being worked on.The second one is that when creating a Combo Box using GuiCtrlCreateCombo() the pull down list doesn't display unless a control height of at least 100 is assigned. This seems to be OS dependant, presenting in 2000 but not XP. I'm not sure what status is on fixing that, but the workaround is easy.Well, given that the this is in the documentation, this is definitely not a bug and it's nobodies fault but your own that you had problems with this. The documentation clearly states that there is a difference in behavior on different versions of Windows and that the solution is to specify a larger size. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now