|
Message Removed
modified 29-Aug-19 21:10pm.
|
|
|
|
|
Message Removed
modified 29-Aug-19 21:10pm.
|
|
|
|
|
Herself decided to actually cook tomorrow, so ask for the recipe.
No problem ... "can you print that for me?"
Ah. Haven't put a printer on the Surface...
"Settings", "Printers and scanners", "Add a printer or scanner" ... searching ...
Oh look. It's there ... and it works. I didn't even have to select it and say what it was.
Very smooth - I remember "Plug and pray" and just how fowl it was most of the time, but that is mature and very, very nice. Impressive stuff.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I know it's going to be an adventure at dinner when my wife is perusing a recipe, and says, "That doesn't seem right..."
That often translates to changing the amount of one or more ingredients, and "bumping up the temperature".
In that case, I start thinking about what I'm going to have for my "backup dinner".
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
So has it connected with a WSD... port and some Microsoft created driver?
Control Panel -> Network and Sharing Centre -> Change advanced sharing settings, then turn off Private -> Turn on automatic setup of network connected devices.
That and Control Panel -> Power Options -> Choose what the power buttons do, then turn off Turn on fast startup (recommended), are the first things I get rid of in a new Windows 10 install.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
Michael Martin wrote: turn off Turn on fast startup
I've disabled that ever since the wonderful "fast startup" killed the system drive on one of my laptops (and I do mean "killed" -- to the extent that all the partitions had to be removed).
There are hundreds of complaints about the wonderful "fast startup" killing system drives on the Interwebs, so people leave it on at their own risk, just to save five seconds at boot.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
When I think of most printer drivers I have been around, it makes me cringe to think about one being installed automatically on a tablet. I hope that one behaves much better for you than they do for me.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
I was kinda expecting "I found a Samsung C430W - insert the CD in the DVD drive" or a download of 700MB of bloatware from the manufacturers site and half a million "read the licence" windows.
But no: it quietly loaded just the print drivers it needed and was ready to rock and roll in seconds. That's how Plug and Play should have worked from day 1 ...
And Win10 gets plenty of stick (from me, included) so I thought that a positive message when it does well is deserved. I doubt that Linux is as smooth to add a printer ... (I just checked on Google, and no, it doesn't appear to be!)
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
That is a surprise. I am glad to read it worked out well for you.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
One thing 10 does well is install printers it never otherwise knew was in the building.
|
|
|
|
|
It should give you the option to install the manufacturer's drivers; I'd trust them quite a bit more than ms drivers -- even if ms drivers have the newest and coolest icons.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Humble Bundle are giving away Dirt Rally: Get DiRT Rally for free[^]
No catch, just log in and grab it. I've had a few free games off them, and they all work with no commitment to buy others required or implied. I'm sure they would be happy if you did, but ... they don't mind if you don't.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: No catch
"when you subscribe to the Humble Bundle newsletter" 
/ravi
|
|
|
|
|
... which is just an email, and can be fed to "junk mail" without problems.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
... And if you've already subscribed, it just gives you the game.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Thanks sir!, I now have 3 games for free just because of your posts.
|
|
|
|
|
Thank you! 
|
|
|
|
|
...They know how to make a Star Wars trailer[^]
Pity the movie is unlikely to be as good* ...
* Judging by the previous two, here
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
If they know how to do that, why didn't they do it?
That thing I saw was for the most part from old movies, with characters which they did their best to erase. And yeah, was that MaRey Sue with a red swiss army light saber? Shocking. Throw in some CGI and that's the best they can do? Thanks a lot.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
|
Hasn't everyone? I did. It even has its own debugger.
Sorry, my cynicism sneaks out now and then.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Do you have a link? I'd be very interested in having a look at it.
Best Wishes,
-David Delaune
|
|
|
|
|
I did it three employers ago. They were bought out and then I worked for the buyer for a while. The bottom line is it's a "captive" software package now, for internal use only. It was very flexible and we could do a lot with it but it wound up being used almost exclusively for one type of automation system known as a wetbench. Here's a video of one in operation : MEI Wet Processing - Full Auto Wet Bench[^]. Here's the page about the software : MEI Wet Processing Systems - IDX Flexware Software[^]. There were over a thousand systems installed the last time I checked. Although I am certain a good number of those have been de-commissioned over the years because they have a somewhat limited lifespan. I think there is at least one in just about every major semiconductor manufacturer in the world. I practically lived in clean rooms for about twenty years and I am very glad to be out of that industry.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Well,
Interesting. The software in both the screenshots and video look alot like a Wonderware HMI for SCADA.
You mentioned that you've written both an interpreted programming language and custom debugger. Could you expand more on that?
Best Wishes,
-David Delaune
|
|
|
|
|
Yes, it does look a bit like Wonderware but ours had more 3D effects. Apparently they became aware of us because one year at SemiCon in San Francisco they saw my badge and wouldn't let me enter their booth. I felt like I had really arrived. 
The language was a cross between C and FORTRAN with, as I used to say, the worst of both. It started out fully interpreted with a VM-type of design and then it morphed into a fully compiled-on-the-fly thing with native machine code generation when we heard concerns about its speed. It could be pre-compiled and loaded from a binary image also. It either called functions from DLLs that were mapped in or it executed an intrinsic operation like a computation or comparison. Everything was shared memory based and this was key to the whole system. We had the prototype definitions of all functions from the DLLs that were mapped in loaded into shared memory so it was like a pre-compiled header and it compiled very quickly. The script engine could be embedded and it was into three or four different process, including the operator interface. Every action in it like clicking a button could invoke a script function.
The shared memory part was very key. The whole system was based on it so you could access data anywhere. That forced things to be rather primitive in the sense that we could only have POD types in shared memory. There were what I called psuedo-pointers though which were actually offsets since pointers are useless outside of the owning process. Even the generated code was in shared memory and the script engine context was too. We started all of this in QNX but we became annoyed by the lack of driver support so we jumped into the Win32 world as soon as it was out and Windows NT when it was in beta. We also used Visual C++ version 1.0 with it. At that time, you could map into another process' memory space but you couldn't safely unmap from it. That was an important thing for us and meant everything had to go into shared memory. We wanted to be able to attach to a running process with the debugger, interact with it, and then detach from it so it could continue running.
The debugger was a pretty standard one for its time. It showed all of the script files used in the process and let you single step through the code, set break points, and all the standard stuff. You could also see the variables for current script function along with variables you selected to watch. This brings up one of the weakness of the design. Because everything had to be in shared memory for access by the debugger, the stack was too but it was a static stack like FORTRAN. This limited recursive functions but we never found a need to implement one so it wasn't a big deal. In retrospect, I could have made a big stack in shared memory and made the stack dynamic but I didn't think of it at the time. I was more concerned with mapping the symbols for the current function and it wasn't obvious to me how to do that dynamically then. It is now.
I mentioned QNX. We really liked its message passing, multi-processing architecture so we implemented that for Windows. With shared memory and a few synchronization events we were able to make a very fast message passing library. That made for a very flexible system architecture. We tried Windows 95 and found its context switch time to be too slow at more than ten times slower than NT so we stuck with NT. Both were out about the same time, at least in beta form. MSDN was really useful back then.
I keep writing we and that's because me and one other guy did all of this. It took about three years to get it all refined. We were very fortunate to get that much time.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
