Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: REACT 2 Released (Read 1277381 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

REACT 2 Released

Reply #525
Still no joy on ssb16 - it rips to wav, but doesn't go any further than that.  For now, I've fallen back to ssb15 as it works correctly as long as the disc remains in the drive.
I'm finding this extremely frustrating, as I can't get b16 to fail.  The changes between b15 and b16 are so minimal.  I need to hear from dewey1973 to see if b15 works for him, and maybe some other kind-hearted souls who are willing to test.  Do I take it the batch file (that actually does all the processing) is never even created?

This  actually got me thinking about another repercussion of doing the disc  numbers of a set dynamically - ssb16 wont process correctly in batch  mode. the interface has to be open with the correct numbers in the  metadata tags in order for it to work. Is there any way to have that  data go into a tag or data file that is persistent until the rip is  processed to flac or ogg or whatever?
Before I worked on the Additional Meta Data dialogue I had an idea of using markup to pass extra values in the few fields available (artist, album, comment).  E.g.:

Album Name <discnumber>2</discnumber><totaldiscs>3</totaldiscs>

I had the markup parsing working fine, but it caused real problems, or at least confusion, when messing with the album and artist name.  Using the comment field was no issue, but IIRC there is a short character limit on the comment field, rendering it near useless (unless you used single character tokens I suppose).

With regard to this solution, it may be possible that REACT could store meta data in a specific file for each album, perhaps using the artist and album name as the file name.  When the processing REACT instance is run it could use the specific ini and ensure that it is deleted afterwards. I can't really see a problem with this approach.

I want to resolve the potential issue with b16 before doing any other work though.
I'm on a horse.

REACT 2 Released

Reply #526
Quote
I need to hear from dewey1973 to see if b15 works for him


Testing now...

REACT 2 Released

Reply #527
Since switching to EAC 0.99pb1 and ssb16 I am having a problem.  Everything goes great until the extractions is complete.  Nothing happens after the extraction completes.  I use F10 to do an image test & copy.  I get the wav, log, cue, and jpg but none of the other processes begin.  Here is my ini.  Any help would be appreciated.
I just tested with ssb16 on my XP machine at work - using your INI file with only OutRoot amended, and the standard cfg file - and it worked fine.

Ho hum.


Quote
I need to hear from dewey1973 to see if b15 works for him
Testing now...
Cool, thanks.
I'm on a horse.

REACT 2 Released

Reply #528
I get the same result for b15.  Nothing happens after extraction.  All I did was unzip and pull those files into my REACT folder.  I hope that is the correct way to install.

REACT 2 Released

Reply #529
So, we're yet to know whether b16 is an issue for other people than deltadave.

Dumping the new EXE in there is fine if you already had REACT and EAC configured.

Is EAC properly configured to use REACT?  It may be worth hitting  Ctrl-F2 with REACT/EAC open, to let REACT (re-)configure EAC.
I'm on a horse.

REACT 2 Released

Reply #530
It may be worth hitting  Ctrl-F2 with REACT/EAC open, to let REACT (re-)configure EAC.


After doing this the next set of processes did kick off.  I did however get an error that I'm sure has to do with where the files are saved.  I'm sure I can fix it after reading the log more carefully.

REACT 2 Released

Reply #531
It may be worth hitting  Ctrl-F2 with REACT/EAC open, to let REACT (re-)configure EAC.


ssb16 rips and converts only for single disc sets.  If any entry is made in the new dialog then the wav file is created and then the process stops.  No conversion, no renames, etc.

I also had to use Ctrl+F2 to reset EAC before ssb16 would rip, convert and rename single disc sets.

Would like to suggest as well, that the dialog not be reset when a new disc is inserted.  If you are ripping a multi disc set, then two values have to be entered with every disc and if ripping a 6 disc set for example, there is a high probability of making a mistake and having to re-rip a disc. Plus it's lot of extra keystrokes.

edit 2: I got ssb16 to work, had to reset EAC with Ctrl+F2 and I also had a missing quote mark in one of the track.cfg file.  Took some doing, but I tracked it down. Sorry about blaming you for my bad typing.

REACT 2 Released

Reply #532
ssb16 rips and converts only for single disc sets. If any entry is made in the new dialog then the wav file is created and then the process stops. No conversion, no renames, etc.

I also had to use Ctrl+F2 to reset EAC before ssb16 would rip, convert and rename single disc sets.
...
edit 2: I got ssb16 to work, had to reset EAC with Ctrl+F2 and I also had a missing quote mark in one of the track.cfg file. Took some doing, but I tracked it down. Sorry about blaming you for my bad typing.
I'm glad you finally got it working.

I would say that I have not had to use Ctrl+F2 on all three computers that I have tested b16 on; it's worked straight off the bat.  Ctrl+F2 seems to resolve issues for people relatively often; I wonder why it (REACT/EAC?) gets confused sometimes.

Would like to suggest as well, that the dialog not be reset when a new disc is inserted. If you are ripping a multi disc set, then two values have to be entered with every disc and if ripping a 6 disc set for example, there is a high probability of making a mistake and having to re-rip a disc. Plus it's lot of extra keystrokes.
My main concern retaining values is that someone could set totaldiscs to 2, hide the dialogue, and then rip a hundred discs forgetting to set it back.  Single disc albums are far more prevalent than muli-disc albums.  The idea is that the settings refer to default - i.e.: the value they will be for most discs - and therefore I would say that you are minimising typing by not having to reset after multi-disc albums.

That's my contra-argument; however if other users disagree I have no problem changing the logic according to the majority.

Thanks for the feedback anyway, I'll certainly bear it in mind.  I have considered providing options on the dialogue before, and perhaps this could be solved with a checkbox to set user preference - possibly even on  a per token basis.

Also, contrary to my previous remark, I have made some steps towards storing the meta data in an album-specific ini, so that it can be used in batch ripping.  My main concern, however, is that - because the EAC wrapper instance only has access to basic info like artist and album - I am currently using "<artist> - <album>.ini" as the naming scheme; fine most times, but not for multi-disc albums.  I don't know a resolve to this, unless I somehow utilise some (as yet undescovered) command line app to calculate the freedb id, use that, and then use the freedb id passed by EAC in the REACT params to find the ini for the album being processed.  Any thoughts?
I'm on a horse.

REACT 2 Released

Reply #533
Would like to suggest as well, that the dialog not be reset when a new disc is inserted. If you are ripping a multi disc set, then two values have to be entered with every disc and if ripping a 6 disc set for example, there is a high probability of making a mistake and having to re-rip a disc. Plus it's lot of extra keystrokes.
My main concern retaining values is that someone could set totaldiscs to 2, hide the dialogue, and then rip a hundred discs forgetting to set it back.  Single disc albums are far more prevalent than muli-disc albums.  The idea is that the settings refer to default - i.e.: the value they will be for most discs - and therefore I would say that you are minimising typing by not having to reset after multi-disc albums.

That's my contra-argument; however if other users disagree I have no problem changing the logic according to the majority.

Thanks for the feedback anyway, I'll certainly bear it in mind.  I have considered providing options on the dialogue before, and perhaps this could be solved with a checkbox to set user preference - possibly even on  a per token basis.


A check box for persistence would solve the problem quite neatly. I'm not sure how big of a problem this would actually be, I keep an eye on the file conversions as things move along.  If they aren't named properly, it would be fairly easy to notice. That is my personal experience only, not sure if it would be applicable to anyone else.

Also, contrary to my previous remark, I have made some steps towards storing the meta data in an album-specific ini, so that it can be used in batch ripping.  My main concern, however, is that - because the EAC wrapper instance only has access to basic info like artist and album - I am currently using "<artist> - <album>.ini" as the naming scheme; fine most times, but not for multi-disc albums.  I don't know a resolve to this, unless I somehow utilise some (as yet undescovered) command line app to calculate the freedb id, use that, and then use the freedb id passed by EAC in the REACT params to find the ini for the album being processed.  Any thoughts?


code libraries:
http://www.codeproject.com/cs/media/freedb.asp

Thread on this very topic:
http://www.autohotkey.com/forum/topic13706.html

In EAC isn't %f the tag for storing freedb id?  Not usually used from what I can tell, but still available. I think.

REACT 2 Released

Reply #534
code libraries:
http://www.codeproject.com/cs/media/freedb.asp

Thread on this very topic:
http://www.autohotkey.com/forum/topic13706.html

In EAC isn't %f the tag for storing freedb id?  Not usually used from what I can tell, but still available. I think.
Thanks for the links.  I found another of interest earlier today also (http://www.vbaccelerator.com/home/vb/code/vbMedia/Audio/CD_Tracklistings/article.asp).

The processing instance of REACT will have access to the %f parameter; however the EAC-wrapper instance does not.  I can only think that the wrapper instance will have to calculate the ID itself somehow, in order to write the INI file.

I'm also worried about over-complicating my mod, with the need for additional EXEs/DLLs and extra processing time.

I've just thought of a sure-fire way to get the freedb id.  Force EAC to write a "Single WAV File" cuesheet (Alt+S) and then grab the freedb id from the REM statement.  Slightly messy, but no need for additional exes/dlls, and I know the id will be the same.

Of course, this will also rely on the user using unique names for their images when ripping to WAVE with the compression queue on.
I'm on a horse.

 

REACT 2 Released

Reply #535
I'm also worried about over-complicating my mod, with the need for additional EXEs/DLLs and extra processing time.

I've just thought of a sure-fire way to get the freedb id.  Force EAC to write a "Single WAV File" cuesheet (Alt+S) and then grab the freedb id from the REM statement.  Slightly messy, but no need for additional exes/dlls, and I know the id will be the same.

Of course, this will also rely on the user using unique names for their images when ripping to WAVE with the compression queue on.


I can understand your concern re processing time and additional dll's etc.... 


If you need a guinea pig to test out your stuff, I'm willing to volunteer.  Should this turn out to be too much of a pain to deal with a special case, I'll just deal with it by hand and take the time.  Default behavior is just fine for most of my collection.

Edit:
I think that I'm slightly confused as to how EAC/REACT works... would you mind putting up a brief summary or pointing to one? 

My understanding:  REACT opens using the .ini file then rips the files from CD to .wav file.  Once the .wav file(s) are created it uses the .cfg file to create a batch file that processes the wav file(s) by instancing FLAC, LAME or whatever external compression program is desired.  The processing instance would be the REACT that creates the wav files? Wrapper would be the batch file that calls the external processor?

REACT 2 Released

Reply #536
After doing this the next set of processes did kick off.  I did however get an error that I'm sure has to do with where the files are saved.  I'm sure I can fix it after reading the log more carefully.


I've done some more playing around and this is what I have found.  I did a complete reinstal of EAC and REACT ssb16.  When I set "Test=1" and "Debug=1" I find the following error.

Code: [Select]
error in tag spec: eaclog=@C:\My Documents\My Music\CD Images\The Police - The Police (Disc 1) [2007].log !


Then the rest of the bat file tries to execute for the file moves, etc.

When I set "Test=0" this error does not occur and the process completes successfully with the exception that the log file is not moved to the new directory.  The log is, however, saved in the tag of the wv file.

I'd really like to use Test & Copy.  Any idea what I can do to make this work?

REACT 2 Released

Reply #537
I think that I'm slightly confused as to how EAC/REACT works... would you mind putting up a brief summary or pointing to one? 

My understanding:  REACT opens using the .ini file then rips the files from CD to .wav file.  Once the .wav file(s) are created it uses the .cfg file to create a batch file that processes the wav file(s) by instancing FLAC, LAME or whatever external compression program is desired.  The processing instance would be the REACT that creates the wav files? Wrapper would be the batch file that calls the external processor?
You're pretty much there. The "wrapper" instance and "processing" instance are purely terminology I have coined recently.

When you first run REACT it determines that no command parameters have been passed, and sets itself up as what I call the wrapper instance, because it wraps the EAC GUI.  This instance handles the hotkeys, setting EAC up, my meta data dialogue, etc.  As you say, it uses some settings in REACT.ini to detirmine the way it acts.

When you hit F10 or F4 to rip the wrapper instance is simply using EAC menu commands to start EAC ripping.  As EAC has been set up to use REACT as an external compressor EAC rips to WAVE, and then calls REACT, passing the parameters specified in the compression options.  This instance of REACT is what I call the processing instance, as it processes the files.  As you say, this instance will take the settings in REACT.ini, the parameters EAC passes (file names and meta data), and the appropriate config file, and create a unique batch file which it eventually sets running.  This batch file can contain any commands you like (written in the cfg file), but the default has options for the major encoders, like FLAC, WavPack, LAME, Nero AAC, etc.

At the time the batch file is running you have two instances of REACT running.  When the batch file finishes the processing instance closes and only the wrapper instance (which shows the icon in the sys tray) remains again.

When I set "Test=0" this error does not occur and the process completes successfully with the exception that the log file is not moved to the new directory.  The log is, however, saved in the tag of the wv file.

I'd really like to use Test & Copy.  Any idea what I can do to make this work?
I will try to do some testing tomorrow. I can't see why the log would be named differently.  I must admit I haven't tested using Test & Copy exhaustively, but I did test it, and never noticed a problem.  I seem to remember Dirk reporting success also.  I will test some more.  Do I take it that you have your images set up to use the scheme "$artist$ - $album$ [$year$]"?

When I set "Test=0" this error does not occur and the process completes successfully with the exception that the log file is not moved to the new directory.  The log is, however, saved in the tag of the wv file.
IIRC the standard behaviour is to not move the log file - if you want this to happen you have to add the line to your cfg.  Therefore, when not in Test mode I think things are working for you as they should.

The log will normally just get deleted at the end of the process; however when debugging various files are not deleted as normal (see cfg extract below - notice that when debugging the batch file exits before cleanup begins).

Code: [Select]
IF @Debug@==1 (
    PAUSE
    EXIT
)

REM ** Cleanup

DEL "@source@"
DEL "@eaclog@"
DEL "@cuesheet@"
DEL "@albumfile@.[*].cue"
DEL "@cover@"

REM ** Delete this .bat file:
DEL %0
I'm on a horse.

REACT 2 Released

Reply #538
I ran ssb16 on a single disc converting to a FLAC image and it worked flawlessly. My cuesheet & log were inserted, along with a jpg album cover. All tags were correct and the FLAC file was moved to the correct directory.

Missing a quote mark in the ini & config files can really mess things up big time. Also, check whether you are using $ and @ signs correctly with the tokens. Check slashes, back slashes, comma's, periods, and spaces.
And lastly, check the spelling of all lines that you edited in the ini & config files.

P.S. I ran the single disc twice. Once normal & then Test & Copy. Correct results both times.
Surf's Up!
"Columnated Ruins Domino"

REACT 2 Released

Reply #539
Hi,

I've just recently figured out that foobar doesn't read the tags that AtomicParsley creates for Nero AAC files, so I've tried modifying the image cfg file to use neroaactag instead, but I can't get it to work.  Please that this is my first time trying to mess with the config files, so I've probably made some simple mistake(s).  I have REACT setup to create a flac image and then nero tracks.  Of course, the flac image is created fine as I haven't messed with that at all, but the nero tracks are not created at all.  I can't tell what the error is (if there's even an error) because the command window closes right after it's done with the flac image.  This is what I've tried so far:

Code: [Select]
IF NOT @NeroAac@==1 GOTO end_nero_aac_tracks
SET dest="@TrackDir_AAC@"
IF NOT EXIST %dest% MKDIR %dest%
PUSHD %dest%
IF @various@==1 SET VA_tag=-meta-user:albumArtist=$q@VA@$q -meta-user:compilation=true
IF %embed_cover%==1 SET Cover_tag=-add-cover:front:$#x
@tools@\acdir.exe --overwrite --output "%TrackName%.m4a" --extra-opt "@cover@" --pipe "TITLE $n/$N aac $#T & @tools@\neroAacEnc.exe @Opt_NeroAac@ -ignorelength -if - -of $#o & @tools@\neroAacTag.exe $#o %Cover_tag% %VA_tag% -meta:artist=$#a -meta:album=$#T -meta:track=$n -meta:title=$#t -meta:year=$q@year@$q -meta:genre=$q@genre@$q -meta:comment=$q@comment@$q -meta-user:encodingTool=$qneroAacEnc @Ver_NeroAac@ @Opt_NeroAac@$q -meta:totaltracks=$N -meta:label=$q@label@$q -meta:disc=$q@discnumber@$q -meta:totaldiscs=$q@totaldiscs@$q"
IF @ApplyAlbumGain@==1 @tools@\aacgain.exe %ApplyAG_AacGain% *.m4a > gainlog.txt
COPY /Y "@eaclog@" "EAClog.txt"
IF %have_cover%==1 COPY /Y "@cover@" "folder.jpg"
POPD
:end_nero_aac_tracks

I'm still fuzzy on the acdir stuff, so I have no idea if what I've done should even be working.  Thanks in advance for any help.
Kittens give Morbo gas.

REACT 2 Released

Reply #540
Do I take it that you have your images set up to use the scheme "$artist$ - $album$ [$year$]"?


Code: [Select]
ImageNaming=$artist$ - $album$ [$year$]
ImageDir_Wavpack=@OutRoot@\CD Images\$cdartist$\$album$ [$year$]


I wonder if this is a timing issue with Test & Copy.  If the REACT script tries to access the log and it is not yet saved, wouldn't that cause the error?  I noticed that when using Test & Copy the status bar progress indicator goes from 0% to 50% during the test and then goes back to 0% for the copy.  As the copy completes it goes to 50% again.  It never reaches 100%.  If this somehow delays the saving of the log (like until I hit OK on the viewable log that pops up) then the wavpack command line would be looking for a file that didn't exist yet.  Any thoughts?

REACT 2 Released

Reply #541
I wonder if this is a timing issue with Test & Copy.  If the REACT script tries to access the log and it is not yet saved, wouldn't that cause the error?  I noticed that when using Test & Copy the status bar progress indicator goes from 0% to 50% during the test and then goes back to 0% for the copy.  As the copy completes it goes to 50% again.  It never reaches 100%.  If this somehow delays the saving of the log (like until I hit OK on the viewable log that pops up) then the wavpack command line would be looking for a file that didn't exist yet.  Any thoughts?
I think you are very likely correct. I don't believe that the logfile can be named differently when using Test, so it's probably just not there yet.  It may be worth having a look at this article:

REACT:Pausing For The Logfile
I'm on a horse.

REACT 2 Released

Reply #542
Just to let you know, as I don't like to say I'll do something and then not:  my wife's ill at the moment (nothing terminal) and I've taken a couple of days off to look after the kids, so I'm afraid I've no time for testing or code changes, and won't have for a few days.

@dewey1973, Although it's a bit of a workaround, hopefully the pause code in the config will sort your issue.  I hope to still test when I get chance, but if it is simply the logfile getting created a little bit late then I'm not sure I can do anything else except suggest that code.  We'll see.

@kalen3285, You seem to be missing the reference to the cuesheet. Append:

Code: [Select]
 "@sourcecuesheet@"

... to the end of your line.
I'm on a horse.

REACT 2 Released

Reply #543
Just to let you know, as I don't like to say I'll do something and then not:  my wife's ill at the moment (nothing terminal) and I've taken a couple of days off to look after the kids, so I'm afraid I've no time for testing or code changes, and won't have for a few days.


By all means, take care of your family!  That's always the top priority.  I'll test the pause code and post my results.  I know it's odd to say this having never met you in person, but please let me know if there is anything I can do to make it easier for to care for your family.  I truly appreciate the work you are doing, thank you!

REACT 2 Released

Reply #544
The pause code worked like a champ!  I guess if someone didn't want to use the pause code they could instead check "Make all compression tasks sleep" in the Compression Queue Control Center.  That way they could make sure nothing happens until the log is ready.

REACT 2 Released

Reply #545
OK, MrPete checking in after a (looong) pause.

I loaded up the latest, ssb16. The new (XUI) albumart as well. Everything worked GREAT... for one album.

On album #2 I get through the rip->wav part, and then it stops.

It's very strange:
* Hangs on "CHCP 1252" command (?!!)... even though doing it myself works fine on cmd line
* Everything works fine IF I...
  - Set DEBUG on
  - Modify the batch file to put the WAV and LOG files back in their proper place, at the top
  - Run the batch file manually after killing REACT

Some kind of window-control thing. I'm guessing it's your windows scripting language... have seen things like this before with WinBatch which is similar.

THANKS for all your hard work! This is soooooooo close...

REACT 2 Released

Reply #546
let me know if there is anything I can do to make it easier for to care for your family.  I truly appreciate the work you are doing, thank you!
That's very kind, thank you.  She's pretty much fine now, thankfully.

The pause code worked like a champ!  I guess if someone didn't want to use the pause code they could instead check "Make all compression tasks sleep" in the Compression Queue Control Center.  That way they could make sure nothing happens until the log is ready.
Good news.  I can't think of any other way around this.  However, following this, and an idea I had a while back, I have now created some updated CFG files, which incorporate this amend and various others.  I will include them in my mod from now on.

I loaded up the latest, ssb16. The new (XUI) albumart as well. Everything worked GREAT... for one album.

On album #2 I get through the rip->wav part, and then it stops.
Your symptoms don't make any sense to me, so I have to start with the basics:  is this one disc that causes the problems, or have you tried various discs, all with no luck?
I'm on a horse.

REACT 2 Released

Reply #547
REACT 1 was great but REACT 2 is excellent, it is much easier to configure.  Thanks for continuing to develope it.

I have one issue.  I do not get the cover art embedded into the FLAC or MP3 files.

I have tried to rip FLAC and MP3 tracks using both EAC095pb3 for copyrighted CD's and EAC099pb1 both with ssb16 with the same results.  On debug it shows the 'have_cover' and 'embed_cover' being reset to '0' and then when the jpg is detected being set to '1'.  The correct location of the jpg is also displayed in the debug file but I can not see the cover when I check it using Mp3tag.

I have noticed that my REACT_track.cfg differs from ones others have posted on this thread in that mine has the cover embedding actions under each individual file format heading whereas other posts show a single mention under Post-processing.

Any help appreciated, thanks again

REACT 2 Released

Reply #548
I loaded up the latest, ssb16. The new (XUI) albumart as well. Everything worked GREAT... for one album.

On album #2 I get through the rip->wav part, and then it stops.
Your symptoms don't make any sense to me, so I have to start with the basics:  is this one disc that causes the problems, or have you tried various discs, all with no luck?


OK, here's an update... first, to answer your question: I have had trouble with quite a few different discs. It is NOT the disc!

I went beack to ssb15... seemed to work better...but still not fully reliable. Messed around with debug settings and REM's.

* If I leave DEBUG off, the batch file never runs. Is it possible that with DEBUG=1 in the ini file, something inside REACT changes?
* With DEBUG=1, I also made the following changes to the CFG file, and I'm now running reliably:

At the top:
Quote
rem ECHO OFF
rem CHCP 1252


(My guess: echo off doesn't matter. But for some reason, the CHCP command still hangs a lot)

Quote
IF @Debug@==1 (
rem   PAUSE
rem   EXIT
)

REM ** Cleanup

DEL "@source@"
rem DEL "@eaclog@"
DEL "@cuesheet@"
DEL "@albumfile@.
  • .cue"
    DEL "@cover@"

    REM ** Delete this .bat file:
    DEL %0

(I like to preserve the log files, particularly when there's trouble...)

REACT 2 Released

Reply #549
I have noticed that my REACT_track.cfg differs from ones others have posted on this thread in that mine has the cover embedding actions under each individual file format heading whereas other posts show a single mention under Post-processing.
I'm not really au fait with album art practices, but it sounds like it is being embedded, but just in a way that MP3Tag is not expecting.  That said, I find that difficult to believe.  As an experiment you could try processing an album both embedding and not embedding the file and see if the resulting files are the same size or not.  Not much help I'm afraid; I mainly posted to say that your track cfg sounds fine - each section should have a "IF %embed_cover%==1 SET Cover_tag" line.

I went beack to ssb15... seemed to work better...but still not fully reliable.
I find it hard to believe that b15 should perform any different to b16 - the changes were with the GUI.

* If I leave DEBUG off, the batch file never runs. Is it possible that with DEBUG=1 in the ini file, something inside REACT changes?
I would have said that it does run, but exits so fast you don't see it.  Just a guess.

* With DEBUG=1, I also made the following changes to the CFG file, and I'm now running reliably:

At the top:
Quote
rem ECHO OFF
rem CHCP 1252

(My guess: echo off doesn't matter. But for some reason, the CHCP command still hangs a lot)
Hmm.. seems like CHCP is your problem, from what you've said, but I have no idea why.  If so you should be able to run the normal cfg not in debug mode, by just commenting out the CHCP line.
I'm on a horse.