Editor, Experienced Forum User, Published Author, Player
(67)
Joined: 6/22/2005
Posts: 1041
Welcome! Not bad for a first TAS. Like you've already mentioned, doing interesting things is a huge part in any autoscroller or autoscrolling section, probably the most important thing after not making mistakes.
Did you load a state around 1:30? There seemed to be a split in the video.
There's also this thread that you can use for WIP files/encodes.
Editor, Experienced Forum User, Published Author, Player
(67)
Joined: 6/22/2005
Posts: 1041
You should use a trace logger to find out what code is executed before the value is written. That can point you to relevant addresses. What emulator are you using?
Editor, Experienced Forum User, Published Author, Player
(67)
Joined: 6/22/2005
Posts: 1041
The behavior of console.write and console.writeline seems unusual in 2.3. If you reload the script via the Script menu or the toolbar button or F5, the message is printed twice. This doesn't happen if you toggle the script or double-click it in the list. Minimal example:
Editor, Experienced Forum User, Published Author, Player
(67)
Joined: 6/22/2005
Posts: 1041
I've been reading more about Linux. Would it be preferred to boot into a graphical environment or into text mode? FP needs the graphical environment to run, but configuring everything would probably be easier in text mode. Also, would we want a full desktop environment, or just the minimum necessary to run FP?
Editor, Experienced Forum User, Published Author, Player
(67)
Joined: 6/22/2005
Posts: 1041
FCEUX has an issue in which the movie files may get saved in a different directory when running a Lua script; in my experience, it's been some subdirectory of the one containing the Lua script. Based on my searches of the forum, this problem was reported several years ago but never fixed. Try looking in all of the subdirectories of your FCEUX directory for the file with the proper input.
Editor, Experienced Forum User, Published Author, Player
(67)
Joined: 6/22/2005
Posts: 1041
BrunoVisnadi wrote:
Oh! I used to think 'zebra' was a Brazilian term, but I listened it in the first episode of House MD, when House was referring to the possibility a improbable disease causing the patient symptoms, instead of a common one. So I figured 'zebra' was an universal term for improbable events.
Yeah, there's a saying in medicine along the lines: "If you hear hooves, think of horses rather than zebras."
I'm still hoping for Belgium to reach the final. Since Switzerland is out, I hope for Russia or Croatia from the other side of the bracket.
Editor, Experienced Forum User, Published Author, Player
(67)
Joined: 6/22/2005
Posts: 1041
Wow, what was going on with the pitch in that Uruguay - Portugal match? The players were slipping and falling so much. At this point, I'm hoping for the final to be Uruguay or Belgium versus Switzerland.
Editor, Experienced Forum User, Published Author, Player
(67)
Joined: 6/22/2005
Posts: 1041
feos wrote:
Does it run at full speed this time?
The PCem emulation generally doesn't run at 100% on my computer (it's old), but I don't think it was going at full speed even when accounting for that slowdown.
feos wrote:
What about Samorost?
It does seem to work, but I didn't get far into it because of the slow speed.
I've looked into the sound situation and learned that Linux has two sounds APIs, OSS and ALSA. OSS is the older one. Unfortunately, I can't install it under TinyCore v9.0 because one of the dependencies is missing: oss-modules-4.14.10. ALSA does install but doesn't work properly with the Sound Blaster PCI 128. During boot, I get the error
snd_ens1371 0000:00:13.0: AC'97 0 access is not valid [0x0], removing mixer.
The description for the alsa-config.tcz extension says that it may be necessary for legacy hardware, but I still get that error message during boot after installing it. Older cards, such as AdLib and Sound Blaster 16, don't seem to be detected at all.
To check if something may be wrong with the ALSA installation, I converted the hard disk image to VMDK format using this program called qemu-img.exe. Then I made a VMware VM and used that file as the hard disk. It was able to detect my computer's sound card without problems, and sound worked after I created the .asoundrc file as described here. Note that the default volume might be 0, which I fixed with the command
amixer set Master 100
So I suspect that the sound cards emulated by PCem are too old to use with TinyCore v9.0. An older version that doesn't have missing dependencies for OSS might work.
EDIT:
OK, so I've confirmed that sound works via OSS. Had to go back to TinyCore 7.0. The 8.x versions ran into some kernel panic when booting from the ISO, so I didn't even get them installed. Unfortunately, abobo crashes at the title screen with an "illegal instruction" error.
EDIT2:
Additional testing suggests that the illegal instruction is a FP problem. You can get past it by mashing A at the title screen.
Editor, Experienced Forum User, Published Author, Player
(67)
Joined: 6/22/2005
Posts: 1041
I got FP9 standalone running in TinyCore Linux version 9.0 using the Core-current ISO. The PCem configuration was:
Award 430VX PCI Pentium 150
256 MB RAM
S3 ViRGE/DX
Sound Blaster PCI 128
C1800 H16 S32 hard disk (450 MiB)
Microsoft 2-button serial mouse
Realtek RTL8029AS network card
Use these instructions to install TinyCore to the hard disk*. Note that the Core-current ISO boots to command-line rather than GUI, so you'll have to use the tce-load commands rather that the Appbrowser. Also, the command-line Appbrowser is actually tce-ab, not ab.
Using these instructions, I chose Xprogs.tcz, Xvesa.tcz, flwm.tcz, and aterm.tcz to get a desktop. I installed them by searching for the names in the tce-ab program rather than using wget.
FP9 also requires gtk2.tcz.
You may need to reboot here.
Mount an ISO file or another hard disk containing FP9 and the SWF files. Technically optional here, since you can do this after you get to the desktop.
Run xsetup to choose the display resolution and specify that the mouse is COM1 and 2 buttons.
Run startx to get to the desktop.
Start the terminal using the rightmost graphic at the bottom of the desktop (this is what aterm.tcz installs).
Mount the ISO or hard disk if you didn't do it earlier.
cd to the proper mount point and run ./flashplayer abobo.swf or whatever file you want.
*A few modifications are necessary to those instructions:
When editing menu.lst, use vmlinuz instead of bzImage, then put the word text at the end of that line. The text makes it boot to command-line rather than GUI.
When editing menu.lst, use core.gz rather than tinycore.gz.
There are graphical errors in the FP9 menus, but the SWF files themselves seem to run properly. I haven't tried to get sound working yet, though. Also, the glibc version installed in TinyCore by default is 2.2.x, which is lower than the requirements that Adobe lists on their site. IDK what problems may arise from this, if any. The TinyCore FAQ says that FP10 is unlikely to work due to its requirements, but it only mentions installation as a browser plugin.
Editor, Experienced Forum User, Published Author, Player
(67)
Joined: 6/22/2005
Posts: 1041
If you don't want to use the preformatted hard disk images from the Bannister OS install thread, here's one way to create hard disks in sizes that you want and then partition them without worrying about DOS limits (BIOS limits still apply):
Create the image file using chdman or PCem's options or whatever method you prefer.
Run PCem with a machine that has a BIOS that lets you access whatever hard disk size you want. For example, I used the Award 430VX PCI Pentium 133 and was able to partition C2000/H16/S63 (984 MiB) and C10000/H16/S63 (4.8 GiB) disks.
Use FDISK on the FreeDOS 1.2 boot floppy with FAT32 support enabled to create the partition(s).
Format the partition(s) using your preferred method, such as the FreeDOS 1.2 boot floppy or an OS that you have installed on another hard disk.
Editor, Experienced Forum User, Published Author, Player
(67)
Joined: 6/22/2005
Posts: 1041
r57shell wrote:
Dacicus wrote:
I ran into the same problem as that guy about only being able to have VGA display in 16 colors.
First, backup your .chd disk.
Switch driver of display in Win98 into Standard VGA using "show all drivers" option dot.
Shutdown windows & mame.
Then, use "-isa1 svga_s3" in command line, to have svga_s3 instead.
Then, in display select "show all drivers" and look for "Number Nine 9FX Vision 330".
Reboot.
Try 256 mode \o/
This doesn't work in Windows ME. I tried with svga_s3, s3virge, and s3virgedx. They all appear in the "show all drivers" screen, but none of them get beyond 640 x 480 x 16 colors. A fresh install of Windows ME in PCem with the Award SiS 496/497 i486DX/25 and ViRGE/DX did pick up the ViRGE/DX from the beginning, though, so I suspect that the problem is with MAME. I even tried changing the hard disk from the PCem install into a CHD and loading it in MAME, but I got a message about the display adapter not being configured properly when WinME started, and it was back to 640 x 480 x 16 colors.
Editor, Experienced Forum User, Published Author, Player
(67)
Joined: 6/22/2005
Posts: 1041
feos wrote:
Install x86 Windows, up to XP, inclusively. Even if we come up with ways to disable some features that may slow the system down or increase its memory usage, there's still no way to distribute it, so we have to install it from scratch.
LitePC has software that can help eliminate some of the features. I've used the trial version of the 98lite product to install WinME in MAME on ct486. Information is available in this thread; I ran into the same problem as that guy about only being able to have VGA display in 16 colors.
Editor, Experienced Forum User, Published Author, Player
(67)
Joined: 6/22/2005
Posts: 1041
I was able to get Flash Player running in DSL, but it was the Firefox plug-in of version 7.
I searched the Red Hat install for those dependencies linked above and found that the following are missing for FP9:
libfreetype.so.6
libfontconfig.so.1
libgtk-x11-2.0.so.0
libgobject-2.0.so.0
libglib-2.0.so.0
glibc>= 2.3 (has 2.1.3)
support for V4L1 (not sure how to check this)
For FP10, the following are also missing:
glibc>= 2.4
libnss3
cURL
support for V4L2 (again, not sure how to check this)
My search consisted of running
find -iname "libgtk*"
or similar lines in the / directory and comparing the file names, but I have minimal experience with Linux, so maybe that's a bad way to approach it.
EDIT: I've also tried some other distros, but these did not even finish booting from the ISO: Tiny Core Linux (never seemed to finish loading the kernel), Gentoo (same thing), CentOS 6.9 (not enough memory).