Create account / Log in

Socket Error

Issues with the Vassal engine.

Moderators: Tim M, uckelman

Re: Socket Error

Postby Cundiff » September 10th, 2018, 11:34 pm

A bigger problem is one caused by the failure to load a new module at all. When that happens Vassal simply refuses to do anything at all. I get a continuing Hour Glass that just sits there. To test to see if this was a time related thing I just completed a 2 hour run in which I attempted to load a module and let the computer sit there "Trying" to load the module. After 2 hours the hour glass was still sitting there. Nothing had loaded, nothing had changed. And there is NO Error Log for that.
Cundiff
 
Posts: 66
Joined: January 3rd, 2017, 8:51 am

Re: Socket Error

Postby JoelCFC25 » September 11th, 2018, 2:00 pm

One relatively easy thing you could try that ends up being the root cause of a surprising number of problems is verify that you have the correct type of Java installed for your system architecture. To wit, there are both 32-bit and 64-bit versions of Windows, and you need the corresponding version of Java. I've lost track of how many people had errors that stemmed from having 32-bit Java running in a 64-bit version of Windows.

The other thing that occurs to me whenever I see socket errors is that there could be firewall and/or internet filtering software running with settings that are incorrectly blocking VASSAL to some degree. If you have software like that, try disabling it.
JoelCFC25
 
Posts: 471
Joined: October 12th, 2010, 5:15 pm
Location: Minnetrista, MN

Re: Socket Error

Postby uckelman » September 11th, 2018, 4:09 pm

Thus spake Cundiff:
> Here it is again:
>
> java.util.concurrent.ExecutionException: java.io.IOException: return
> value == 1
> at java.util.concurrent.FutureTask.report(Unknown Source)
> at java.util.concurrent.FutureTask.get(Unknown Source)
> at org.jdesktop.swingworker.SwingWorker.get(Unknown Source)
> at

That's the exception stacktrace, not the complete errorLog.

http://www.vassalengine.org/wiki/Error_Logs

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8041
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: Socket Error

Postby Cundiff » September 12th, 2018, 12:27 am

Ok, here's the complete Error Log:

2018-09-10 19:29:53,700 [0-main] INFO VASSAL.launch.StartUp - Starting
2018-09-10 19:29:53,700 [0-main] INFO VASSAL.launch.StartUp - OS Windows Vista 6.0
2018-09-10 19:29:53,700 [0-main] INFO VASSAL.launch.StartUp - Java version 1.8.0_111
2018-09-10 19:29:53,700 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.17
2018-09-10 19:29:53,981 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2018-09-10 19:30:49,626 [0-SwingWorker-pool-26611018-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module file C:\Users\Customer\Downloads\Anthon\l'Epee de Anthon.vmod
2018-09-10 19:30:50,203 [0-SwingWorker-pool-26611018-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\Java\jre1.8.0_111\bin\java -classpath lib\Vengine.jar -Xmx394M -DVASSAL.id=2 -Duser.home=C:\Users\Customer -DVASSAL.port=53088 VASSAL.tools.image.tilecache.ZipFileImageTiler C:\Users\Customer\Downloads\Anthon\l'Epee de Anthon.vmod C:\Users\Customer\AppData\Roaming\VASSAL\tiles\743044e59383d4eecb128f15d23286b02c1243d4 256 256
2018-09-10 19:30:52,216 [2-main] INFO VASSAL.tools.image.tilecache.ZipFileImageTiler - Starting
2018-09-10 19:30:52,497 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/01.PNG
2018-09-10 19:30:52,824 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/02.PNG
2018-09-10 19:30:53,027 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/03.PNG
2018-09-10 19:30:53,152 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/04.PNG
2018-09-10 19:30:53,261 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/05.PNG
2018-09-10 19:30:53,386 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/06.PNG
2018-09-10 19:30:53,511 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/07.PNG
2018-09-10 19:30:53,635 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/08a.PNG
2018-09-10 19:30:53,791 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/09.PNG
2018-09-10 19:30:53,901 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/10.PNG
2018-09-10 19:30:54,010 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/11.PNG
2018-09-10 19:30:54,119 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/12.PNG
2018-09-10 19:30:54,259 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/13.PNG
2018-09-10 19:30:54,400 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/14.PNG
2018-09-10 19:30:54,587 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/15.PNG
2018-09-10 19:30:54,712 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/16.PNG
2018-09-10 19:30:54,837 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/17.PNG
2018-09-10 19:30:54,961 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/18.PNG
2018-09-10 19:30:55,117 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/19.PNG
2018-09-10 19:30:55,227 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/20.PNG
2018-09-10 19:30:55,351 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/21.PNG
2018-09-10 19:30:55,492 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/22.PNG
2018-09-10 19:30:55,663 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/23.PNG
2018-09-10 19:30:55,804 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/24.PNG
2018-09-10 19:30:55,929 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/26.PNG
2018-09-10 19:30:56,053 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/Anthon Map RESIZED.PNG
2018-09-10 19:30:57,582 [2-main] INFO VASSAL.tools.image.tilecache.ZipFileImageTiler - Exiting
2018-09-10 19:30:57,598 [2-main] ERROR VASSAL.tools.image.tilecache.ZipFileImageTiler - main
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Unknown Source) ~[na:1.8.0_111]
at java.io.ByteArrayOutputStream.grow(Unknown Source) ~[na:1.8.0_111]
at java.io.ByteArrayOutputStream.ensureCapacity(Unknown Source) ~[na:1.8.0_111]
at java.io.ByteArrayOutputStream.write(Unknown Source) ~[na:1.8.0_111]
at VASSAL.tools.io.RereadableInputStream.read(RereadableInputStream.java:107) ~[Vengine.jar:na]
at java.io.DataInputStream.readFully(Unknown Source) ~[na:1.8.0_111]
at java.io.DataInputStream.readFully(Unknown Source) ~[na:1.8.0_111]
at VASSAL.tools.image.PNGDecoder.decodeChunk(PNGDecoder.java:77) ~[Vengine.jar:na]
at VASSAL.tools.image.ImageIOImageLoader.load(ImageIOImageLoader.java:282) ~[Vengine.jar:na]
at VASSAL.tools.image.tilecache.FileArchiveImageTiler.run(FileArchiveImageTiler.java:77) ~[Vengine.jar:na]
at VASSAL.tools.image.tilecache.ZipFileImageTiler.main(ZipFileImageTiler.java:173) ~[Vengine.jar:na]
2018-09-10 19:30:58,487 [0-AWT-EventQueue-0] ERROR VASSAL.tools.ProblemDialog -
java.util.concurrent.ExecutionException: java.io.IOException: return value == 1
at java.util.concurrent.FutureTask.report(Unknown Source) ~[na:1.8.0_111]
at java.util.concurrent.FutureTask.get(Unknown Source) ~[na:1.8.0_111]
at org.jdesktop.swingworker.SwingWorker.get(Unknown Source) ~[swing-worker-1.2.jar:na]
at VASSAL.launch.AbstractLaunchAction$LaunchTask.done(AbstractLaunchAction.java:604) ~[Vengine.jar:na]
at VASSAL.launch.Player$LaunchAction$1.done(Player.java:188) [Vengine.jar:na]
at org.jdesktop.swingworker.SwingWorker$5.run(Unknown Source) [swing-worker-1.2.jar:na]
at org.jdesktop.swingworker.SwingWorker$DoSubmitAccumulativeRunnable.run(Unknown Source) [swing-worker-1.2.jar:na]
at org.jdesktop.swingworker.AccumulativeRunnable.run(Unknown Source) [swing-worker-1.2.jar:na]
at org.jdesktop.swingworker.SwingWorker$DoSubmitAccumulativeRunnable.actionPerformed(Unknown Source) [swing-worker-1.2.jar:na]
at javax.swing.Timer.fireActionPerformed(Unknown Source) [na:1.8.0_111]
at javax.swing.Timer$DoPostEvent.run(Unknown Source) [na:1.8.0_111]
at java.awt.event.InvocationEvent.dispatch(Unknown Source) [na:1.8.0_111]
at java.awt.EventQueue.dispatchEventImpl(Unknown Source) [na:1.8.0_111]
at java.awt.EventQueue.access$500(Unknown Source) [na:1.8.0_111]
at java.awt.EventQueue$3.run(Unknown Source) [na:1.8.0_111]
at java.awt.EventQueue$3.run(Unknown Source) [na:1.8.0_111]
at java.security.AccessController.doPrivileged(Native Method) [na:1.8.0_111]
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) [na:1.8.0_111]
at java.awt.EventQueue.dispatchEvent(Unknown Source) [na:1.8.0_111]
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) [na:1.8.0_111]
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) [na:1.8.0_111]
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) [na:1.8.0_111]
at java.awt.WaitDispatchSupport$2.run(Unknown Source) [na:1.8.0_111]
at java.awt.WaitDispatchSupport$4.run(Unknown Source) [na:1.8.0_111]
at java.awt.WaitDispatchSupport$4.run(Unknown Source) [na:1.8.0_111]
at java.security.AccessController.doPrivileged(Native Method) [na:1.8.0_111]
at java.awt.WaitDispatchSupport.enter(Unknown Source) [na:1.8.0_111]
at java.awt.Dialog.show(Unknown Source) [na:1.8.0_111]
at java.awt.Component.show(Unknown Source) [na:1.8.0_111]
at java.awt.Component.setVisible(Unknown Source) [na:1.8.0_111]
at java.awt.Window.setVisible(Unknown Source) [na:1.8.0_111]
at java.awt.Dialog.setVisible(Unknown Source) [na:1.8.0_111]
at VASSAL.launch.TilingHandler$3.run(TilingHandler.java:267) [Vengine.jar:na]
at java.awt.event.InvocationEvent.dispatch(Unknown Source) [na:1.8.0_111]
at java.awt.EventQueue.dispatchEventImpl(Unknown Source) [na:1.8.0_111]
at java.awt.EventQueue.access$500(Unknown Source) [na:1.8.0_111]
at java.awt.EventQueue$3.run(Unknown Source) [na:1.8.0_111]
at java.awt.EventQueue$3.run(Unknown Source) [na:1.8.0_111]
at java.security.AccessController.doPrivileged(Native Method) [na:1.8.0_111]
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) [na:1.8.0_111]
at java.awt.EventQueue.dispatchEvent(Unknown Source) [na:1.8.0_111]
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) [na:1.8.0_111]
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) [na:1.8.0_111]
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) [na:1.8.0_111]
at java.awt.EventDispatchThread.pumpEvents(Unknown Source) [na:1.8.0_111]
at java.awt.EventDispatchThread.pumpEvents(Unknown Source) [na:1.8.0_111]
at java.awt.EventDispatchThread.run(Unknown Source) [na:1.8.0_111]
Caused by: java.io.IOException: return value == 1
at VASSAL.launch.TilingHandler.runSlicer(TilingHandler.java:306) ~[Vengine.jar:na]
at VASSAL.launch.TilingHandler.sliceTiles(TilingHandler.java:375) ~[Vengine.jar:na]
at VASSAL.launch.AbstractLaunchAction$LaunchTask.doInBackground(AbstractLaunchAction.java:281) ~[Vengine.jar:na]
at VASSAL.launch.AbstractLaunchAction$LaunchTask.doInBackground(AbstractLaunchAction.java:244) ~[Vengine.jar:na]
at org.jdesktop.swingworker.SwingWorker$1.call(Unknown Source) ~[swing-worker-1.2.jar:na]
at java.util.concurrent.FutureTask.run(Unknown Source) ~[na:1.8.0_111]
at org.jdesktop.swingworker.SwingWorker.run(Unknown Source) ~[swing-worker-1.2.jar:na]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[na:1.8.0_111]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[na:1.8.0_111]
at java.lang.Thread.run(Unknown Source) ~[na:1.8.0_111]
2018-09-10 19:41:14,148 [1-AWT-EventQueue-0] WARN VASSAL.launch.BasicModule - Hastings AFDE version 1.0
2018-09-10 19:41:14,560 [1-AWT-EventQueue-0] INFO VASSAL.build.GameModule - Exiting
2018-09-10 19:41:14,612 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream - java.net.SocketException: Connection reset by peer: socket write error
2018-09-10 19:41:14,612 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-10 19:41:14,613 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.SocketOutputStream.socketWrite0(Native Method)
2018-09-10 19:41:14,613 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-10 19:41:14,613 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.SocketOutputStream.socketWrite(Unknown Source)
2018-09-10 19:41:14,613 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-10 19:41:14,613 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.SocketOutputStream.write(Unknown Source)
2018-09-10 19:41:14,613 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-10 19:41:14,614 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream - at java.io.ObjectOutputStream$BlockDataOutputStream.drain(Unknown Source)
2018-09-10 19:41:14,614 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-10 19:41:14,614 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream - at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Unknown Source)
2018-09-10 19:41:14,614 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-10 19:41:14,614 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream - at java.io.ObjectOutputStream.writeNonProxyDesc(Unknown Source)
2018-09-10 19:41:14,615 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-10 19:41:14,615 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream - at java.io.ObjectOutputStream.writeClassDesc(Unknown Source)
2018-09-10 19:41:14,615 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-10 19:41:14,615 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream - at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)
2018-09-10 19:41:14,615 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-10 19:41:14,615 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream - at java.io.ObjectOutputStream.writeObject0(Unknown Source)
2018-09-10 19:41:14,615 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-10 19:41:14,616 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream - at java.io.ObjectOutputStream.writeFatalException(Unknown Source)
2018-09-10 19:41:14,617 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-10 19:41:14,617 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream - at java.io.ObjectOutputStream.writeObject(Unknown Source)
2018-09-10 19:41:14,617 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-10 19:41:14,617 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream - at VASSAL.tools.ipc.IPCMessageDispatcher.run(IPCMessageDispatcher.java:26)
2018-09-10 19:41:14,618 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-10 19:41:14,618 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream - at java.lang.Thread.run(Unknown Source)
2018-09-10 19:41:14,618 [1-IPC dispatcher for 4380597] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-10 19:58:45,473 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManagerWindow - Exiting
Cundiff
 
Posts: 66
Joined: January 3rd, 2017, 8:51 am

Re: Socket Error

Postby Cundiff » September 12th, 2018, 12:33 am

I have Avast Free Antivirus. I cannot find the firewall. I'd make a guess it doesn't exist.

Now about Java. I am unable to access the Java update to discover this. I'm not a computer guru, so I'm rather out of my realm on this.

I'm running Vista. I search online to discover how to find this, but they all make reference to places that do not exist on my computer.
Cundiff
 
Posts: 66
Joined: January 3rd, 2017, 8:51 am

Re: Socket Error

Postby Cundiff » September 12th, 2018, 10:51 am

Have found the currently installed Java

Java Version 8 update 111 (build 1.8.0_111-b14)

Cannot find a means to update it.
Cundiff
 
Posts: 66
Joined: January 3rd, 2017, 8:51 am

Re: Socket Error

Postby Brent Easton » September 12th, 2018, 11:52 am

The key is on the first line of the error message:

java.lang.OutOfMemoryError: Java heap space


The Maximum Java Heap size recorded in the preferences file for this module (394Mb) is too small and causing the load to crash. Normally you adjust this preference once the module is loaded, but because you cannot load the module, you will have to edit the preference file and update it in there. Unfortunately, once the heap is set too low, you often can't change it through Vassal.

On a windows system, the preferences are stored in the folder

C:\Users\<user>\AppData\Roaming\VASSAL\prefs

where <user> is your windows account name. Edit the file with your module's name with any text editor and change the line that reads

maximumHeap=512

to (say)

maximumHeap=1024

Regards.
User avatar
Brent Easton
 
Posts: 2743
Joined: December 21st, 2007, 3:06 am
Location: Berry, NSW, Australia

Re: Socket Error

Postby Cundiff » September 12th, 2018, 1:03 pm

This works fine for already loaded modules. What do I do about new modules that refuse to load? They just hang up while tiling and crash. They never load.
Cundiff
 
Posts: 66
Joined: January 3rd, 2017, 8:51 am

Re: Socket Error

Postby Cundiff » September 12th, 2018, 1:45 pm

Ok, I have found where I can change the MaxHeap size to 1024 in the Module Preferences. Is this the maximum to which it can be changed?

I've still got a module that indicates the exact same problem. It hangs up at 23% and indicates a Socket problem, the same one as indicated previously, and the one which began this saga.
Cundiff
 
Posts: 66
Joined: January 3rd, 2017, 8:51 am

Re: Socket Error

Postby JoelCFC25 » September 12th, 2018, 3:17 pm

Keep adjusting it higher, though you are going to be limited by the amount of RAM your computer has (and the operating system itself is going to consume some of that). For example, if you have 8 GB of RAM, try a max heap of 2048 (one quarter of your RAM). There will be some trial and error here.
JoelCFC25
 
Posts: 471
Joined: October 12th, 2010, 5:15 pm
Location: Minnetrista, MN

Re: Socket Error

Postby Cundiff » September 12th, 2018, 8:42 pm

Well, I'm limited. I have all of 3 Gb of Ram. Not much. So, I will have to repair that first.

I did manage to get Java Updated.

Thanks,
Tom
Cundiff
 
Posts: 66
Joined: January 3rd, 2017, 8:51 am

Re: Socket Error

Postby Cundiff » September 12th, 2018, 8:50 pm

Thanks Everyone

Tom
Cundiff
 
Posts: 66
Joined: January 3rd, 2017, 8:51 am

Re: Socket Error

Postby uckelman » September 13th, 2018, 11:08 pm

Thus spake Cundiff:
> VASSAL.launch.AbstractLaunchAction - Loading module file
> C:\Users\Customer\Downloads\Anthon\l'Epee de Anthon.vmod

Where can I find this module so I may test it?

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8041
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: Socket Error

Postby Cundiff » September 15th, 2018, 7:41 am

I'll have to send it to you. It's a situation in which the original module was based upon a scenario that had errors in it. I was attempting to rebuild the module by inserting a new map and new counters into the old module, replacing the old files which contained errors. There are several of the l'Epee modules whose original builds are based upon scenarios that later had Errata to correct errors. However, the designers of the modules never returned to correct the error laden modules. So, I've been attempting to make these repairs for Frederic Bey (the game designer).
Cundiff
 
Posts: 66
Joined: January 3rd, 2017, 8:51 am

Re: Socket Error

Postby uckelman » September 15th, 2018, 9:20 pm

Thus spake Cundiff:
> I'll have to send it to you.

Please do. My address is uckelman@nomic.net, or if the module is very
large, upload it somewhere and send me a link.

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8041
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

PreviousNext

Return to Technical Support & Bugs

Who is online

Users browsing this forum: No registered users and 0 guests