Project looking for Programmer (I can't do it myself)

[bplus]

Yeah, except User Interface is probably much easier with QB64, specially if at some point we want to select items from an array.

[Pete]

Is it as simple as this...

DEMO. I would recommend this.

1) DON'T use run, instead choose to make this exe by clicking RUN in the IDE and in the menu that opens, click "Make exe only."

2) Now make a folder called "myQB64installdemo" and cut and use Windows Explorer to move the qb64 exe file just made into that new folder.

3) Run the exe.

This is just for piece of mind, so any modifications will not mess with stuff in your QB64 folder.

The program will make a new sub-directory, called: mock-directory-to-demo-installer

Now I made it a sub-directory for demo purposes, only. If this is what the OP is looking for, obviously that part of the installer would need to be worked on so the user could install to the C drive, D drive, etc.

The code also makes a phony Hello World text file in the folder the exe is in. It then copies that file to the new install folder. The demo technique could be used to copy (install) any file. Of course this simple type of install process does not affect the Windows Registry. Anyway, here's my demo...

Code: QB64: [Select]

1. OPEN "Hello-World.txt" FOR OUTPUT AS #1: PRINT #1, "Hello World!": CLOSE #1
2.  
3. SourceFile$ = "Hello-World.txt"
4. TargetDir$ = "mock-directory-to-demo-installer"
5. IF _FILEEXISTS(SourceFile$) THEN ELSE PRINT "Source file: "; SourceFile$; " not found. Ending...": _DELAY 5: END
6. ' Source file exists, ask user to install.
7. PRINT "Would you like to install " + SourceFile$ + "? Y/N: ";: LINE INPUT ans$: PRINT
8. IF ans$ = "" OR UCASE$(ans$) = "N" THEN END
9. ' User wants to install. Ask if target directory is okay for install.
10. IF _DIREXISTS(TargetDir$) THEN
11.     ' Prompt for overwrite.
12.     IF _FILEEXISTS(TargetDir$ + "\" + SourceFile$) THEN
13.         PRINT SourceFile$ + " already exists on this device. Overwrite? Y/N: ";: LINE INPUT ans$: PRINT
14.         IF ans$ = "" OR UCASE$(ans$) = "N" THEN END
15.         PRINT "Overwrite in progress...": PRINT
16.         KILL TargetDir$ + "\" + SourceFile$ ' Removes previous install.
17.     END IF
18. ELSE
19.     PRINT "Setup will create directory " + TargetDir$
20.     PRINT "to install " + SourceFile$ + ". Press Enter to begin or Esc to abort.": PRINT
21.     DO
22.         _LIMIT 30
23.         b$ = INKEY$
24.         IF LEN(b$) THEN
25.             SELECT CASE b$
26.                 CASE CHR$(23): SYSTEM ' Ends routine and closes install window.
27.                 CASE CHR$(13): EXIT DO ' Okay to install.
28.                 CASE ELSE: BEEP ' Wrong entry signal.
29.             END SELECT
30.         END IF
31.     LOOP
32.     ' Create directory.
33.     MKDIR TargetDir$
34. END IF
35. ' Install.
36. IF _DIREXISTS(TargetDir$) THEN
37. ELSE
38.     PRINT "Directory path: "; TargetDir$
39.     PRINT "not found. Cannot install. Ending...": _DELAY 5: END ' Fail safe.
40. END IF
41. PRINT "Installing app...": PRINT
42. OPEN SourceFile$ FOR BINARY AS #1
43. a$ = SPACE$(LOF(1))
44. GET #1, , a$
45. CLOSE #1
46. OPEN TargetDir$ + "\" + SourceFile$ FOR BINARY AS #1
47. PUT #1, , a$
48. CLOSE #1
49. ' Verify install.
50. IF _FILEEXISTS(TargetDir$ + "\" + SourceFile$) THEN
51.     PRINT "Installation successful.": PRINT
52. ELSE
53.     PRINT "Installation failed.": PRINT
54. END IF
55. END

Pete

[SMcNeill]

If these are for windows only, couldn't you just make the whole thing a self-extracting EXE?

https://www.winosbite.com/iexpress-exe/

iexpress comes with windows in the C:\Windows\System32\ and can create self-extracting archives, and sounds like it'd be the best tool for the job to me.  Compress and make the EXE.  Distribute it.  User clicks the EXE and windows handles the rest of the install process.

[Pete]

I used to use WinZIP Professional to set up my office software. I wrote a setup program and included the 20 or so office programs. Remember, that was back in the day QuickBASIC was limited to about 200KB per app, provided you took a mullti-modular build approach. Anyway, the WinZIP allowed me to pack all my files and unpack them on all my office computers. It would also initiate my setup.exe program, upon unpacking. What was neat is it kept all files in a temp folder, until the directories were made by the setup program. It would then transfer them to the correct folders, and kill the temp stuff.

Pete

[Daniel3D]

If these are for windows only, couldn't you just make the whole thing a self-extracting EXE?

It is meant to be DOS only. To fit with the game.

And maybe a batch script can do it to, I don't know
I don't know if that can handle sub folders and check source and destination.

I'll type out a pseudo script later when I am behind a real computer.

Thanks for the response so far.

[SMcNeill]

It is meant to be DOS only. To fit with the game.

@bplus Then you're going to need DOSBOX and QB45, if you want to compile a DOS-level executable from a BAS file.  QB64 requires Win XP or better to run.

I haven't did any DOS level stuff for twenty years.  I moved on with the times.  :P

[bplus]

@SMcNeill  That's what I thought but Daniel was posting FB code at another forum. So I am thinking he has Windows to run exe's that do Setups but Runs the actual game in DOSBOX.

Yeah I haven't done DOS since late 90's. I gave my computer with all that stuff to a kid that didn't have anything when I updated to Windows 7? I think.

[Pete]

@bplus and @SMcNeill Do you guys think what I posted will turn out to be relevant or is this project looking like something more complicated than the usual way we copy files in QB64?

Pete

[bplus]

@Pete  going by this

User input. As long as the source contains the game.
If destination doesn't exist ask to create.
If it does exist ask for overwrite.

I was thinking "the source" is Folder containing "the game".

We could actually make a backup folder before overwriting the destination in case something goes horribly wrong.

[bplus]

I'll wait for pseudo, get all questions answered before coding.

[Pete]

Mostly, you need to be careful while you're coding it. I think that's why BASIC developers chose the name KILL for that keyword. I mean you could incorporate Indy's neat send to the Recycle Bin API code. That way, nothing every gets completely removed, or sure, MKDIR backup and number the backup files. That's the method I use for my database files... myfile-1.bak, myfile-2.bak, etc. Hey, what are the chances Rob will return and code us the _RESURRECT keyword? That would solve everything! :D

Pete

[SMcNeill]

The problem with this type of request is the target audience.

This task is as simple zs:

At command prompt type: COPY *.* MyDrive://MyFolder/MySubfolder/*.*

That's it, and any jack-ass even 0.01 percent fluent with DOS should know enough to do that.  Unfortunately, the people who play this game are completely clueless about the environment they're working in because they need an installer.

Which leads to using QB45 and DOSBOX...

Where nobody has any libraries or toolsets anymore...

Which means you need to write a file listing program to give you a list of the files and folders on the drive, then an input routine so the user can choose which drive and folder to copy it to, then you need a disk space checker, then finally a copy routine with clean up and overwrite capacity...

Your little one line DOS command is now 1000 lines of antiquated, redundant, error-checking with a simple single SHELL command placed right before the END statement.


Good luck with that!

Here's my go at this:

INSTALL.BAT:

Code: [Select]

COPY *.* DRIVE://FOLDER/*.*
README.TXT:

Code: [Select]

Edit INSTALL.BAT to point to desired directory to save to.  Save and execute.

[Daniel3D]

Yes, the installer is aimed at people not used to DOS. I do expect them to be able to navigate in a DOS environment though.
But that's about it.

@bplus : the Freebasic code you referred to was compiled such that it runs under DOS. It was the easiest way to code what was needed and still support DOS.

As for the installer.  (I included screenshots of the original installer that doesn't work with this version of the game: it has a text mode interface. It would be cool if that could be copied for ascetic reasons, the base for that is in the SETUP.BAS that may be used. But command line is fine to)

Code: QB64: [Select]

1. on run install
2. - ask source of the game #(can be the same as the current dir or different, does not matter | does not need to be checked)
3.   # Enter drive to install form:
4.   # EXAMPLE: A:\  
5.  
6. - check if the source contains SKID*.exe files (there should be four of them, but check for any)
7.  
8. ask for destination,
9.   # Enter GAME directory
10.   # EXAMPLE c:\stunts\
11.  
12. Check if the destination exists.  Create or Ask to overwrite or change destination.
13. Don't check for enough space.
14.  
15. then copy files [source directory + subdirectories + all files]
16. (ESC to terminate, don't revert, just stop)
17. show, install complete box Return to menu on enter.

[Daniel3D]

I'll wait for pseudo, get all questions answered before coding.

I hope I cover all important bits.
Like I said in the title. I can't write code, I can read it and understand most of it though. I'm not completely clueless.

Keep it simple. If the user f**s it up, he can download it again. It is a free game.

[Daniel3D]

@Pete  going by this

I was thinking "the source" is Folder containing "the game".

We could actually make a backup folder before overwriting the destination in case something goes horribly wrong.

Technically, one could use the installer to restore a broken game by installing/overwrite.
It should not matter if the installer is started from the broken game folder or from the installation copy.

A backup is not needed. Too much work, the game can always be downloaded again, just as any mods.