This is exactly how I had to do it in Windows XP. I have an application that eats too much CPU while doing a certain batch process, so I start it in low priority mode to allow interactive processes to respond.
echo on start/belownormal program.exe exit
I just keep that batch file in the directory for my program and have two shortcuts, one to my batch script and one directly to the program. I never did figure out how to get PowerDVD to start in Realtime mode when I pop in a CD either, nor could I get a shortcut to simply run the start command to start my apps at a given priority level. If XP can't do it cleaner than by running a script, I wouldn't necessarily expect Linux to, but I would be happy if it did.
O(log(N)) for insertion, but that only occurs when a new task is created. The scheduler's complexity would be calculated based on how long it takes to choose what process to allow to execute next.
Given the new info that the furnace is going in after the IDF, which must then be retrofit, this is probably the best option yet. Your equipment in this location is NOT going to last, so get another unit set up before the current one fails. You'll wind up spending less time and money in the long run by far. Although geeks do make miracles happen every day, there's a cost-benefit analysis to consider. It sounds to me like you have four options: 1) Put the furnace elsewhere 2) Put the IDF elsewhere 3) Prepare to lose IDF components frequently, causing issues with stability of both your network and your budget. 4) Spend more to insulate, cool, and protect the IDF than the cost of a relocated one
If you can come up with and implement a valid 5, I'd be interested to see what it is. The problem with this is that it will probably wind up being a combination of 4 and 3, with a final result of #2....good luck regardless what you decide.
STP, if installed right, will lessen interference, but fiber will eliminate it entirely. The OP was right to go with fiber, given that they had the budget for it.
Actually, the check box there is labelled "Install QuickTime icon in the system tray"
There's a difference between loading the program and showing the icon. Unless Apple mislabeled the box, they need to add a second box. Otherwise they need to fix the label. Either way, if anyone knows I'd appreciate an informed response.
Keeping the temperature up in an abandoned house is important to prevent such catastrophies as freezing pipes. Plus it's not exactly a great idea to allow appliances to be exposed to sustained extreme temperatures (either hot or cold)
Freezing pipes can generally be prevented by shutting off the water at the entrance to the house, but as there are many things in houses which are designed to be kept at room temperature, it's usually considered best to keep them at a lowered room temperature. You also have things like the goosenecks in drain pipes that can't be emptied, and if you did (or if they burst) would create a real mess. Ever smelled a drain pipe where the gooseneck has dried out? You don't want to come back to a house that's been sitting like that.
As for electricity, you need that to run most thermostats, even if the heater is propane or natural gas. Additionally many people set timers for lights when they leave for an extended period in order to make the house appear occupied in an attempt to dissuade burglars. These simple timers have no batteries (at least the ones I've seen) and therefore lose time should the power go out. If it is out for under an hour, no big deal, or multiples of 24 hours would leave it where it was, but you don't want your lights going on in the morning and off mid-day.
20 Meg drive that Dad added onto the IBM 8088 PC that he bought in 1983. Still worked fine the last time I booted the system. (Admittedly several years ago, probably 5.)
...it was nice being able to list out the entire contents of the hard drive and be able to read each filename as it scrolls up.
I think I know a thing or two about this subject as I managed the computer labs at a university for about nine months. That was something like 900 machines in 35 labs as I recall.
Start over with a clean install of XP Pro on one machine. (which gives far better manageability than Home; If you don't have remote desktop or gpedit you'll miss them.) Install all of the programs, plugins, etc that you will need.
Run gpedit, the group policy editor. You can lock them down by making such restrictions as removing Run... from the Start menu, disallowing the ability to lock the computer, even removing the ability to change the preferences in IE. It's surprisingly user-friendly for the control that it provides. I used this to lock down the kiosks and other public access systems, leaving very little for users to do. They could run the few programs that I left for them (IE, FireFox, and a few other specific programs) and not do much else. They couldn't change preferences, no Run dialog, no right-click menu on the desktop, no way to save anything, or even see the hard drives, for that matter. You do need to leave yourself a back door, however (i.e. allow cmd to be run from a desktop icon which is only installed in one admin account, so that you can run gpedit again to remove restrictions.)
Use Norton Ghost to create an image of the hard drive and distribute it to the other machines. (They do have identical hardware, correct? If not, there is a way to use sysprep to remove the drivers before creating the image, but I have never done this.) You will want to create a script to rename the machines based on a DNS entry or other network database as a source, using the MAC address as a unique ID. I suppose you could rename them all manually, but since it requires two reboots, it could be a rather time-consuming process.
Ghost is great. Well worth the license fee for a setup like a highschool. You can make a change on one machine and distribute that new hard drive image to all the other machines. My process was: remove a machine from the lab in question, put the old ghost image back on it (to remove any corruption introduced since it was last imaged), update Windows and McAfee, make the change, begin the rename cycle, create a new ghost image, and finally distribute the image to the lab. It took a couple of hours (more or less depending on image size and network speed), but every time I did it, it was as if I had just reinstalled Windows and every other program on every machine in the lab. Just try installing 35 copies of Windows, Office, FireFox, Adobe, JRE, and 30-50 other programs in a few hours using any other system! I had a laptop to use as a Ghostcast server and a set of CDs to boot each system with. I simply had to set up the laptop as a server on that lab's subnet, boot each system to the CD (Bart PE -- Live CD of XP) which would automatically run Ghost and connect to the server. I start the distribution from the server and when it finishes, eject each CD, and reboot the systems. They rename themselves and return to the XP login screen. Nothing to it!
My alternate method was a different Bart PE CD from which I mapped my images share (net use s: \\smbserver\path; this can be scripted) and ran Ghost 9 from the menu, and did it all through unicast. Again, after it finished I simply removed the CD and reboot and it would rename itself and come up to the login prompt. The big difference is that it was unicast instead of multicast and I therefore didn't need my server to be on the same subnet. (In theory it didn't anyway, but the volume of multicast network traffic would cause some trouble on the core of the network if it had to be routed. This was somebody else's department, I was just following orders in never doing that.)
Set up an Active Directory and lock down the various account types through that (my recommendation is a Student group, possibly with other subgroups for particular classes, a Teacher group, and an Administrator group. Give students their own accounts with passwords that they mu
Actually, Verizon is getting ready to launch a version of this phone intended for the elderly as well. I understand that it has the same reduced-buttons face, but it comes in less childish colors. I don't know whether they changed the form factor any.
I'm sorry that I can't provide a link or evidence; this is just something I learned from a Verizon saleslady.
Not true.
There are QOS issues that Ethernet cannot possibly guarantee. With token ring, on a fully loaded network, you are GUARANTEED to receive the token and therefore be able to send data with a certain frequency. Therefore, if you have data that MUST be sent and received with certain maximum delay characteristics, Token Ring wins hands down. Ethernet simply cannot guarantee anything of the sort. Switches reduce collisions, but if there is an upstream link in the design, you can still overflow the buffers if you have enough data to overload that link's capacity.
Admittedly, these are extremely rare requirements, but they do arise.
Also, as somebody had mentioned in a previous post, FDDI is an advanced version of Token Ring, with dual rings (running opposite directions) in the event that one segment is cut. The second ring passes data backwards to the last node before the cut, therefore replacing the cut segment at the cost of a slight delay increase, but as traffic on this ring is not processed by any node except the last, delay is extremely minimal.
As far as network engineers learning token ring, it is covered by Cisco's CCNA exam, and probably some of the professional-level exams too, but pretty much just as an archaic technology. It works, here's how it works, here are the pros and cons, but use something else.
So you're going to emulate the NES through Windows Media Player running through an emulated XBox360 running on a supercomputer. You know, there are NES emulators that run just fine on well-below-average computers now. Of course, when the Revolution comes out, you can do it legally, and without all the messiness of running emulators inside of emulators.
Why don't you test it out? Put a line of it on a piece of waxed paper and check the resistance. Remember that the thicker you lay it on, the less resistance per unit of length, assuming that it is conductive, so your number isn't going to be usable in calculations using this method, but it'll tell you HOW conductive it is.
Don't forget the whole not having media thing. If I'm paying as much as for a DVD, why would I not want to have the actual disc that I could carry to a friend's house, or wherever?
Actually, we're clean on Ghost too, AFAIK. They're using 8 and 9 IIRC, so the license you read doesn't necessarily apply. I haven't read the license, but like I mentioned, the Procurement guy does so far as I can tell. I'm sure they'd have bought a site license if that was necessary. I don't know the exact terms, but as careful as they are about everything else, I sincerely doubt that something on that order could have slipped through the cracks.
I don't know the details, but the Desktop Infrastructure guys set up a nifty little perl script that would unjoin the computer from the domain, rename it based on a database entry (the same database the DNS servers use, I believe) and rejoin it to the domain. Like I said, I don't know details, but it worked great. I just ran the script before making the image and it would unjoin. The next time that computer or any created with its image booted up, it would remane itself and rejoin the domain. (It took 3 reboots to complete this, one after unjoining, one after renaming, and one after rejoining, but it still beats doing it manually on 7-55 computers at a time, depending on which lab.)
Sassafras Keyserver is a good way to have a program installed on more systems than it is licensed for but only allow the licensed number to be run concurrently. I don't know details, but they can probably be found on the http://www.sassafras.com/ website.
From the site: Regardless of the type of licenses you need to manage, when properly configured, K2 will always keep usage within legal limits. You can set it and forget it. K2 does the rest. You can predict future software demand and purchase only what your organization needs. You can even reclaim lost or abandoned software, and prevent the need to purchase replacement software.
It is legal. Windows was volume licensed, meaning only one key for all the PCs on campus, and the software was either site licensed or only installed in the labs for which we had licenses. Ghost isn't installed everywhere, only on the bootable CDs, so the number of machines isn't an issue.
The procurement guy kept track of all the licenses (and actually read the EULAs as far as I can tell.) I'd have to go to him if I wasn't sure if we had enough licenses to satisfy a request, or if I thought there was a chance that what a professor or TA was requesting wasn't legal.
Slashdot Mirror
O(log(N)) for insertion, but that only occurs when a new task is created. The scheduler's complexity would be calculated based on how long it takes to choose what process to allow to execute next.
Given the new info that the furnace is going in after the IDF, which must then be retrofit, this is probably the best option yet. Your equipment in this location is NOT going to last, so get another unit set up before the current one fails. You'll wind up spending less time and money in the long run by far. Although geeks do make miracles happen every day, there's a cost-benefit analysis to consider. It sounds to me like you have four options:
...good luck regardless what you decide.
1) Put the furnace elsewhere
2) Put the IDF elsewhere
3) Prepare to lose IDF components frequently, causing issues with stability of both your network and your budget.
4) Spend more to insulate, cool, and protect the IDF than the cost of a relocated one
If you can come up with and implement a valid 5, I'd be interested to see what it is. The problem with this is that it will probably wind up being a combination of 4 and 3, with a final result of #2.
STP, if installed right, will lessen interference, but fiber will eliminate it entirely. The OP was right to go with fiber, given that they had the budget for it.
Another option targeted to the tailgater behind you:
"Please don't squish the Mini."
Or to the slow driver in front:
"Hurry up before I drive this thing up your tailpipe!"
MINI is calling them Motorboards, not Motherboards. The article is incorrect.
Actually, the check box there is labelled "Install QuickTime icon in the system tray"
There's a difference between loading the program and showing the icon. Unless Apple mislabeled the box, they need to add a second box. Otherwise they need to fix the label. Either way, if anyone knows I'd appreciate an informed response.
Keeping the temperature up in an abandoned house is important to prevent such catastrophies as freezing pipes. Plus it's not exactly a great idea to allow appliances to be exposed to sustained extreme temperatures (either hot or cold)
Freezing pipes can generally be prevented by shutting off the water at the entrance to the house, but as there are many things in houses which are designed to be kept at room temperature, it's usually considered best to keep them at a lowered room temperature. You also have things like the goosenecks in drain pipes that can't be emptied, and if you did (or if they burst) would create a real mess. Ever smelled a drain pipe where the gooseneck has dried out? You don't want to come back to a house that's been sitting like that.
As for electricity, you need that to run most thermostats, even if the heater is propane or natural gas. Additionally many people set timers for lights when they leave for an extended period in order to make the house appear occupied in an attempt to dissuade burglars. These simple timers have no batteries (at least the ones I've seen) and therefore lose time should the power go out. If it is out for under an hour, no big deal, or multiples of 24 hours would leave it where it was, but you don't want your lights going on in the morning and off mid-day.
I think I know a thing or two about this subject as I managed the computer labs at a university for about nine months. That was something like 900 machines in 35 labs as I recall.
Start over with a clean install of XP Pro on one machine. (which gives far better manageability than Home; If you don't have remote desktop or gpedit you'll miss them.) Install all of the programs, plugins, etc that you will need.
Run gpedit, the group policy editor. You can lock them down by making such restrictions as removing Run... from the Start menu, disallowing the ability to lock the computer, even removing the ability to change the preferences in IE. It's surprisingly user-friendly for the control that it provides. I used this to lock down the kiosks and other public access systems, leaving very little for users to do. They could run the few programs that I left for them (IE, FireFox, and a few other specific programs) and not do much else. They couldn't change preferences, no Run dialog, no right-click menu on the desktop, no way to save anything, or even see the hard drives, for that matter. You do need to leave yourself a back door, however (i.e. allow cmd to be run from a desktop icon which is only installed in one admin account, so that you can run gpedit again to remove restrictions.)
Use Norton Ghost to create an image of the hard drive and distribute it to the other machines. (They do have identical hardware, correct? If not, there is a way to use sysprep to remove the drivers before creating the image, but I have never done this.) You will want to create a script to rename the machines based on a DNS entry or other network database as a source, using the MAC address as a unique ID. I suppose you could rename them all manually, but since it requires two reboots, it could be a rather time-consuming process.
Ghost is great. Well worth the license fee for a setup like a highschool. You can make a change on one machine and distribute that new hard drive image to all the other machines. My process was: remove a machine from the lab in question, put the old ghost image back on it (to remove any corruption introduced since it was last imaged), update Windows and McAfee, make the change, begin the rename cycle, create a new ghost image, and finally distribute the image to the lab. It took a couple of hours (more or less depending on image size and network speed), but every time I did it, it was as if I had just reinstalled Windows and every other program on every machine in the lab. Just try installing 35 copies of Windows, Office, FireFox, Adobe, JRE, and 30-50 other programs in a few hours using any other system! I had a laptop to use as a Ghostcast server and a set of CDs to boot each system with. I simply had to set up the laptop as a server on that lab's subnet, boot each system to the CD (Bart PE -- Live CD of XP) which would automatically run Ghost and connect to the server. I start the distribution from the server and when it finishes, eject each CD, and reboot the systems. They rename themselves and return to the XP login screen. Nothing to it!
My alternate method was a different Bart PE CD from which I mapped my images share (net use s: \\smbserver\path; this can be scripted) and ran Ghost 9 from the menu, and did it all through unicast. Again, after it finished I simply removed the CD and reboot and it would rename itself and come up to the login prompt. The big difference is that it was unicast instead of multicast and I therefore didn't need my server to be on the same subnet. (In theory it didn't anyway, but the volume of multicast network traffic would cause some trouble on the core of the network if it had to be routed. This was somebody else's department, I was just following orders in never doing that.)
Set up an Active Directory and lock down the various account types through that (my recommendation is a Student group, possibly with other subgroups for particular classes, a Teacher group, and an Administrator group. Give students their own accounts with passwords that they mu
Actually, Verizon is getting ready to launch a version of this phone intended for the elderly as well. I understand that it has the same reduced-buttons face, but it comes in less childish colors. I don't know whether they changed the form factor any.
I'm sorry that I can't provide a link or evidence; this is just something I learned from a Verizon saleslady.
It's not so odd after all. The complaints are sent out of band.
Not true. There are QOS issues that Ethernet cannot possibly guarantee. With token ring, on a fully loaded network, you are GUARANTEED to receive the token and therefore be able to send data with a certain frequency. Therefore, if you have data that MUST be sent and received with certain maximum delay characteristics, Token Ring wins hands down. Ethernet simply cannot guarantee anything of the sort. Switches reduce collisions, but if there is an upstream link in the design, you can still overflow the buffers if you have enough data to overload that link's capacity. Admittedly, these are extremely rare requirements, but they do arise. Also, as somebody had mentioned in a previous post, FDDI is an advanced version of Token Ring, with dual rings (running opposite directions) in the event that one segment is cut. The second ring passes data backwards to the last node before the cut, therefore replacing the cut segment at the cost of a slight delay increase, but as traffic on this ring is not processed by any node except the last, delay is extremely minimal.
As far as network engineers learning token ring, it is covered by Cisco's CCNA exam, and probably some of the professional-level exams too, but pretty much just as an archaic technology. It works, here's how it works, here are the pros and cons, but use something else.
So you're going to emulate the NES through Windows Media Player running through an emulated XBox360 running on a supercomputer. You know, there are NES emulators that run just fine on well-below-average computers now. Of course, when the Revolution comes out, you can do it legally, and without all the messiness of running emulators inside of emulators.
It seems that he meant Nintendo, Sony, and Microsoft, but this is the first time I've ever heard of Microsoft in the same sentence as the word "holy."
Why don't you test it out? Put a line of it on a piece of waxed paper and check the resistance. Remember that the thicker you lay it on, the less resistance per unit of length, assuming that it is conductive, so your number isn't going to be usable in calculations using this method, but it'll tell you HOW conductive it is.
If he's got that kind of money, I don't think he'd be trying to save a little by computing his bankroll on his GPU.
Printed out, of course. File cabinets full. :-D
Sounds more like a job for light posts to me. Why do the sensors have to move? Couldn't they use stationary monitors more cost-effectively?
Don't forget the whole not having media thing. If I'm paying as much as for a DVD, why would I not want to have the actual disc that I could carry to a friend's house, or wherever?
Actually, we're clean on Ghost too, AFAIK. They're using 8 and 9 IIRC, so the license you read doesn't necessarily apply. I haven't read the license, but like I mentioned, the Procurement guy does so far as I can tell. I'm sure they'd have bought a site license if that was necessary. I don't know the exact terms, but as careful as they are about everything else, I sincerely doubt that something on that order could have slipped through the cracks.
I don't know the details, but the Desktop Infrastructure guys set up a nifty little perl script that would unjoin the computer from the domain, rename it based on a database entry (the same database the DNS servers use, I believe) and rejoin it to the domain. Like I said, I don't know details, but it worked great. I just ran the script before making the image and it would unjoin. The next time that computer or any created with its image booted up, it would remane itself and rejoin the domain. (It took 3 reboots to complete this, one after unjoining, one after renaming, and one after rejoining, but it still beats doing it manually on 7-55 computers at a time, depending on which lab.)
From the site:
Regardless of the type of licenses you need to manage, when properly configured, K2 will always keep usage within legal limits. You can set it and forget it. K2 does the rest. You can predict future software demand and purchase only what your organization needs. You can even reclaim lost or abandoned software, and prevent the need to purchase replacement software.
The procurement guy kept track of all the licenses (and actually read the EULAs as far as I can tell.) I'd have to go to him if I wasn't sure if we had enough licenses to satisfy a request, or if I thought there was a chance that what a professor or TA was requesting wasn't legal.