JEPC (Jaguar Electronic Parts Catalogue) Graphics
#1
JEPC (Jaguar Electronic Parts Catalogue) Graphics
(see post #3 for the resolution of this issue)
With effect from 12 January 2021, members who use unofficial (offline) copies of JEPC will find all the graphics have been replaced by a Flash Player default:
Since Adobe is no longer supporting Flash Player after the EOL Date, Adobe will block Flash content from running in Flash Player beginning 12 January 2021 to help secure users’ systems. Flash Player may remain on the user’s system unless the user uninstalls it.
This effectively cripples JEPC. All the text remains accessible but without the supporting grapics, it is next to useless. Aftermarket suppliers who rely of Flash Player to support their online parts catalogues will also be affected.
JLR TOPIx, the Dealer portal to JEPC is shown today as having "no known issues".
This may mean JLR have a workaround for the official JEPC ......... or it could be they are not yet aware of the issue.
Graham
With effect from 12 January 2021, members who use unofficial (offline) copies of JEPC will find all the graphics have been replaced by a Flash Player default:
Since Adobe is no longer supporting Flash Player after the EOL Date, Adobe will block Flash content from running in Flash Player beginning 12 January 2021 to help secure users’ systems. Flash Player may remain on the user’s system unless the user uninstalls it.
This effectively cripples JEPC. All the text remains accessible but without the supporting grapics, it is next to useless. Aftermarket suppliers who rely of Flash Player to support their online parts catalogues will also be affected.
JLR TOPIx, the Dealer portal to JEPC is shown today as having "no known issues".
This may mean JLR have a workaround for the official JEPC ......... or it could be they are not yet aware of the issue.
Graham
Last edited by GGG; 02-26-2021 at 05:14 PM. Reason: Remove "RESOLVED" from thread title
Top Answer
01-14-2021, 07:48 AM
I don't know the rules on posting links to other forums so I'll post this here for everyone. I take no credit for the fix provided. It was found my MrKris on another jaguar forum with almost the exact URL as this one.
Method #1:
There may be a better solution using some sort of whitelist exception.....
Method #2:
USE This, it is the official way from the Adobe developers manual and much easier.
In short, you need to create a file called mms.cfg which should be located in the following directory, depending on operating system (if the directory does not exist, create it):
on Linux - /etc/adobe
on 64-bit Windows - C:\Windows\SysWow64\Macromed\Flash
on 32-bit Windows - C:\Windows\System32\Macromed\Flash
(of course if you installed Windows in a different directory than C:\Windows, change the paths appropriately)
on MacOS - /Library/Application Support/Macromedia
To allow local Flash content to run, you need to put in the mms.cfg file the following:
AllowListUrlPattern=file:///
You could also reference just the JEPC data folder if you prefer.
For Windows 10 users. Step by step
1. Open any documents folder
2. Right click and create new text file
3. Call that file mms (File would now be mms.txt in reality)
4. Click the view tab and then tick the option for See file name extensions
5. Now you can rename the file from mms.txt to mms.cfg
6. Copy this file to the location given above for your version of Windows.
Method #1:
- Copy this Flash directory (C:\WINDOWS\system32\Macromed\Flash for 32-bit, C:\Windows\SysWOW64\Macromed\Flash for 64-bit) to somewhere with write permission;
- Use a hex editor to open Flash.ocx;
- Search for the hexadecimal string 000040463E6F7742 (the timestamp) and replace it with 000000000000F87F;
- Save the file;
- Rename the original Flash directory to Flash.bak or something;
- Copy the Flash directory with the modified binary back to its original location as above.
There may be a better solution using some sort of whitelist exception.....
Method #2:
USE This, it is the official way from the Adobe developers manual and much easier.
In short, you need to create a file called mms.cfg which should be located in the following directory, depending on operating system (if the directory does not exist, create it):
on Linux - /etc/adobe
on 64-bit Windows - C:\Windows\SysWow64\Macromed\Flash
on 32-bit Windows - C:\Windows\System32\Macromed\Flash
(of course if you installed Windows in a different directory than C:\Windows, change the paths appropriately)
on MacOS - /Library/Application Support/Macromedia
To allow local Flash content to run, you need to put in the mms.cfg file the following:
AllowListUrlPattern=file:///
You could also reference just the JEPC data folder if you prefer.
For Windows 10 users. Step by step
1. Open any documents folder
2. Right click and create new text file
3. Call that file mms (File would now be mms.txt in reality)
4. Click the view tab and then tick the option for See file name extensions
5. Now you can rename the file from mms.txt to mms.cfg
6. Copy this file to the location given above for your version of Windows.
#2
Join Date: Apr 2008
Location: Ottawa, Ontario, Canada
Posts: 2,910
Received 1,192 Likes
on
832 Posts
lol... just in time for the EOL of flash. nice job guys.
Incidentally, I like your browser choice. I worked on mozilla in the mid ‘90s... Then on to Netscape.
(which I hope explains my affection for open standards and my distaste for proprietary add ons and extensions)
Incidentally, I like your browser choice. I worked on mozilla in the mid ‘90s... Then on to Netscape.
(which I hope explains my affection for open standards and my distaste for proprietary add ons and extensions)
Last edited by guy; 01-13-2021 at 08:45 AM.
The following users liked this post:
GGG (01-13-2021)
#3
I don't know the rules on posting links to other forums so I'll post this here for everyone. I take no credit for the fix provided. It was found my MrKris on another jaguar forum with almost the exact URL as this one.
Method #1:
There may be a better solution using some sort of whitelist exception.....
Method #2:
USE This, it is the official way from the Adobe developers manual and much easier.
In short, you need to create a file called mms.cfg which should be located in the following directory, depending on operating system (if the directory does not exist, create it):
on Linux - /etc/adobe
on 64-bit Windows - C:\Windows\SysWow64\Macromed\Flash
on 32-bit Windows - C:\Windows\System32\Macromed\Flash
(of course if you installed Windows in a different directory than C:\Windows, change the paths appropriately)
on MacOS - /Library/Application Support/Macromedia
To allow local Flash content to run, you need to put in the mms.cfg file the following:
AllowListUrlPattern=file:///
You could also reference just the JEPC data folder if you prefer.
For Windows 10 users. Step by step
1. Open any documents folder
2. Right click and create new text file
3. Call that file mms (File would now be mms.txt in reality)
4. Click the view tab and then tick the option for See file name extensions
5. Now you can rename the file from mms.txt to mms.cfg
6. Copy this file to the location given above for your version of Windows.
Method #1:
- Copy this Flash directory (C:\WINDOWS\system32\Macromed\Flash for 32-bit, C:\Windows\SysWOW64\Macromed\Flash for 64-bit) to somewhere with write permission;
- Use a hex editor to open Flash.ocx;
- Search for the hexadecimal string 000040463E6F7742 (the timestamp) and replace it with 000000000000F87F;
- Save the file;
- Rename the original Flash directory to Flash.bak or something;
- Copy the Flash directory with the modified binary back to its original location as above.
There may be a better solution using some sort of whitelist exception.....
Method #2:
USE This, it is the official way from the Adobe developers manual and much easier.
In short, you need to create a file called mms.cfg which should be located in the following directory, depending on operating system (if the directory does not exist, create it):
on Linux - /etc/adobe
on 64-bit Windows - C:\Windows\SysWow64\Macromed\Flash
on 32-bit Windows - C:\Windows\System32\Macromed\Flash
(of course if you installed Windows in a different directory than C:\Windows, change the paths appropriately)
on MacOS - /Library/Application Support/Macromedia
To allow local Flash content to run, you need to put in the mms.cfg file the following:
AllowListUrlPattern=file:///
You could also reference just the JEPC data folder if you prefer.
For Windows 10 users. Step by step
1. Open any documents folder
2. Right click and create new text file
3. Call that file mms (File would now be mms.txt in reality)
4. Click the view tab and then tick the option for See file name extensions
5. Now you can rename the file from mms.txt to mms.cfg
6. Copy this file to the location given above for your version of Windows.
The following 10 users liked this post by MoJo88:
DaveAllen (11-11-2022),
Elskan (03-08-2021),
FerrariGuy (09-18-2021),
GGG (01-14-2021),
kj07xk (01-17-2021),
and 5 others liked this post.
The following users liked this post:
Aarcuda (01-21-2021)
#5
#8
Thanks for the fix. Not sure what the issue is but method 2 didn't work for me on my Windows 10 laptop.
The file already existed in C:\Windows\SysWOW64\Macromed\Flash so I just put AllowListUrlPattern=file:/// at the end of it. That didn't works so I also tried just having that entry in it.
I definitely had the right directory because renaming the directory stopped the flash icon appearing at all in JEPC.
In the end I went with option 1 and used the online hex editor at https://hexed.it/ to change the file.
Changing the system date to last year also worked but that would be a pain to do each time I used JEPC.
The file already existed in C:\Windows\SysWOW64\Macromed\Flash so I just put AllowListUrlPattern=file:/// at the end of it. That didn't works so I also tried just having that entry in it.
I definitely had the right directory because renaming the directory stopped the flash icon appearing at all in JEPC.
In the end I went with option 1 and used the online hex editor at https://hexed.it/ to change the file.
Changing the system date to last year also worked but that would be a pain to do each time I used JEPC.
#9
Hmmm, looks like it might be Flashplayer version related. My laptop is running 32.0.0.387 which is mentioned as exhibiting the same issues here:
https://stackoverflow.com/questions/...s-cfg-settings
Earlier versions used different keywords.
I have reverted back and retested and WhitelistUrlPattern=file:/// works on my laptop.
https://stackoverflow.com/questions/...s-cfg-settings
Earlier versions used different keywords.
I have reverted back and retested and WhitelistUrlPattern=file:/// works on my laptop.
Last edited by u102768; 01-16-2021 at 09:10 PM.
The following users liked this post:
V7Sport (01-17-2021)
#17
Method #2:
In short, you need to create a file called mms.cfg which should be located in the following directory, depending on operating system (if the directory does not exist, create it):
on 64-bit Windows - C:\Windows\SysWow64\Macromed\Flash
on 32-bit Windows - C:\Windows\System32\Macromed\Flash
(of course if you installed Windows in a different directory than C:\Windows, change the paths appropriately)
on MacOS - /Library/Application Support/Macromedia
#19
#20
ya the instructions are a lil confusing to the non computer crowd.
I already had the file listed in the directory you posted so I didnt need to create it. You want to open it with notepad. The file lacked the AllowListUrlPattern=file:/// instruction but after adding the instruction to the end of the file, it said I didnt have permission to save it So I had to right click on the file name and select properties and change the PERMISSIONS for ......./users under the Security tab under Properties to allow WRITE.
Then you can save it
I already had the file listed in the directory you posted so I didnt need to create it. You want to open it with notepad. The file lacked the AllowListUrlPattern=file:/// instruction but after adding the instruction to the end of the file, it said I didnt have permission to save it So I had to right click on the file name and select properties and change the PERMISSIONS for ......./users under the Security tab under Properties to allow WRITE.
Then you can save it
The following users liked this post:
roman_mg (01-22-2021)