|
Post by makaimura on Jan 17, 2020 9:32:04 GMT
Thank you all for the help. I was a little afraid the activity on the forum would be slow and would have made 2 months for someone to notice my thread... well this forum is more than alive for sure and I am happy about it. I know CMD... by that I mean I know how to start it but my knowledge about cmd stop around only that. I have put the huc.cmd in the bin folder. Now reading all of your comments I start to think I should not be in the bin folder .... because is where I was using my hello.c with huc.exe from the start. If Is that true ... I am sorry for my mistake. You see, After downloading the HUC Dev and for the first time after unzip it. The first thing I was looking for is a .exe to convert my hello.c. The only .exe I could find was in the bin folder. There is a "Makefile" file but with no extension at the very beginning .... if there is no extension , how can I launch it? I did run huc.cmd in the bin folder with all the other .exe. Even gave administrative power to every files and still no go. ( see picture attached please). I am really serious on learning Huc but as you can see I can't even create a .PCE lol. I really believe the problem is me here and not the software. Attachments:
|
|
|
Post by Arkhan on Jan 17, 2020 13:54:40 GMT
The problem is you in a sense, but it isn't a real problem or one you should feel bad about. You're just not used to how the old DOSy stuff needs to be setup. It's pretty easy to pick up on quickly though. If anything, the hardest part is Windows 8. The bin folder is absolutely correct. that contains the HuC.exe that you need. However, what you can do is set this HuC bin folder in your system's PATH variable so that you can access it from ANY directory in CMD. That way you can have your code in a folder called "My Game" for example, and still be able to call huc.exe This shows how on Windows 8 www.computerhope.com/issues/ch000549.htmignore the makefile. You won't need it. Just set the HuC bin on your system path and make sure the PCE_INCLUDE variable has been created as well, and you should be OK to use the tutorials. However, if the tutorial is saying drag and drop .C files onto the .exe, IGNORE that. It's a bad suggestion and a bad habit to form, because if you encounter errors, you won't see them because drag-drop closes the windows after they get these errors. Here is the actual HuC installation instructions: www.zeograd.com/parse.php?src=hucf#installation use those too.
|
|
|
Post by elmer on Jan 17, 2020 20:52:05 GMT
I really believe the problem is me here and not the software. Haha ... don't worry about it, it's not you, it really is the software! Please understand that HuC is 20 years old, and didn't really recieve any updates from 2005-2014, so there are a number of things in there that don't behave quite the way that modern folk expect. In this case, you've found another issue that most of us old-timers don't even think about ... you've installed HuC on your Windows Desktop, in a path that has spaces in the name. The screencap that you've posted shows that you're using the old HuC 3.21 from 2005, which was built with tools/technology that absolutely can't handle paths or filenames with spaces in them. You are welcome to keep on using that version of HuC if you wish, and ignore all of the changes and updates in the last 5 years, but if you do so, then there will be limited support that I can give you myself, since I don't use that old version. If you do wish to keep on using it, then I'd recommend that you move your huc directory from your desktop, and put it at the root of your C: drive, i.e. c:\huc\. Then you'll need to edit the huc.cmd file that I posted and change the line that says ... huc.exe -v -msmall "%~1" || goto huc_failed ... to ... huc.exe -v "%~1" || goto huc_failed Then, you should be able to compile the tutorials with the drag-n-drop, but only if your .c file is located in a path that has no spaces (such as c:\huc\bin). Now, even the latest release build of HuC from 2018 still has a problem with spaces in the compiled .s filename that HuC creates, but it is actually OK with HuC itself being located on your desktop. I've fixed the remaining problem now, and here is a build for you to try that should work properly when it and/or the file that you're compiling, are located on a path with spaces in it ... huc-2020-01-17.zip
|
|
|
Post by DarkKobold on Jan 18, 2020 1:17:30 GMT
I wish we could completely eliminate HuC 3.21, seems to be causing too many issues.
|
|
|
Post by spenoza on Jan 18, 2020 1:38:55 GMT
AFAIK, excepting those who don’t know about the updates to it, Arkhan is the only one who intentionally uses 3.21. Dunno about touko or cabbage, though.
|
|
|
Post by dshadoff on Jan 18, 2020 1:43:39 GMT
I do too... but only because I don't use it often enough to try out the updated version.
|
|
|
Post by elmer on Jan 18, 2020 4:27:55 GMT
I wish we could completely eliminate HuC 3.21, seems to be causing too many issues. I strongly believe that everyone has the absolute right to use whatever version they wish. I find it sad that some of the active PCE programmers aren't interested in the many long-overdue improvements that Uli made in HuC, and in supporting the continued development of both HuC and PCEAS .. but that is their choice to make. Just to remind folks (especially the newbies), Uli made over 650 commits to github in 2 years as he worked hard to improve HuC and to bring it more up-to-date. In the last 3-and-a-bit years (after his burnout), I have only made a paltry 70-or-so commits as I have fixed small bugs in his updates, and have added some new functionality of my own. The really big and useful changes are there because of Uli's amazing work, and have nothing to do with me. As Dave has said, HuC & MagicKit were supposed to be "starting points" that the community of developers would keep on working on and improving Even though that didn't really happen in the 2005-2015 time period, I still have the hope that more developers will come forward this decade to keep Dave's (and the other original developers') work alive and improving.
|
|
|
Post by elmer on Jan 18, 2020 4:49:54 GMT
Now reading all of your comments I start to think I should not be in the bin folder .... because is where I was using my hello.c with huc.exe from the start. If Is that true ... I am sorry for my mistake. Honestly, it really isn't something that you should worry about at this point. I'd recommend just following the tutorials and experimenting, while hopefully having fun. Yes, there are good reasons over the long term not to keep on putting your development files in the huc\bin directory, but that is something that you really don't need to think about until you start developing a real project. As I just said ... try to have fun, that's the most important thing right now. Yep, if the environment variables are setup on Windows, then drag-n-drop should just work. Microsoft just keeps on making that harder and harder with every version, since they'd prefer you to use an installer program and put such things in the Windows registry. I should probably just include a script in the next version of HuC that Windows folk can use to set up those variables. OK, here is such a script. Put it in your huc\bin\ directory, and then double-click on it in Windows Explorer to run it. It will set up the environment variables for you based on its knowledge that you have put it in the huc\bin\ directory. After you run this, you should just be able to drag-n-drop .c files onto the huc.exe program and have them compile. If it doesn't work as expected, then I'd like to know. Here is the downloadable file set-paths.cmd (1.35 KB), and here are the contents ... yuk, Windows command/batch files can be *ugly*! @echo off setlocal
rem ***************************************************************************
rem Simple setup of the HuC environment variables on Windows. rem rem Just put this file in the huc\bin\ directory and then double-click on it rem in Windows Explorer ... and it will set up PATH and PCE_INCLUDE for you.
rem ***************************************************************************
rem Get just the user's PATH, not the system PATH, nor the combined PATH.
for /f "tokens=2*" %%G in ('REG.EXE QUERY HKCU\Environment /V PATH 2^>NUL ^| FIND /I "PATH"') do set ipath=%%H
rem Remove any stray quotes.
set ipath=%ipath:"=%
rem Turn any stray Unix path separators into Windows path separators.
set ipath=%ipath:/=\%
rem Turn any spaces into Unix path separators (temporarily).
set ipath=%ipath: =/%
rem Loop through the path and remove any existing references to HuC.
set opath= for %%G in (%ipath%) do (call :filter_path "%%G")
rem Turn any Unix path separators back into spaces.
set opath=%opath:/= %
rem Set the user's new PATH and the PCE_INCLUDE environment variables.
pushd "%~dp0" cd .. setx PATH "%CD%\bin%opath%" setx PCE_INCLUDE "%CD%\include\pce" popd
exit /b 0
rem Add a path segment to the output path unless it contains "\huc\" somewhere in it.
:filter_path
set found=%~1 if "%found%" == "%found:\huc\=%" set opath=%opath%;%~1
exit /b 0
|
|
|
Post by gredler on Jan 18, 2020 4:58:44 GMT
That env variable script is probably worth putting in your stickied post, elmer.
|
|
|
Post by Arkhan on Jan 18, 2020 6:16:18 GMT
Actually, Microsoft made editing environment variables easier as of late, and finally fixed the UI so that each variable/path entry is it's own separate line...
so it's easier now than ever, especially for a non commandline fanatic like makaimura might be.
I think we should be careful in understanding the OPs stance/abilities/mannerisms before drowning them in scripts and technobabble.
Following the basic Zeograde HuC instructions from 15 years ago that I posted, should, in theory, be all that is needed to use ObeyBrew and get going.
|
|
|
Post by makaimura on Jan 18, 2020 13:25:15 GMT
Hi guys! Again Thank you for your informations and supports. I am frustrated but I am not giving up yet !! Arkhan : I will jump on the Zeograd tutorial and see if I can make it from there.Keep you updated! Believe me if the tutorial would have told me to write a specific command line in the CMD I will. The Obey tutorial says drag and drop so monkey see monkey do I do lol. I really want to learn I swear. The tutorial is well written. It is fun to read and give a positive energy, very good for beginners. elmer : I did download the huc-2020-01-17.zip , extract it and still no .pce converted (Failed message) . I edited the line in the huc.cmd and still nothing. I did exactly the same thing on a other computer running win7 ....same exact thing. the program keep making hello.s But seriously thank you for your patience !! Then I have some questions. On what "OS" are you running? Would it be better that I run a old OS in a virtualbox? Could it be a localisation problem? I live in Japan right now and my windows are Japanese. So just to make it clear (lol) ... I just wanted to write a hello words and see it in a PCengine ( emulator ) and it seem LOL starting to use the program is harder for... me.......... at least. It is quiet a shock for me. I jump on zeograd right now.
|
|
|
Post by Arkhan on Jan 18, 2020 15:55:32 GMT
Yeah, I think it might be a failing on the ObeyBrew tutorials if they didn't give the steps to install properly. Zeograd's site has the original HuC installs and instructions, so follow that. also, Zeograd's site has some open source tutorials/examples worth checking. For more code examples to mess with, we also released some opensource stuff done by TheOldMan and myself years ago: aetherbyte.com/aetherbyte-protocade_for_pc-engine_and_turbografx-16.htmlEDIT: you can also checkout Squirrel on our site, and run the BAT file there. If it runs, you have HuC installed right!
|
|
|
Post by elmer on Jan 18, 2020 22:02:58 GMT
That env variable script is probably worth putting in your stickied post, elmer . I'll add it to the next version of HuC so that people don't have to search for it. It is worth noting that the old ancient DOS instructions on Zeograd's Lair and ArchaicPixels only set the environment variables for that one particular invocation of a command shell, and that anyone following those instructions will need to be set the environment again if they ever close that window and/or reboot their computer. The variables need to be set the "Windows" way for them to stay permanently set, which you can either do with the script that I have provided, or by following the instructions on the website that Arkhan gave, or by creating a batch file to do your builds, such as DK & Greldler are using for Catastrophy. I am frustrated but I am not giving up yet !! Excellent! If you keep on trying, we'll eventually figure out what is going wrong! elmer : I did download the huc-2020-01-17.zip , extract it and still no .pce converted (Failed message) . I edited the line in the huc.cmd and still nothing. I did exactly the same thing on a other computer running win7 ....same exact thing. the program keep making hello.s But seriously thank you for your patience !! Then I have some questions. On what "OS" are you running? Would it be better that I run a old OS in a virtualbox? Could it be a localisation problem? I live in Japan right now and my windows are Japanese. I usually run Windows 7 (64-bit), but I have just downloaded the huc-2020-01-17.zip file and tried it on my Windows 10 computer, and it works perfectly. There shouldn't be any need to run an old OS. The set-paths.cmd file works too, but I did have to manually unblock it on Windows 10 because Windows Defender didn't like it that I had downloaded the program from the Internet. That is another reason for posting the source for the batch file ... so that folks can verify that I'm not distributing a virus or anything like that. At this point I'm guessing that we're hitting a localization problem, especially since *nothing* in *any* version of HuC is able to handle either unicode, or non-english characters. Could you please attach a copy of your "hello.c" file to a message here so that I can download it and check it? I'll also try switching my Windows into Japanese and see if that breaks things.
|
|
|
Post by dshadoff on Jan 18, 2020 22:14:19 GMT
Perhaps you can also give the full pathname that you are using for the HuC install and where you are doing your program development (not sure if they are the same directory at present).
|
|
|
Post by elmer on Jan 19, 2020 0:08:04 GMT
I'll also try switching my Windows into Japanese and see if that breaks things. I switched my Windows locale to Japanese, and confirmed that the font had changed in the command window (as expected). Then I used notepad++ to create the tutorial's hello.c from the ObeyBrew website. Unfortunately, HuC had no problem at all building the file and creating hello.pce ... so I think that Dave is right, we're going to need to see both that hello.c file, and know which diretories everything is in. If that doesn't show an obvious problems, then we're going to have to resort to special test-builds that spit out more information so that we can debug the problem.
|
|