Re: SM is not accepted by Chase.com - again!

2018-04-01 Thread EE
cmcadams wrote: David E. Ross wrote: On 3/31/2018 11:23 AM, EE wrote: cmcadams wrote: Trying a user.js didn't work. prefs.js didn't wish to be changed...tried both Windows 7 Notepad and DOS Edit, but evidently didn't know the right save options, because after running SM the new entry

Re: SM is not accepted by Chase.com - again!

2018-04-01 Thread Ed Mullen
On 4/1/2018 at 1:05 AM, cmcadams created this epitome of digital genius: David E. Ross wrote: On 3/31/2018 6:49 PM, cmcadams wrote: David E. Ross wrote: On 3/31/2018 11:23 AM, EE wrote: cmcadams wrote: Trying a user.js didn't work. prefs.js didn't wish to be changed...tried both Windows 7

Re: SM is not accepted by Chase.com - again!

2018-04-01 Thread Ed Mullen
On 3/31/2018 at 2:38 PM, cmcadams created this epitome of digital genius: WaltS48 wrote: On 3/30/18 10:25 PM, cmcadams wrote: Ed Mullen wrote: On 3/30/2018 at 10:45 AM, Marisa Ciceran created this epitome of digital genius: As of about a week ago, when I log into my Chase accounts account

Re: SM is not accepted by Chase.com - again!

2018-04-01 Thread Daniel
cmcadams wrote on 01/04/18 15:27: David E. Ross wrote: On 3/31/2018 11:23 AM, EE wrote: cmcadams wrote: Trying a user.js didn't work. prefs.js didn't wish to be changed...tried both Windows 7 Notepad and DOS Edit, but evidently didn't know the right save options, because after running SM the

Re: SM video problems continue - will they ever end!?

2018-04-01 Thread null
IRRITATING SPAMMER wrote: null wrote: IRRITATING SPAMMER wrote: null wrote: Have had increasing problems playing video in SM for a long time now. Getting the latest SM version doesn't help. Seems it all stems from ongoing, behind-the-scenes jostling between flashplayer, WEBM and the HTML5

Re: SM is not accepted by Chase.com - again!

2018-04-01 Thread Ray_Net
Marisa Ciceran wrote on 30-03-18 16:45: As of about a week ago, when I log into my Chase accounts account using SM 2.49.2 on my Windows 7 desktop and laptops, it goes to the following page: https://m.chase.com/secure.html?newstoken=false=https%3A%2F%2Fm.chase.com%2Findex.html=success