Windows 7 Pro 32 bit - Low on Memory... Ideas?
-
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@jmoore said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs When was last time the machine was updated and restarted?
Restarting right now again - I found a JavaUpdater in the start up through
msconfigand disabled it.
We dont use Java from my knowledge and My boss even said just to disable it.Yeah, if that isn't needed, you definitely don't want it.
I dont see any reason it would be needed.
It was odd that it was there. -
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
This was bought years ago - they haven't updated because its rather expensive.
I get leaving things old, but is it actually older than 2005, or just messed up in 2005? 32bit is so old. Older than Windows 7. Windows 7 deployed as 32bit means a new OS on very old hardware. Windows 7 was 2010, 64bit was like 2003. 64bit came out in 2000, but we can excuse not deploying till about 2003. After that point, anything 32bit really has no excuse. So that would imply Windows 7 on hardware that is at a minimum seven years old, or just a total screw up.
And that's before addressing the lack of licensing which has nothing to do with age.
-
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
How is It not licensed ?
Because there is no license. Windows 7 can never be used like this. It's unlicensable as a server. It's that simple. This is just pirated.
The simple rule of thumb is "when you have a server, it has to have server licensing." There are really rare, special circumstances where that can be bypassed, but they are crazy specific and it's obvious when they apply (like it applies to file transfers to move files back and forth between machines.) Anytime someone says "we don't need a server, we'll just use a desktop for that", that's pirating.
This is one of the big reasons why Windows is so bad for this stuff. No matter how tiny or silly the install, you must pay for Windows Server licensing. So it makes even the tiniest task cost a lot of money both in licensing and effort to plan and deal with. Being "locked in" to Windows comes at a huge cost that whoever decided to use Aloha accepted when choosing that product. It's not good or bad, it's just the biggest piece of that decision. So someone accepted that Aloha has an ~$800 extra licensing fee for every deployment on top of the Aloha costs.
-
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
How is It not licensed ?
Because there is no license. Windows 7 can never be used like this. It's unlicensable as a server. It's that simple. This is just pirated.
What makes this a "server" in this case? Either I missed something or something else is being read into this.
It is pretty common in the point of service space for one register to play the role of "lead" and all other registers are slaves.
-
@donaldlandru said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
How is It not licensed ?
Because there is no license. Windows 7 can never be used like this. It's unlicensable as a server. It's that simple. This is just pirated.
What makes this a "server" in this case? Either I missed something or something else is being read into this.
It is pretty common in the point of service space for one register to play the role of "lead" and all other registers are slaves.
We use a file-server system environment - Maybe that's what he is meaning as "server"
I'm not sure, -
@donaldlandru said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
What makes this a "server" in this case? Either I missed something or something else is being read into this.
Really simple... it's running a database whose services are used by other machines. It's a by the book database server.
-
@donaldlandru said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
It is pretty common in the point of service space for one register to play the role of "lead" and all other registers are slaves.
Read: It is pretty common to commit piracy with POS deployments.
-
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
We use a file-server system environment - Maybe that's what he is meaning as "server"
You are using MS SQL Server. What does that exist for, if not to be a database server? If you turn it off, does nothing break?
-
If SQL Server is there for no function whatsoever, then it might not qualify as a server. But if that is the case, turn it off as that is certainly using a lot of resources that can't be afforded on such an ancient machine.
-
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
We use a file-server system environment - Maybe that's what he is meaning as "server"
You are using MS SQL Server. What does that exist for, if not to be a database server? If you turn it off, does nothing break?
We are using MS Sql Express - yes. It's needed for the database in New versions of Aloha manager.
If we turn it off, the point of sale doesnt get the changes made. -
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
We use a file-server system environment - Maybe that's what he is meaning as "server"
You are using MS SQL Server. What does that exist for, if not to be a database server? If you turn it off, does nothing break?
We are using MS Sql Express - yes. It's needed for the database in New versions of Aloha manager.
If we turn it off, the point of sale doesnt get the changes made.So you are running a database server that absolutely requires server licensing. Ergo, it's not licensed.
-
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
If SQL Server is there for no function whatsoever, then it might not qualify as a server. But if that is the case, turn it off as that is certainly using a lot of resources that can't be afforded on such an ancient machine.
The way new aloha manager works, from what I'm told- It breaks the changes down into the sql. Then it imports into the file folders and sends the change to the front of house.
SQL is needed for information to pass along to the front of house. -
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
We use a file-server system environment - Maybe that's what he is meaning as "server"
You are using MS SQL Server. What does that exist for, if not to be a database server? If you turn it off, does nothing break?
We are using MS Sql Express - yes. It's needed for the database in New versions of Aloha manager.
If we turn it off, the point of sale doesnt get the changes made.So you are running a database server that absolutely requires server licensing. Ergo, it's not licensed.
Okay.
You point these things out - however Point of Sales have been running like this for decades. Why was it not brought up prior. -
I'll go out on a limb and infer the if Oracle was directing people to pirate Microsoft licensing, Microsoft would be saying something about it.
With that said, Oracle Xstore is not even supported on Windows Server.
-
Using a Windows 7 (or 10) workstation for basic file serving is allowed in uselessly limited circumstances. That's one of the exceptions. But the limit is crazy low and not easy to explain. It is limited on connections, not users, and people always misstate it. It's useful only for the amount of connections needed to use a desktop in normal ways, the moment you try to use it even as a file server, it will generally go over the limits. But that gets into a grey area of "how can we tell how many connections?"
But that's not the case here. That would apply to software that simply shares a database file for an extremely limited number of workstations. Old QuickBooks, for example. But that system is so buggy and problematic, no viable software really still does that. They are all using databases and connection handling software now. Or should. (Example: AviMark vs. AviMark with Guardian. You can disable the server aspects of the system for fallback desktop licensing, but it makes the product a total dog.)
So even products that have traditionally been able to be used in this way like AviMark or QuickBooks left that model years ago and now require Windows Server and CAL licensing to be able to deploy.
-
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
We use a file-server system environment - Maybe that's what he is meaning as "server"
You are using MS SQL Server. What does that exist for, if not to be a database server? If you turn it off, does nothing break?
We are using MS Sql Express - yes. It's needed for the database in New versions of Aloha manager.
If we turn it off, the point of sale doesnt get the changes made.So you are running a database server that absolutely requires server licensing. Ergo, it's not licensed.
Okay.
You point these things out - however Point of Sales have been running like this for decades. Why was it not brought up prior.Why is it just now coming up that this a problem with the way it's working?
Maybe I dont have enough information and you're piecing things together ?
what is it that I'm doing wrong exactly in my current position ? -
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
If SQL Server is there for no function whatsoever, then it might not qualify as a server. But if that is the case, turn it off as that is certainly using a lot of resources that can't be afforded on such an ancient machine.
The way new aloha manager works, from what I'm told- It breaks the changes down into the sql. Then it imports into the file folders and sends the change to the front of house.
SQL is needed for information to pass along to the front of house.Yup. A bit weird, but doesn't change that SQL Server is being used and is needed. That there is another connection process in between is just part of the API and neither here nor there in a licensing discussion.
-
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
We use a file-server system environment - Maybe that's what he is meaning as "server"
You are using MS SQL Server. What does that exist for, if not to be a database server? If you turn it off, does nothing break?
We are using MS Sql Express - yes. It's needed for the database in New versions of Aloha manager.
If we turn it off, the point of sale doesnt get the changes made.So you are running a database server that absolutely requires server licensing. Ergo, it's not licensed.
Okay.
You point these things out - however Point of Sales have been running like this for decades. Why was it not brought up prior.Because you didn't ask anyone prior. How would we know if you didn't tell us?
-
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
We use a file-server system environment - Maybe that's what he is meaning as "server"
You are using MS SQL Server. What does that exist for, if not to be a database server? If you turn it off, does nothing break?
We are using MS Sql Express - yes. It's needed for the database in New versions of Aloha manager.
If we turn it off, the point of sale doesnt get the changes made.So you are running a database server that absolutely requires server licensing. Ergo, it's not licensed.
Okay.
You point these things out - however Point of Sales have been running like this for decades. Why was it not brought up prior.Because you didn't ask anyone prior. How would we know if you didn't tell us?
Or maybe It's because I dont have the exact information and only telling you what I know - Is that possible?
-
@donaldlandru said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
I'll go out on a limb and infer the if Oracle was directing people to pirate Microsoft licensing, Microsoft would be saying something about it.
This has been the standard excuse people have always used and holds no water.
- In no way whatsoever is YOUR licensing requirements any of Oracle's concern or place to inform you anything. Zero, zip, nada. You are assuming a legal advisory role from them that no software vendor will ever make.
- Never, ever does Oracle tell you to pirate software. They inform you of which OSes they are willing to provide support. There is no relationship between that and what you are stating.
- Windows 7 is legal to use in this way in some jurisdictions where Oracle provides support and Microsoft does not have licensing rights (example: China, Bolivia, Cuba, Iran.)
- This is completely standard to state where it works and is tested, all vendors do this.
- Microsoft and Oracle have no relationship about this and Microsoft has zero right to say anything about it. You are assuming a legal position between them that does not exist.
- Licensing is between you and Microsoft. Oracle has no way to know what you have worked out and MS has every right to change licensing. Oracle would be insane to voluntarily try to police something they have no right or power to police.
- All liability for piracy and all moral obligation to not pirate is on the customer, Oracle is not part of the equation. The one and only person who has a responsibility for this is the customer choosing what licensing is needed.
- There ARE scenarios where you are allowed to use it in this way, such as single machine deployments, and development environments. Just because it is legal somewhere doesn't imply it is legal everywhere.
