Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

skip DOS part of sb16 install #12

Open
stsp opened this issue Mar 2, 2025 · 4 comments
Open

skip DOS part of sb16 install #12

stsp opened this issue Mar 2, 2025 · 4 comments

Comments

@stsp
Copy link
Member

stsp commented Mar 2, 2025

Hi, would it be possible to
skip the DOS part of SB16 install?
Otherwise it see the existing
C;\SB16 and asks for a confirmation.

Also the URL for the SB16 drivers
is pretty much "unreliable".

@jschwartzenberg
Copy link
Member

I think this should be possible. Possibly there are more appropriate driver sets that could be integrated directly into the Windows installer.

Otherwise it see the existing
C;\SB16 and asks for a confirmation.

Where did your existing c:\sb16 come from? Did it already have Windows drivers in it? Maybe the script could also detect the existence of an existing c:\sb16 directory and pick that up instead?

Also the URL for the SB16 drivers
is pretty much "unreliable".

Did you see it break? The archive that's there now has been in that spot for a few years.

@stsp
Copy link
Member Author

stsp commented Mar 2, 2025

Where did your existing c:\sb16 come from?

I had them previously, but
I could get them by running
your installation 2 times.

Did it already have Windows drivers in it?

Unless I am mistaken, DOS
drivers go there and windows
drivers go to windows\system?

Maybe the script could also detect the existence of an existing c:\sb16 directory and pick that up instead?

If the windows drivers are
there then maybe, but my
guess is that your driver
installs both. But we don't
need the DOS part.

The archive that's there now has been in that spot for a few years.

But no one can trust that, as
its too easy to replace its
content and drop in something
malicious.

@stsp
Copy link
Member Author

stsp commented Mar 2, 2025

In fact, your driver also updates
config.sys to include csp.sys, so
its definitely a DOSish part of the
driver.

@jschwartzenberg
Copy link
Member

Unless I am mistaken, DOS
drivers go there and windows
drivers go to windows\system?

Also the Windows drivers go there initially. Then a later installer phase takes them from c:\sb16 and puts them under the windows directory. The Windows applications and sample files stay under c:\sb16.
It is possible to trigger that later phase independently if the drivers were there from an older installation already.

your driver
installs both. But we don't
need the DOS part.

Indeed. I did not find a set with just the Windows parts and didn't find any way to skip the dos part.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants