Access Violation

General comments and questions. Technical support.
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Access Violation

Post by patr »

I've been using Atlantis for a long time, but every now and then the program just clunks out and I have to reinstall it.

What starts happening is it errors out giving a "access violation" error. I knew where Atlantis stores its various files like ProgramData and AppData locations, so I wanted to see what file could be causing it to error out.

The way I went about doing this was deleting the various files in above locations until Atlantis would start up without error message again. It kept erroring out every time I tried to start it (either via starting up an associated file or starting up the program directly from shortcut), until I removed "awp.dat" in AppData\Roaming.

After I removed the above file, Atlantis started up normally again. My opinion is that this persistent (but strangely irregular) error is due to the awp.dat file somehow getting corrupted by Atlantis as it uses it. I don't know if Atlantis writes to this file or not, but as soon as I deleted that file Atlantis started normally (albeit without activation).

I mainly run Windows 7 x64, and this issue has come and gone quite a few times and over many fresh OS installs. I've tried to uninstall anything I thought could be interfering, and also killed some running processes I thought might be interfering, but nothing helped until I deleted awp.dat. There is something amiss here, no other program I use has such a problem. But Atlantis has had it many times over various Windows installs. This has been my experience.

I ended up making my personal installer for it so I can just double-click and overwrite and corrupted files and that fixes it also. But eventually I have this error again.

I hope this will finally get fixed properly.

Thanks,

patr
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

However, what is weird about it, is when I try to restore the old AppData files, I couldn't recreate the issue. But it definitely went away as soon as I deleted awp.dat.

It could be a combination of files from ProgramData and AppData being deleted, that made it so when I restored the AppData ones but other files at ProgramData were not there, that the error somehow resolved.

This is what makes this persistent error so elusive. It definitely has happened to me many times. I maintain updated images from Win7 to Win10, have all runtimes installed -- there are no botched OS installs on my end. I'm saying the OS situation couldn't be much better than it is and yet this error happens.

Something is amiss.
User avatar
admin
Site Admin
Posts: 2437
Joined: Wed Jun 05, 2002 10:48 pm
Contact:

Post by admin »

Deleting or modifying system files of Atlantis is not recommended.

If Atlantis displays an error when trying to open a document file, please email us that document file.

Otherwise please launch a "factory settings" copy of Atlantis by running the following command-line:

"C:\Program Files\Atlantis\awp.exe" -dls -dss

or

"C:\Program Files (x86)\Atlantis\awp.exe" -dls -dss

If it works correctly, the error is probably linked to your current Atlantis settings.
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

To be clear:

Atlantis has manifested this behavior both when merely opening the application itself (not via opening a document), as well as when opening a document. It is not any document that causes this in my case, in other words. I've never been able to reproduce the error merely by means of any document.

In my experience it is only erroring out on a document when starting up Atlantis by itself is producing the error. In other words, I've never had it error out on a document, but then the application itself starting up correctly. It is starting up the application (not via a document) that is associated with the error.

Again, in deleting program files one by one, it was only once I removed awp.dat that the error resolved (which may or may not be pertinent to the issue).

If indeed any such files containing settings, etc., would be corrupting or causing this not infrequent error, and given the fact that customizing the Atlantis interface is not something you'd want to be doing time and time again (I have it set up the way I want and am now accustomed to; it takes a long time to customize it that way), in that case I would recommend Atlantis produce a simple settings files that cannot corrupt that can simply be exported and imported. Or is there such a function that I'm not aware of?

To give many customization options that then can't be backed up or imported properly (when customizing the interface, etc., takes a long time to do) does not seem like a good idea. And if it is a simple settings file that can also be read (like an .ini file or something like that) then that would be helpful.

I guess, therefore, that the only thing I can do is do a fresh install having removed all previous settings. Then go through the arduous process of recreating the UI customizations and other desired defaults, then not saving or backing up these settings, so that in the future I should go through all that again. This does not sound like a good solution. If indeed it is old, grandfathered-in settings that cause the error (which yes, I do install as not to have to reconfigure Atlantis each time on fresh OS install), then it sure doesn't explain why it can function for a month without any issue, and then suddenly start erroring out. I then reinstall with the same settings and it goes away again. Until it comes back. Something is not right here and my previous configurations shouldn't be able to make Atlantis fail to start over time. Something is not right about this.
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

I've been customizing the toolbar for an hour now and not even halfway done.
Robert
Posts: 1876
Joined: Fri Aug 15, 2003 8:27 pm

Post by Robert »

It seems that you are running round and round in circles installing, then uninstalling, then reinstalling Atlantis. It can only lead to frustration.
Tampering with the internal system files of Atlantis or any other application is most unadvisable unless you really know what you are doing, which is obviously not the case.

I suggest that you completely uninstall Atlantis from your Windows system. If necessary, delete all of the Atlantis own system files manually. Remove all traces of Atlantis from your system.

Then, and only then, reinstall Atlantis through the normal standard procedure (Setup file of Atlantis Word Processor 4.1.3.4).
You will have to reenter your registration information, and reconfigure Atlantis to your liking.

When this is done, you can easily save your current Atlantis configuration with the "Save to File…" button located at the bottom of the "Tools | Options…" dialog:

Image

The "Load from File" button will allow you to restore your Atlantis settings if necessary in the future.

HTH
Robert
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

Amazing how that is so obvious to you, since that is the method I used in the beginning when Atlantis got the redesigned interface. Only because I started experiencing the access violation error did I take it upon myself to save the actual files to replace them as that restores those settings, too. I just forgot it was indeed in .ini format.

I don't know what you consider tampering with system files or even Atlantis files, but anyone with a passing understanding of operating systems and programs would not make such a leap in statement based on what I said. The access violation was not *because* I did anything, it was Atlantis corrupting files over time. I tried both restoring via loading the config, and when that didn't fix the issue I resorted to placing the pertinent files in their locations manually (or through unattended method).

So please don't conflate what I said about the process of narrowing down upon which file Atlantis failed with Atlantis failing in the first place, which is an entirely different matter of course.

I will reinstall Atlantis with the command switches provided and not restore via loading presets nor use my own secondary method this time around when re-configuring everything, as these methods sooner or later give me the access violation errors. So I'll manually set everything and again save, again backup actual files also, and see what happens going forward. It should not give an access violation, period. It is the program doing this, not a document. More precisely, it is a configuration file that causes Atlantis to crash. Why it gets corrupted in the first place, I guess I'll never know.
Robert
Posts: 1876
Joined: Fri Aug 15, 2003 8:27 pm

Post by Robert »

"awp.dat" is not an Atlantis "configuration file". It is a proprietary internal file meant "for Atlantis-eyes-only". End-users are not supposed to modify or remove, then reinstate that file haphazardly with their "own personal installer". In doing so, you are tampering with the normal natural functioning of Atlantis. It can only lead to corruption. There is nothing to be fixed regarding "awp.dat". Just leave it alone. It will take care of itself.

The only "configuration file" you should care about is the "Atlantis.ini" file created through the "Tools | Options…" dialog.

"Access Violation" do happen with Atlantis, but they happen very infrequently, and they are always linked to a specific chain of commands, most of the time with specific documents, and a particular configuration.

When this happens on your system, don’t tamper with any of the Atlantis proprietary internal files. Just send a bug report and your current "configuration file" ("Atlantis.ini") to "support@AtlantisWordProcessor.com", describing steps to reproduce the problem. You will spare yourself a lot of aggravation.
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

I understand what apw.dat is and does -- if you read my post closely you would see that, too, but I didn't want to indicate all too publicly what it did do...

Thanks for acknowledging that access violation errors do occur in Atlantis. In my case, however, they occur when the program loads by itself without opening any document (except perhaps the default new blank document that it loads).

I only started backing up local files to restore from when the access violation error kept occurring. It was merely a quick way to get back to work with all my personal files and settings in place in one click. It was not a recommendation. I would recommend, however, that Atlantis shouldn't throw access violation errors. It should just never do this. Perhaps create a debug option for this issue.
Robert
Posts: 1876
Joined: Fri Aug 15, 2003 8:27 pm

Post by Robert »

If you get access violation messages just by launching Atlantis, it can only mean that your install of Atlantis is corrupt, or that your current Atlantis settings have hit on a bug. In which case, it would be much wiser to send your current Atlantis configuration file ("Atlantis.ini") to "support@AtlantisWordProcessor.com", with steps to reproduce the problem.

Reinstating Atlantis through your "own personal installer" is the wrong way to go about such problems. It is no wonder access violations keep reoccurring on your system. The outcome could not be otherwise.

Note that your Atlantis personal files should normally be located in "C:\Users\<User’s Name>\Documents\Atlantis\Documents". They shouldn’t normally be affected by problems related to access violations.
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

I get what you're saying, however when I started writing this post I was not closing off the possibility that Atlantis itself is crashing. However, I did think it odd that there weren't many more such reports than there are.

But I will start afresh and do as you suggested (exclusively use the .ini file) and if I then still have these access violations, I'll come back to the forum to report it.

I have come across programs that rely on config files like this, but they don't error out beyond usage. Some will make a backup of the old/corrupted .ini file and then create a new one as to keep the program usable. I think things can improve on this issue.

Thanks for all the help!
Robert
Posts: 1876
Joined: Fri Aug 15, 2003 8:27 pm

Post by Robert »

If there aren’t many crash reports in this forum or elsewhere, it is simply because they happen very rarely:)
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

:D
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

Wow. Just wow.

After the clean install of Atlantis, getting everything configured, backing up the .ini file, etc., I then sought to uninstall Atlantis. As soon as I did, I got an access violation just trying to uninstall the program...

I'm saying, there is something wrong. Why would it give an access violation upon uninstallation? This is v4.1.3.4.
Attachments
access_violation.png
access_violation.png (33.54 KiB) Viewed 3724 times
User avatar
admin
Site Admin
Posts: 2437
Joined: Wed Jun 05, 2002 10:48 pm
Contact:

Post by admin »

Possibly the error is linked to your current Atlantis configuration.
Could you please email your INI file to support@atlantiswordprocessor.com ?
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

I've emailed the .ini file to you. To note, this .ini file is based on a clean install of Atlantis; I then configured the application as I wanted and saved the .ini file. I then uninstalled Atlantis and this is when the access violation error occurred.

Thank you!
User avatar
admin
Site Admin
Posts: 2437
Joined: Wed Jun 05, 2002 10:48 pm
Contact:

Post by admin »

Thanks for the INI file. But we cannot reproduce errors under your INI file.

If you have a memory flash drive, please do the following:

1. Connect the memory flash drive to your computer.

2. Use the setup file of Atlantis to install Atlantis to the memory flash drive (specify a folder on the removable drive as the destination folder).

3. Copy your INI file to the home folder of Atlantis on the flash drive.

4. Launch Atlantis from the flash drive.

Do you still get errors in your portable copy of Atlantis?
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

Okay, I will do as you suggested and report back.

Meanwhile I'd like to say that I also can't reproduce it just with that .ini file. But since no other modifications were put in place than the configurations of the settings and UI at this point (as recorded in the .ini file) it couldn't be any factor other than what is Atlantis is doing. I noticed uninstalling Atlantis calls the awp.exe file (shows in Task Manager), so when uninstalling, awp.exe gets run. (Or it couldn't error out, I imagine. I don't know whether something goes awry with a memory space awp inhabits or allocates or what.)

This is something that either happens over time or else irregularly so this is why I have never been able to willfully reproduce it via any settings or documents. Hence I say it's "elusive."

Will report back with the flash drive test.
Robert
Posts: 1876
Joined: Fri Aug 15, 2003 8:27 pm

Post by Robert »

patr wrote:I've emailed the .ini file to you. To note, this .ini file is based on a clean install of Atlantis; I then configured the application as I wanted and saved the .ini file. I then uninstalled Atlantis and this is when the access violation error occurred.
First thing that came to my mind was "why on earth would anybody want to uninstall an application immediately after having just installed, and configured it?"
But it obviously can be done. So why not do it? If only to make a point!

Now your screen capture seems to imply that you tried to uninstall Atlantis when there was still an instance of Atlantis running on your system: the 2 dialogs in your screen capture are spawned by Atlantis, and the access violation can only happen if there is a running instance of Atlantis.
I did not have Windows 7 to test this. I tested it in Windows 10 (with all latest updates). I left Atlantis running and tried to remove it through the standard Windows procedure. This is most unadvisable. But obviously, some people will inevitably try to do it.
So I went ahead with the uninstall. I got this:

Image

I closed the running instance of Atlantis 4.1.3.4, and clicked on the Uninstall button again. I got this:

Image

So it was impossible for me to uninstall Atlantis without closing any running instance of Atlantis first. How was it possible for you? It baffles me!

I clicked on the “Yes” button in the above dialog and got this:

Image

No access violation!
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

Robert, I can see you have somewhat of a chip on your shoulder and that is okay. But rather than try to eviscerate my findings by mere logic and your own experience, you might try to adopt the attitude of trying to figure out what is going on in these instances of access violations and perhaps, in addition, why Atlantis throws these in the first place. (And does it in such a crippling manner -- see points I made above for suggestions.)

If your point was that a person should not uninstall Atlantis after configuring as to prevent access violation errors, again I find you on the wrong side of this issue. It is the opposite of constructive.

I also just explained that uninstalling Atlantis calls awp.exe into action, so again you're off regarding the issue at hand.

I can do what you did above as well (installing, uninstalling, etc). I just did it ten times. This thread is not about when it works as it should. It is about when it doesn't. And why it throws access violation errors in various scenarios, however un-reproducable we might find them. Programmatic errors often don't manifest on schedule, you know.

I think it is more helpful if we whittle down the useless responses of which there have been enough now, and try to figure out why those access violation errors occur.
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

@admin:

I was able to install Atlantis on the flash drive, activate it, and import my saved Atlantis.ini and everything works well.

Of course, most of the time Atlantis does work well on my end. Until it doesn't.

EDIT: An additional note regarding possible corruptions of the .ini file and that line of thought: the times when the access violation errors occur when (merely) starting up Atlantis do NOT coincide with having made configuration changes. However, files and registry do get written to every start up and use of Atlantis, so read from and writing to files/registry does occur every time.
Robert
Posts: 1876
Joined: Fri Aug 15, 2003 8:27 pm

Post by Robert »

To be able to fix any bug in any application, the developers must be able to reproduce the steps as described by end-users. Bugs that cannot be reproduced are quintessentially idiosyncratic. Your access violations won’t be stopped until the developers can reproduce them on their own system. Developers cannot fix bugs in a vacuum.
To me, uninstalling an application that has just been installed and customized is the opposite of constructive. Atlantis is meant to be used as a word processor to create documents. You are not testing the creation of documents in Atlantis, you are trying to catch Atlantis out through repeated and wild install, reinstall and uninstall. This is the opposite of constructive.

You assume that Atlantis includes programmatic errors regrading its uninstallation and you behave as if it was your assigned task to detect them. You "try to figure out why those access violation errors occur" but unfortunately you figured out nothing at all that would really help!
Most likely, these violation errors occur because of specific interactions between your system and the Atlantis uninstall. The developers could not even dream to be able to fix your problem unless and until they can reproduce these particular interactions on their own systems.

Now the INI file that you sent was merely a capture of your current Atlantis settings. That INI file won’t change until you overwrite it with a new version created from the "Tools |Options…" dialog. If it contains settings that don’t spawn access violation messages, you could rename it as "MyAtlantis.ini" and launch Atlantis through the following command-line:

"C:\Program Files (x86)\Atlantis\awp.exe" /dss /lsi /sfn "C:\Users\<User’s Name>\Documents\Atlantis\MyAtlantis.ini"

This would launch Atlantis with the settings stored in your stable "MyAtlantis.ini" file, and tell Atlantis DontSaveSettings, LoadSettingsFromIni, SettingsFileName
In this way, Atlantis would read settings exclusively from your stable "MyAtlantis.ini" file.

If you want to make changes to these settings later on, make them in the Atlantis interface, and save the new settings as "MyAtlantis2.ini" file.
The above command-line would then become:

"C:\Program Files (x86)\Atlantis\awp.exe" /dss /lsi /sfn "C:\Users\<User’s Name>\Documents\Atlantis\MyAtlantis2.ini"

If these new settings prove to be as stable, you could make them permanent.
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

You assume that Atlantis includes programmatic errors regrading its uninstallation and you behave as if it was your assigned task to detect them. You "try to figure out why those access violation errors occur" but unfortunately you figured out nothing at all that would really help!
You are so incredibly off regarding the points I made in this thread that it is bordering on ridiculous.

How you think I "behave" is entirely ridiculous. I have documented what has happened to me in my use of Atlantis. How I then sought to reproduce and/or to remedy the issue, and I have further documented the various methods I've used to get back to being productive with an Atlantis that is erroring out.

Where you read that I'm behaving as a self-assigned bug-hunter is just, frankly, crazy. I'm trying to get to the bottom of the issue I'm repeatedly encountering on various systems and I'd like to do that with the developers who have insight derived from programming -- in that light I have tried everything that has been suggested and I have reported back. Exactly as one would.

Perhaps you should remove yourself from the discussion if you don't appreciate bug reporting and following up on admin suggestions. "Yeah sure Atlantis errors out on access violation at times, so what?" is not even remotely the attitude of one who would like to see a program improve or else understand what external process or state might be triggering the issue. All else is just your ego. You can recuse yourself from this thread at any time. You're only going in circles at this point.
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

Now the INI file that you sent was merely a capture of your current Atlantis settings. That INI file won’t change until you overwrite it with a new version created from the "Tools |Options…" dialog.
What should be abundantly clear by now is that these errors seem to occur at random. The only changes would have been those Atlantis self-saves on every startup/exit and these are found in registry and such, not in the .ini file. I never claimed the latter. For example, runcount changes all the time and gets recorded in the registry. These would be among the type of "changes" that are the only thing I can see as occurring *as I didn't personally and expressly change program settings when these random-like errors occur.* I really hope you understand me this time. And please stop quoting me on things I never said!
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

To be able to fix any bug in any application, the developers must be able to reproduce the steps as described by end-users. Bugs that cannot be reproduced are quintessentially idiosyncratic. Your access violations won’t be stopped until the developers can reproduce them on their own system. Developers cannot fix bugs in a vacuum.
Where do you get the idea that I expect developers to fix things they can't reproduce? Why would I share config files with them (upon their request) if I thought they could reproduce it without those files? Your attitude is basically such that people shouldn't report bugs and give feedback on their issues! "Your .ini file did not trigger the program crash" may just mean it's not the .ini file causing it. So what is? The issue occurs. It should not be reported now? I can't fathom your absurd attitude toward this whole matter. Frankly, it is absurd.
Robert
Posts: 1876
Joined: Fri Aug 15, 2003 8:27 pm

Post by Robert »

There is no point in getting so peevish and personal, unjustifiably so to boot…

Just for the record, I have been involved daily in the development of Atlantis since it was first released many many years ago as "Atlantis 0.7", then as "Atlantis Ocean Mind", and now as "Atlantis Word Processor". I can rightfully claim to have helped fix an untold number of bugs which were present in the beta versions of Atlantis to which I have had regular access since its incipience. So I don’t see any reason why I should recuse myself from this thread. Or from any other thread for that matter…

You misunderstood what I said. Atlantis does self-save settings on every exit and these are normally saved to registry. But if you use the command-line I suggested above, nothing will be saved to the registry on exit, and the settings stored in your stable "MyAtlantis.ini" will be automatically used whenever you launch Atlantis. You'll then be able to use Atlantis as a stable word processor, and spare yourself a lot of aggravation…
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

Let's be clear: you are the one that keeps jabbing in unjustified ways and insult a customer about their self-assigned bughunter status, etc. I never said or implied any of the things you keep bringing up and which I have all refuted successfully.

Like assuming that I had Atlantis running, when in fact I did not nor said I did, and to boot not understand that uninstalling Atlantis actually calls awp.exe into running. Things like this, time and time again.

So whether your sense of ownership is somehow affected by my bug report, I can't help that. If you want to ignore that this issue is occurring then that's up to you. I have complied with and responded to each suggestion as a constructive person would.

Your attitude has nothing but dented the good feeling I had associated with Atlantis for so long. I can say that. Your attitude is ridiculous. Appalling. Destructive. Not helpful.

It shouldn't throw an access violation error. I run various professional software and VMs and whatnot and none of the 200 programs I use ever has an issue. Only Atlantis.

I've had enough. I've reported the issue and gave plenty background information. Good luck!
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

Don't read into me posting one more time, it's not what you think. I was actually uninstalling Atlantis and going back to TextMaker instead because I'm done with this sideshow.

Guess what happened when I uninstalled Atlantis just now? No really. Just guess.

Just to be overly clear yet again: no, no instance of Atlantis was running. But as I just mentioned twice, awp.exe gets called when you uninstall Atlantis and then this happened. The ini file was fine, right? You guys checked it out and it wasn't throwing errors while I was using it, this time (yet). No, I'm not implying it's caused by the .ini file or anything else. One has to be this disclaiming when someone willfully misinterprets you.

My experience here has been simply like this: being met with maximum prejudice and inexcusable ill will, and minimum inquisitiveness and good will.

To then do a final uninstall and get this... the cherry alright.
Attachments
Image 1.png
Image 1.png (38.23 KiB) Viewed 3621 times
Last edited by patr on Tue Sep 14, 2021 2:50 pm, edited 1 time in total.
Robert
Posts: 1876
Joined: Fri Aug 15, 2003 8:27 pm

Post by Robert »

I run various professional software and VMs and whatnot and none of the 200 programs I use ever has an issue.
You’re trying to make out that Atlantis is the only program that has issues, especially issues that occur on your system. But no one else has reported any similar occurrences with Atlantis.
All programs have bugs and problems, even the best of them. For example, if you’d take a look at the MS office Community and Microsoft Word forums, you should notice how many problems users have had and still have with MS Word.
I've reported the issue and gave plenty background information.
Unfortunately, you gave nothing that could really help solve your problem… “awp.dat” had nothing to do with your problem, unless you tampered with it very unwisely.

Now I just changed the advanced file properties of "awp.exe" on my Windows 10 system. I asked Windows to compress its contents to spare disk space. This was obviously a silly thing to do, but I did it for test purposes. I then tried to uninstall Atlantis through the standard Windows procedure. I got this:

Image

Would you by any chance have altered the file properties of any of the Atlantis files in its home folder, especially those from "awp.exe"? Did you activate the Windows option to compress the Atlantis executable?

Would you by any chance have altered the file or folder properties of your hard disk so that Windows would compress their contents?

Just brainstorming!
patr
Posts: 51
Joined: Fri May 06, 2016 8:05 pm

Post by patr »

No, I do not have file compression on any of my installs or systems. And I doubt that file compression is the actual cause of the occurrence of that error on your end, either -- for this is how elusive it is acting every time... Coincidence does not equal cause. I'm very well aware of all such things, I just don't understand why I'm on trial to prove I'm not 7 years old if it weren't for your towering prejudices.

I never, ever, implied that awp.dat had anything to do with the error. What I said was that it was interesting that Atlantis would not successfully start up (not able to get beyond the error it threw) until I deleted that file (this of course only being one thing I tried and nothing definitive). Deleting that and other files was not a diagnosis of the problem, I was merely relating to you (or whoever) that *once* I deleted awp.dat, Atlantis started up again (albeit without activation). I only mentioned that in case this could give a hint where to look for the causes of this issue -- further, I even said it "may not be pertinent to the issue". I also never edited that file by any means. I have no idea why you keep misconstruing my words so blatantly. It is not hard to grasp what I meant.
Post Reply