RomRaider

Dale, did you tag the repo? I checked, you didn't, or at least, if you did, you didn't push it. If you'd like me to tag it on your behalf, let me know. Tagging should typically be done before distribution.

What are your plans with respect to this being a snapshot and an actual release of 0.5.5? Hmm, decided to research before hitting submit on the post:

Your comment reads "Update Release Notes for 0.5.5 SNAPSHOT release". It can't be a snapshot and a release. It's either a snapshot (@ a specific hash/date, which is nice to point out, but unessential) or it's a release. Snapshots are development versions between releases.

Also, none of the commits since early June are in the official RR repo. Would you like me to push the head of yours there?

https://github.com/RomRaider/RomRaider/network

Great progress! :-)

Fred.

The intent with this snapshot was to get something out for general feedback. If it is working well enough I was going to then push it to the official repo. So that could be in a month or so. It could then be called "0.5.5" release?

Sorry I don't understand the naming of such things as snapshot or release or tag...
What are you suggesting I do here...? Go ahead with the appropriate Git commands or a link if it's easier on your wrists.

OK! This is an RC, then, not a SNAPSHOT :-) RCs should still be tagged. The tag should be duplicated if it makes release spec.


Snapshot = grab a particular current version and give it to people to use/try without intent for it to become anything with a name/version/meaning. You might give someone a snapshot one day, and another the next day, and they may not know what you did in between. They're random "snapshots" (like from a camera) of the code base over time.

Release = something named, distinct, permanent, tested, documented, etc.

Tag = a name and description for a specific revision of the code base.

Releases and RCs should always be tagged. Snapshots should typically not, though I tag a snapshot version immediately after/at the release version such that git-describe gives 0.0.2-SNAPSHOT-COMMIT_COUNT-gGIT_HASH for the version during dev, rather than 0.0.1-COMMIT_COUNT-gGIT_HASH which I feel is misleading.


Push all work that you're happy with to the official repo because I see people basing their work off of it rather than tracking you. If you want to keep a dev/master distinction there, that's a great idea. Tag this hash as 0.5.5-RC1 with a suitable description. Push that tag to your repo and the official one. Wait.

If all is well in some days/weeks/months push updates to version strings, then make a new tag on the new commit. Build with the new names and distribute as release. This commit should be pushed to a branch so as to exist in the repo. This way you can go ahead and keep developing while it stabilises. I prefer a freeze/stabilisation period on master in the mean time myself, but if you prefer the branch and carry on method, that can be made to work too.

Any chance of turning on quote tags here?

Fred.

I've had four or five blue screens while logging with this version. It blue screened twice within 15 minutes as I was heading back from a run. Is there anything I can post or send you that will help with identifying the problem? I'm running Win7 with a Tactrix OP2 and Innovate LC-1.

I also had blue screen trouble with the last revision but never had an opportunity to post about it. Crashes typically happen after logging for more than 25 or 30 minutes.

I'll have to read this a few times as it's not sinking in except for the part that this more of a RC.


When you post make sure "Disable BBCode" is not checked.

There are certainly some major differences in this 0.5.5 version over 0.5.4.
1) The whole Openport 2 driver access code changed so if you had BSOD before then that's probably not the problem.
2) In 0.5.4 I provided an updated version of COM4J which is used for the Innovate MTS protocol but not for the LC-1 attached to a serial port (although Innovate MTS will still allow you to log an LC-1 if selected).

You can try sending the rr_system.log file, but I'm not sure it will help if the OS is crashing. Can you identify the reason for the BSOD? You may have to disable the automatic reboot function in Windows so the system stops at that screen. Take a photo of it if possible and submit it.

I have only personally logged for about 15 to 20 minutes using Win XP Pro and haven't noticed a problem. But I don't have an LC-1 installed (it's sitting on the desk) nor am I using my Openport 2 (also sitting on the desk, but I can try it out).

Sounds good, I'll try to get a photo of the screen before rebooting and send you the system log next time I have an issue. Not sure if it makes a difference, but the LC-1 is going through a serial to USB adapter.

Thanks again for all the hard work!

Have you tried a different one or version. I think some people have reported BSOD related to certain adapters.

Skype this weekend, perhaps? Will be in Madrid away from dev box :-(


Are you calling me a noob? :-) (It's disabled for this forum section in your admin panel) Edit: I see quotes above!!! Maybe I'm not sufficiently privileged? I definitely do not have the option, and it says this:

Options:
BBCode is OFF

to the lower left. Can screen shot. Maybe I am a noob, but I don't think so. EDIT2: ALL functioning quote tags belong to you, the mod. No one else has a quote tag to test. BBCODE is on in my profile and works in other parts of the board. Sorry for offtopic.

Re BSOD: Driver issue. Which chipset in the USB-RS232 adapter? Which driver for it? Which version? etc. Unless you're using win ME or 98 lol.

Fred.

I see what's going on. The post was moved to General News as a global topic which has very restricted permissions. I moved it to this forum so you should see the options now.

As I moved the split line between the parameter/switch selection table and the widget area of the dashboard, the widgets turned tiny, without the alarm setting boxes.

I liked them tiny (the normal ones were too big, I could fit only 9 in my screen), but the title became too tiny to read.

Is there a way to control this?

I have tactrix 2, mtx-l wideband and log on windows xp sp2, I have noticed no problems at all apart from when I open the logger it tells me that the logger file can't be found but once I push ok it boots onto the logger and runs perfectly. Great work on the rom compare tool too!

You want to change the font size?

Did you move the logger.xml and not tell the Logger definition manager, or is it something else? Maybe a Print Screen capture would help. Or send the rr_system.log file.

removed and re-added logger file and problem went away