|
6W
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
modified 26-Apr-16 9:04am.
|
|
|
|
|
|
Nope, thanks i messed up forgetting to count the d so instead of 4 w its 6w
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
I guess it can't be Dijkstra then...
[edited]
DIJKSTRA
ANDROIDS
I count 5W.
|
|
|
|
|
sh..... i fortgot the D
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Well you get to try again tomorrow
|
|
|
|
|
maybe i should reuse this XD
Thinking of something new!
Although i am impressed it didn't come to anyones mind that it could be dijkstra.
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Motorcar?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
3W
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
That's a relief!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
come on, try again mate
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Navigate suggests 'Search'
And possiblu every student has written a 'Search' algo once.
So is it must be Search3|
or is it Searchin?
|
|
|
|
|
The direction aint that bad but still no chicken for you.
4W
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
A*Search???
I don't think that's one word, though...
|
|
|
|
|
4W
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
modified 26-Apr-16 9:07am.
|
|
|
|
|
Traverse?
Tell me I'm right this time
|
|
|
|
|
Im sorry you are not
5W
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
modified 26-Apr-16 9:03am.
|
|
|
|
|
That's alrighto
You were meant to win it again Will try harder today
|
|
|
|
|
|
5W
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
That was my first guess yesterday, but you initially had 4W for Androids.
|
|
|
|
|
Erm...
Let's say I would like to test the new MS Edge browser.
And that I want to configure the start page and the search engine to be used by default.
When I start it and go to the three dots (top right) and then click on settings, it takes a while and then edge disappears/shuts down automatically.
Has anyone here seen that behavior? and has anyone here solved it?
I've downloaded a small powershell script that resets it at it's factory settings, but no way it helped.
Thank you in advance!
|
|
|
|
|
Works fine for me, version information:
Microsoft Edge 25.10586.0.0
Microsoft EdgeHTML 13.10586
|
|
|
|
|
Method 1:
Run the apps troubleshooter and check if it helps with the issue. Refer to the following article and run the Apps troubleshooter:
Run the troubleshooter for Windows apps
If the issue still exists, try the next method.
Method 2:
Try to run a System File Checker (SFC) scan to check for any file corruption. SFC scan will scan for corrupt system files on the computer and repair them.
Press Windows key + X, click Command Prompt (Admin).
In the Command Prompt, type the following command, and then press ENTER:
sfc /scannow
If the issue still exists, try the next method.
Method 3:
You may check the same issue with the new user account.
Try these steps to create a new user account and check if it fixes the issue. Refer to the steps below to create a new User Account:
Go to Settings.
Choose Accounts and then select Other User Accounts towards the left.
Select Add an Account.
Enter a user name and hit Next.
Click on Finish.
Sign out from the current Account and Log into the new account.
Check if issue persists.
|
|
|
|
|
Apps troubleshooter?
Second method already tested. No luck.
|
|
|
|