Search results for query: *

Well, Moregelen; as I'm sure you're aware...TLS is a Windows thing, not a MICROS thing. If by saying, your understanding is that "everything is on the system"; if you mean, newer systems staged by MICROS...then probably yes. Also...not everyone, by a long shot; uses a TVC driver. There's...

Really? Are we the only ones struggling with this?? We have 2 tests: howsmyssl and ssllabs. We've been getting some "splits", but putting more weight...on the ssllabs test. However...we still have some MICROS sites, with Host connectivity issues; rolling blackouts, etc. Our...

Before I start a duplicate; is there one, elsewhere...already? If not...I have questions; as I'm sure we all must have.

^^ Wow; really? 4LX?? [surprise]

Did just 5s...as opposed to 5As...stop being supported at some point? If so...what version?? Thanks,

OK; sorry for the dupe posts. But no one is going to look at those others anymore...and I really need to try and get an answer on this. I have a client...has RDCs with CE 6.0; and we've tried CE 5.0 Pro. Seems like CE 6.0 has embedded drivers, for ELO and StarTech; and 5.0 Pro has ELO (Touch)...

We usually use, the SySParms.

OK; no one is touching, my RDC w/IoT thread...so I'll piggy-back here, lol :) Need to "re-image"...KDS. In one case...just now; I have a customer, who got zapped and can't get to CE...so we can wipe and re-load CAL, etc. In the other case...we need to "copy" image, from other RDCs; onto new...

Wow; no one wants to touch this one, huh?? [sad]

OK...let me try and re-phrase, and/or elaborate on our question here: To put it simply...IMO; there are 3 versions of the RDC out there. The "old old" one, is CE and has limited T/S driver compatibility; the "newer old" is POSReady or CE Pro...and has more flexibility, to run off-the-shelf T/S...

Sorry if this sounds dumb...and/or has been covered. We ordered a customer, new RDCs...and discovered 7/POSReady, has been replaced by 10/IoT. We've discovered, it's like a win32 client. Should we even fiddle, with trying to get it to work with a Win7 BOPC Server/RES 5.1 set-up; or will it be...

...that MLI warns about (have to check, with my Elavon guy on that). I'll stop there for now...as that's plenty, to get the ball rolling; but I guess I'm just wondering: what the h*ll, are you guys doing? LOL Oh, P.S. For the record; there is NO integrated solution, for e7...correct? Thanks,

Good idea.

It's what's called, an alignment issue. It's why you should always...but especially with MyMICROS...create a new Menu Item, as opposed to writing-over an old one. MyMICROS alignments are not easy (not something, an end-user can really do MO). If you don't have a support contract, do you have a...

Can it? I know "in the day", Rochelle boxes were the only solution...and they only worked, with analog lines.

That's them...lol. Sorry we didn't get to it in time.

Well...I've had other programmers tell me it doesn't make a difference; but I've had it work so... You've still got TransactionVault drivers (TVCA/TVCS), even though you're on Heartland now (HLS). I'd triple-check, which driver is current; make sure all CCs are linked to the correct one...then...

Yeah; if the Menu Items in question...all have 'Food Prep' linked, as an Allowed Condiment. There must be something wrong, with the set-up...of the 'Food Preps' themselves.

I'd rotate your 3700d log, try running a settle; and see if the error leads you anywhere.

What Win are you running on? If 7 Pro, first thing I'd check...is the binding order of your NICs.